After being again some days offline (yes, I'm still alive) I quickly scanned the IRC logs (some interruption?) and saw that I missed some discussion about uboot v1 patches upstream sending.
Don't forget me
I'd be really happy to help to bring uboot v1 patches upstream as I already helped with DaVinci uboot support.
Step 1: First, I think we need a patch again recent uboot v1 that works for all of us. For this first step, I think the format (code and file organization) doesn't matter. Just let us get the technical stuff working (*).
Step 2: Then, the next step would be to reorganize the file/directory organization, clean up the code and create a set < 40k patches from the first step patch.
Step 1 & 2 can be done on this list. If we think that the result of step 2 is ready we can send it to uboot list. Then, the usual re-do cycles start, everybody can help. Most probably, it will become harder than with omap-linux patches
I think we need to agree that we couldn't get anything what is currently in the uboot patches upstream. E.g. I think our chance for upstream will be better if we omit logo and audio output and try to bring "nice to have features" upstream in some later steps.
Btw: Steve: Does
mean that recent uboot v1 git
+ uboot beagle patches
+ 500MHz patch
+ don't disable L2 cache for kernel patch
+ logo and audio *disabled*
works stable for you? Have to try this, maybe if we disable audio the I2C issues I saw are gone...
(*) I would have started with upstream preparing already if I hadn't these I2C issues, i.e. if I had some stable uboot git patches.