am=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
I found Kevin reported the similar issue here (
http://www.spinics.net/lists/linux-omap/msg44384.html ), and wondering
1
> OMAPFB: omapfb_init
> OMAPFB: omapfb_probe
> omapfb omapfb: no driver for display
> omapfb omapfb: failed to setup omapfb
>
> I found Kevin reported the similar issue here (
> http://www.spinics.net/lists/linux-omap/msg44384.html ), and wondering
> about whether I has been patch
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_
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 displa
h 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.
l 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
On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei wrote:
>> 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.
>
> Even after enabling all this options above, there is s
Hi,
Thanks for your reply.
2011/2/19 Felipe Contreras :
> On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei wrote:
>>> 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 selec
On Sat, Feb 19, 2011 at 11:24 AM, Ming Lei wrote:
> Hi,
>
> Thanks for your reply.
>
> 2011/2/19 Felipe Contreras :
>> On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei wrote:
It looks like an issue with what you have selected in the menuconfig. Could
you ensure you have DPI and VENC selected,
Hi,
2011/2/19 Felipe Contreras :
> 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.00] Memory: 1008MB = 1008MB total
but if 'vram=8M' is taken, will be
[0.00] Memory
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.
Hi,
2011/2/19 archit taneja :
> 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.
Pandaboard.
> For example, in board3430-sdp.c, we add a sharp ls, a dvi and venc panel. We
> therefore se
Hi,
On Sat, Feb 19, 2011 at 6:10 PM, Ming Lei wrote:
> Hi,
>
> 2011/2/19 archit taneja :
>> 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.
>
> Pandaboard.
DVI support for pandaboard
.303924] omapfb omapfb: no driver for display
[1.304016] omapfb omapfb: failed to setup omapfb
You can find the full dmesg and the full kernel config at [0] and
[1]. Can you tell me the reason for the "no driver for display"
message? I thought acx565akm has been registered as displ
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Sebastian Reichel
> Sent: Sunday, March 27, 2011 8:09 AM
> To: linux-omap@vger.kernel.org
> Subject: rx51: "omapfb: no driver for display"
>
for device display0
> [1.130096] omapdss CORE: bus_match. dev display1/venc, drv panel-acx565akm
> [1.303741] OMAPFB: omapfb_init
> [1.303894] OMAPFB: omapfb_probe
> [1.303924] omapfb omapfb: no driver for display
> [1.304016] omapfb omapfb: failed to setup omapf
> > [1.113830] omapdss CORE: save context
> > [1.129608] acx565akm spi1.2: omapfb: acx565akm rev 8b LCD detected
> > [1.130065] omapdss CORE: probe done for device display0
> > [1.130096] omapdss CORE: bus_match. dev display1/venc, drv
> > panel-ac
Hi,
I'm getting the following error with linux-2.6.37-rc7. Is there a
.config setting that I'm missing?
[2.175872] omapfb omapfb: no driver for display
[2.180999] omapfb omapfb: failed to setup omapfb
My bootargs are as follows:
mmcargs=setenv bootargs console=ttyO
On Mon, Dec 27, 2010 at 12:10 AM, Elvis Dowson wrote:
> I'm getting the following error with linux-2.6.37-rc7. Is there a
> .config setting that I'm missing?
>
> [ 2.175872] omapfb omapfb: no driver for display
> [ 2.180999] omapfb omapfb: failed to setup o
On Dec 27, 2010, at 4:39 AM, Felipe Contreras wrote:
>> [2.175872] omapfb omapfb: no driver for display
>> [2.180999] omapfb omapfb: failed to setup omapfb
>>
>> My bootargs are as follows:
>>
>> mmcargs=setenv bootargs console=ttyO2,115200n8 vram=
Felipe, Elvis,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Elvis Dowson
> Sent: Monday, December 27, 2010 11:30 AM
> To: Felipe Contreras
> Cc: Linux OMAP Mailing List
> Subject: Re: omapfb:
21 matches
Mail list logo
