On Mon, Nov 29, 2010 at 09:56, Carsten Munk <[email protected]> wrote: > They'll stay on Maemo side as they're fairly hacked. At least the > default boot script parts. As well as the fact that on N900, it's not > the first boot loader that runs, NOLO is, so maybe it's not really > suitable for real u-boot support. errr... x-loader does something similar on other OMAP platforms - it might be good to cleanup the series and post upstream if possible. > > http://al.robotfuzz.com/~al/maemo/u-boot/ contains patches. What we http://al.robotfuzz.com/~al/maemo/u-boot/0001-Reduce-delays-in-omap-i2c-driver.patch i had seen something similar to mainline: http://marc.info/?t=128715890600001&r=1&w=2 no reason for these to be private
http://al.robotfuzz.com/~al/maemo/u-boot/0002-Make-bootm-optionally-use-pre-existing-atags-for-Lin.patch should post it upstream IMHO. http://al.robotfuzz.com/~al/maemo/u-boot/0004-Nokia-RX-51-aka-N900-support.patch can go upstream in short, I dont think these need to be private.. at least could rebase and start the discussion on denx u-boot ML :). > need in MeeGo is just the uImage generation for N900 side. ofcourse and u-boot-tools does the job > We should test the Trunk:Testing package for PandaBoard. sure, will do. Regards, Nishanth Menon _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
