On Thu, Apr 11, 2002 at 05:03:41PM -0700, Tom Rini wrote: > I assume once the custom HW is 'ready', you'll be able to stop doing > that tho. I think you'll spend more time trying to get everything just > right than you would building 2 kernels a few times (I bet much of the > pain comes from the current kbuild crap. You might wanna play w/ the > current kbuild-2.5 stuff if you're going to pick a kernel rev & stay for > a while, it gets the deps right so you only recompile the needed files > in cases like this).
We already have a few boards running but right now we have to fight over them. With the Walnuts we can build and test kernel changes without holding up other people using the boards. So far doing 2 builds has been ok, but it shouldn't be too much work to get things working for both. I am not looking at the code now, but for a 405 you just need to do a board header and a C file. The amount of work these things do is small, but they all define the same functions. That doesn't lend itself to working for more than one board. It should be easy enough to put those functions in a structure do things dynamicaly. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
