From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/11] omap2/3/4: Disable CONFIG_FB_OMAP in omap3_defconfig
Date: Tue, 4 May 2010 12:23:24 -0700 [thread overview]
Message-ID: <20100504192324.GI29604@atomide.com> (raw)
In-Reply-To: <1272984625.1978.30.camel@tubuntu.research.nokia.com>
* Tomi Valkeinen <tomi.valkeinen@nokia.com> [100504 07:45]:
> On Tue, 2010-05-04 at 16:40 +0200, ext Tony Lindgren wrote:
> > * Tomi Valkeinen <tomi.valkeinen@nokia.com> [100504 00:21]:
> > > Hi,
> > >
> > > On Tue, 2010-05-04 at 02:52 +0200, ext Tony Lindgren wrote:
> > > > * Tony Lindgren <tony@atomide.com> [100430 13:47]:
> > > > > * Tony Lindgren <tony@atomide.com> [100430 13:32]:
> > > > > > Looks like CONFIG_FB_OMAP prevents somehow mounting root on MMC
> > > > > > at least on zoom3 for multi-omap. Disable CONFIG_FB until the
> > > > > > omap FB code is fixed.
> > > > >
> > > > > This one I'll drop as soon as the problem is sorted out with
> > > > > CONFIG_FB_OMAP.
> > > >
> > > > This one seems to be something under drivers/video/omap, so
> > > > I'll change CONFIG_FB_OMAP to be a module now. Updated patch
> > > > below.
> > > >
> > > > I'll update omap for-next accordingly, then Tomi can figure
> > > > it out :)
> > >
> > > This sounds... interesting... =) Any more info on what happens? Does it
> > > also affect new omapfb driver?
> >
> > Yeah this is interesting, it seems like the kernel cmdline gets
> > somehow corrupted for zoom3 with the omap3_defconfig if CONFIG_FB_OMAP=y.
> > Some options seem to be there, but for example rootwait option is
> > ignored and the root on MMC never mounts. This is in the current
> > omap for-next branch.
>
> Ok, so the cmdline parsing in omapfb could be broken. I'll check it out.
OK thanks. Hmm, it could be that it works on n8x0 and n900 because they
are using the kernel built in cmdline.
> > Hmm, what do you mean with "new omapfb" driver, the stuff you have
> > queued up?
>
> No, I mean the DSS2 version. drivers/video/omap is the old one, written
> mostly by Imre, and drivers/video/omap2 is the new one, written mostly
> by me.
>
> I guess most boards are still using the old omapfb driver.
Ah I see, it does not have CONFIG_FB_OMAP2 set. I did a quick test
with that and the bootloader passed cmdline on zoom3 works just fine.
I used the options below.
Nothing on the LCD panel on zoom or n900 though, I guess some updates
are still needed for that.
Regards,
Tony
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fb-omap2.patch
Type: text/x-diff
Size: 1388 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100504/cf575178/attachment.bin>
next prev parent reply other threads:[~2010-05-04 19:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 20:33 [PATCH 00/11] omap2/3/4: Multi-omap updates to boot test with omap3_defconfig Tony Lindgren
2010-04-30 20:33 ` [PATCH 01/11] omap2/3/4: Fix multi.h when omap3 and omap4 are selected without omap2 Tony Lindgren
2010-04-30 20:33 ` [PATCH 02/11] omap2/3: Fix DEBUG_LL for omap zoom2/3 Tony Lindgren
2010-04-30 20:55 ` Kevin Hilman
2010-04-30 21:02 ` Tony Lindgren
2010-04-30 21:20 ` Kevin Hilman
2010-04-30 21:37 ` Pandita, Vikram
2010-04-30 21:53 ` Pandita, Vikram
2010-04-30 22:00 ` Kevin Hilman
2010-04-30 23:30 ` Tony Lindgren
2010-05-01 0:10 ` Kevin Hilman
2010-05-01 1:37 ` Tony Lindgren
2010-05-01 1:50 ` Tony Lindgren
2010-05-03 22:10 ` Pandita, Vikram
2010-05-04 0:40 ` Tony Lindgren
2010-05-04 0:57 ` [PATCH 02a/11] omap: Use a memory address for storing the debug port info instead of UART1 scratchpad Tony Lindgren
2010-05-04 0:58 ` [PATCH 02b/11] omap2/3: Fix DEBUG_LL for omap zoom2/3 Tony Lindgren
2010-05-04 17:33 ` Pandita, Vikram
2010-05-04 23:09 ` Tony Lindgren
2010-04-30 20:33 ` [PATCH 03/11] omap3: Fix compile for board-cm-t35 Tony Lindgren
2010-04-30 20:33 ` [PATCH 04/11] omap3: Remove non-muxable ball entries for 3630 Tony Lindgren
2010-04-30 20:33 ` [PATCH 05/11] omap4: Fix multiboot with CONFIG_PM and CONFIG_ARCH_OMAP3 selected Tony Lindgren
2010-04-30 20:33 ` [PATCH 06/11] omap4: Fix omap_l2_cache_init not to run for other omaps Tony Lindgren
2010-05-01 6:18 ` Shilimkar, Santosh
2010-05-01 17:46 ` Tony Lindgren
2010-04-30 20:34 ` [PATCH 07/11] omap2/3/4: Add new boards to omap3_defconfig Tony Lindgren
2010-04-30 20:34 ` [PATCH 08/11] omap2/3/4: Make omap3_defconfig usable on Nokia boards Tony Lindgren
2010-04-30 20:34 ` [PATCH 09/11] omap2/3/4: Update PMIC options for TWL and Menelaus chips Tony Lindgren
2010-04-30 20:34 ` [PATCH 10/11] omap2/3/4: Dissable CONFIG_PM_VERBOSE in omap3_defconfig Tony Lindgren
2010-04-30 20:34 ` [PATCH 11/11] omap2/3/4: Disable CONFIG_FB_OMAP " Tony Lindgren
2010-04-30 20:50 ` Tony Lindgren
2010-05-04 0:52 ` Tony Lindgren
2010-05-04 7:26 ` Tomi Valkeinen
2010-05-04 14:40 ` Tony Lindgren
2010-05-04 14:50 ` Tomi Valkeinen
2010-05-04 19:23 ` Tony Lindgren [this message]
2010-05-05 17:32 ` Old DSS code broken as module (was "RE: [PATCH 11/11] omap2/3/4: Disable CONFIG_FB_OMAP in omap3_defconfig") Aguirre, Sergio
2010-05-05 17:43 ` Tony Lindgren
2010-05-05 18:23 ` Aguirre, Sergio
2010-05-06 8:07 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100504192324.GI29604@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).