On Wed, Jun 22, 2011 at 11:50 PM, Andy Green <[email protected]> wrote: > On 06/22/2011 10:44 PM, Somebody in the thread at some point said: > >>> androidboot.console=ttyO2 >>> >>> but later there might be more funnies for Android that could conflict, >>> eg, omapdss needs twiddling for Android use. >> >> Well, the change in question is >> >> - 'omapfb.vram=0:24M mem=456M@0x80000000 mem=512M@0xA0000000') >> + 'omapfb.vram=0:24M,1:24M mem=456M@0x80000000 >> mem=512M@0xA0000000') >> >> is that going to affect Ubuntu too? > > Probably not... the code iterates through those 0:24M or 1:24M according to > how many framebuffers are defined. > > But the general point is they might come to conflict for sure one day... if > you want to leave separating them out until that day then fine; but we are > left with having to confirm changes both ways.
my understanding is that we can specify default built-in bootargs for the android u-boot ... so if our boot.scr just adds to the default bootargs, things that are android specific could be done there. For the vram case I don't think its something that affects ubuntu ... might even be useful. Lets take a more thorough look for 11.07 on this topic. -- - Alexander _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
