From: archit taneja <archit@ti.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Sung Hee Park <shpark7@stanford.edu>,
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: Sat, 19 Feb 2011 16:15:15 +0530 [thread overview]
Message-ID: <4D5F9F3B.6000507@ti.com> (raw)
In-Reply-To: <AANLkTinUO69HYZUUQ-NzyB_LDLvvfBnLqtSDKimu0xy3@mail.gmail.com>
Hi,
Which board are you on? For all the display devices you add in the board
file, you should have the corresponding drivers in the menuconfig set also.
For example, in board3430-sdp.c, we add a sharp ls, a dvi and venc
panel. We therefore select sharpls and generic dpi panel in menuconfig.
and at least DPI and VENC in the interfaces menu.
On Saturday 19 February 2011 03:30 PM, Ming Lei wrote:
> Hi,
>
> 2011/2/19 Felipe Contreras<felipe.contreras@gmail.com>:
>> Are you sure? AFAIK early_param is executed _after_ memory blocks are reserved.
>
> Yes, I am sure.
>
> If 'vram=16M' is passed in, I can find the below:
>
> [ 0.000000] Memory: 1008MB = 1008MB total
>
> but if 'vram=8M' is taken, will be
>
> [ 0.000000] Memory: 1016MB = 1016MB total
>
> You may have a try on your board to confirm it.
>
>
> thanks,
next prev parent reply other threads:[~2011-02-19 10:43 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
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 [this message]
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=4D5F9F3B.6000507@ti.com \
--to=archit@ti.com \
--cc=bryan.wu@canonical.com \
--cc=felipe.contreras@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=shpark7@stanford.edu \
--cc=sumit.semwal@ti.com \
--cc=tom.leiming@gmail.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