On 2008.05.12. 20:31:38 Brian Oostenbrink <[EMAIL PROTECTED]> wrote: > We certainly will consider donating a couple of boards. They are in a > bit of short supply right now, so not sure yet when we'd be able to free > a couple up. > However, I'm not sure how having hardware would help to answer the > questions I raised, as they are really about the architecture of the > build system.
Sounds good, thanks! I think Gregers meant that we could actually answer better to the integration/optimization questions given we have the hardware, too. Of course your current questions were mostly "starters before the lunch" I think :) I would be happy to help in getting the needed patches working with newer kernels, too. > I managed to resolve the third question I raised > (compilation error), and have managed to build a working image for my > board, using a ram filesystem. I'm now working on getting the squashfs > filesystem working with our kernel. I've chosen to work with the 7.09 > release of kamikaze for now, and have simply added my own kernel version > to the workspace. I've added a patched-2.6.20 directory to > target/linux/generic-2.6 and this allows me to control exactly which > patches are applied against my kernel, but it seems wrong to have to > modify the generic-2.6 folder to get what I want. If there is a way to > accomplish this inside my target/linux/<my_platform> dir, that would > seem a better way to go. What you did sounds right. If general, if you want to add support for a different kernel version, you have to place the patches in target/linux/generic-2.6/patches-x.y.z and create a target/linux/generic-2.6/config-x.y.z if needed, too. If you don't want to have all the current generic openwrt patches, you can simply avoid them in the new directory. Cheers, Imre _______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
