From: archit taneja <archit@ti.com>
To: Sung Hee Park <shpark7@stanford.edu>
Cc: Bryan Wu <bryan.wu@canonical.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Semwal, Sumit" <sumit.semwal@ti.com>
Subject: Re: omapfb: no driver for display
Date: Fri, 18 Feb 2011 09:57:51 +0530 [thread overview]
Message-ID: <4D5DF547.7010703@ti.com> (raw)
In-Reply-To: <AANLkTinoLOyqBCMNKbpcJMhZHnncX1T07nbfsTThA_a4@mail.gmail.com>
Hi,
On Friday 18 February 2011 09:46 AM, Sung Hee Park wrote:
> Bryan,
>
> I've already tried that patch but didn't work. The omapdss is not
> showing any error message, but omapfb still does.
>
> Thanks,
> Sung Hee
>
> On Thu, Feb 17, 2011 at 7:46 PM, Bryan Wu<bryan.wu@canonical.com> wrote:
>> Sung Hee,
>>
>> Could you please try the patch I forwarded to L-O yesterday?
>> https://patchwork.kernel.org/patch/569501/
>>
>> Thanks,
>> -Bryan
>>
>> On Fri, Feb 18, 2011 at 11:17 AM, Sung Hee Park<shpark7@stanford.edu> wrote:
>>> Hi,
>>>
>>> I found my frame buffer is not working while I'm testing the linux
>>> kernel 2.6.38-rc5 on omap3evm, which used to work fine with 2.6.37.
>>>
>>> Kernel command line: mem=128M console=ttyO0,115200n8 noinitrd rw
>>> root=/dev/mmcblk0p2 rootfstype=ext3 rootwait omapfb.rot
>>> ate=3 omapfb.vrfb=y vram=8M earlyprintk=serial,uart0,115200n8
>>> omapdss.debug=1 omapfb.debug=1
>>> OMAPFB: omapfb_init
>>> OMAPFB: omapfb_probe
>>> omapfb omapfb: no driver for display
>>> omapfb omapfb: failed to setup omapfb
It looks like an issue with what you have selected in the menuconfig.
Could you ensure you have DPI and VENC selected, and in displays Generic
DPI panel and sharp-ls panel selected.
Regards,
Archit
next prev parent reply other threads:[~2011-02-18 4:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 3:17 omapfb: no driver for display Sung Hee Park
2011-02-18 3:46 ` Bryan Wu
2011-02-18 4:16 ` Sung Hee Park
2011-02-18 4:27 ` archit taneja [this message]
2011-02-18 6:55 ` Sung Hee Park
2011-02-19 7:41 ` Ming Lei
2011-02-19 9:06 ` Felipe Contreras
2011-02-19 9:24 ` Ming Lei
2011-02-19 9:56 ` Felipe Contreras
2011-02-19 10:00 ` Ming Lei
2011-02-19 10:45 ` archit taneja
2011-02-19 12:40 ` Ming Lei
2011-02-21 2:40 ` Semwal, Sumit
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=4D5DF547.7010703@ti.com \
--to=archit@ti.com \
--cc=bryan.wu@canonical.com \
--cc=linux-omap@vger.kernel.org \
--cc=shpark7@stanford.edu \
--cc=sumit.semwal@ti.com \
/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