Re: [microblaze-uclinux] [patch test] syscall interface cleanup

[David McCullough <davidm@xxxxxxxxxxxx>]

Jivin John Williams lays it down ...
...
> The tricky part concerns when and how to apply these patches in the 
> uclinux.org CVS repository.  Both patches (uClibc and kernel) are 
> required for proper operation, but only the kernel CVS can be updated on 
> demand.  This means the uClibc patch would have to be applied manually 
> until the new uClinux-dist comes out, and it would, in effect, be 
> mandatory for anyone tracking CVS on the kernel.
> 
> The other approach would be to get the Snapgear guys to apply the 
> patches to the new uClinux-dist, then we apply the kernel patches to CVS 
> at the same time as the uClinux-dist at cvs.uclinux.org is updated. 
> This way anyone could do a CVS update over both the dist and kernel, and 
> it should all pull down cleanly... (everybody synchronise your watches! :)

I am sure we could manage that.  As a minimum I was thinking the next
test dist should go into CVS anyway to make it easier for people to send
in patches before the final release.  We can make sure we have all the
code in the dist before hand.  We sync our kernels up to uclinux.org
about the same time anyway.

> Finally, it is possible to make this new brki support conditional in the 
> kernel with a config option, but it's ugly and seems like a lot of work 
> to provide back-compatibility to something so broken.

If it's a better way to go I would just drop the old way,

Cheers,
Davidm


-- 
David McCullough, davidm@snapgear.com  Ph:+61 7 34352815 http://www.SnapGear.com
Custom Embedded Solutions + Security   Fx:+61 7 38913630 http://www.uCdot.org
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/