omapfb: no driver for display

omapfb: no driver for display

[Sung Hee Park]

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

I found Kevin reported the similar issue here (
http://www.spinics.net/lists/linux-omap/msg44384.html ), and wondering
about whether I has been patched. Sumit, could you please let me know
if one of your recent patches would solve this problem? If it does,
which patches am I supposed to apply on 2.6.38-rc5?


Regards,
Sung Hee

Re: omapfb: no driver for display

[Bryan Wu]

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
>
> I found Kevin reported the similar issue here (
> http://www.spinics.net/lists/linux-omap/msg44384.html ), and wondering
> about whether I has been patched. Sumit, could you please let me know
> if one of your recent patches would solve this problem? If it does,
> which patches am I supposed to apply on 2.6.38-rc5?
>
>
> Regards,
> Sung Hee
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Bryan Wu <bryan.wu@canonical.com>
Kernel Developer    +86.138-1617-6545 Mobile
Ubuntu Kernel Team
Canonical Ltd.      www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[Sung Hee Park]

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
>>
>> I found Kevin reported the similar issue here (
>> http://www.spinics.net/lists/linux-omap/msg44384.html ), and wondering
>> about whether I has been patched. Sumit, could you please let me know
>> if one of your recent patches would solve this problem? If it does,
>> which patches am I supposed to apply on 2.6.38-rc5?
>>
>>
>> Regards,
>> Sung Hee
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
>
> --
> Bryan Wu <bryan.wu@canonical.com>
> Kernel Developer    +86.138-1617-6545 Mobile
> Ubuntu Kernel Team
> Canonical Ltd.      www.canonical.com
> Ubuntu - Linux for human beings | www.ubuntu.com
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[archit taneja]

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

Re: omapfb: no driver for display

[Sung Hee Park]

Thanks for your suggestions. I've selected DPI and VENC options, and
Sharp LS LCD Panel in OMAP2/3 Display Device Drivers section, but not
Generic Panel. Enabling Generic Panel made it work. Thanks!

Regards,
Sung Hee



On Thu, Feb 17, 2011 at 8:27 PM, archit taneja <archit@ti.com> wrote:
> 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[Ming Lei]

Hi,

2011/2/18 archit taneja <archit@ti.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.

Even after enabling all this options above, there is still the failure
message on my pandaboard(2.6.38-rc5-next-20110217):

[    0.000000] Kernel command line: console=ttyO2,115200n8 vram=16M
root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext3 rootwait
......
[    2.847625] omapfb omapfb: no displays
[    2.851562] omapfb omapfb: failed to setup omapfb
[    2.856719] omapfb: probe of omapfb failed with error -22


thanks,
-- 
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[Felipe Contreras]

On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei <tom.leiming@gmail.com> 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 still the failure
> message on my pandaboard(2.6.38-rc5-next-20110217):
>
> [    0.000000] Kernel command line: console=ttyO2,115200n8 vram=16M
> root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext3 rootwait
> ......
> [    2.847625] omapfb omapfb: no displays
> [    2.851562] omapfb omapfb: failed to setup omapfb
> [    2.856719] omapfb: probe of omapfb failed with error -22

Note that the command line parameters are ignored since 2.6.36, you
need to specify CONFIG_OMAP2_VRAM_SIZE.

Cheers.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[Ming Lei]

Hi,

Thanks for your reply.

2011/2/19 Felipe Contreras <felipe.contreras@gmail.com>:
> On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei <tom.leiming@gmail.com> 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 still the failure
>> message on my pandaboard(2.6.38-rc5-next-20110217):
>>
>> [    0.000000] Kernel command line: console=ttyO2,115200n8 vram=16M
>> root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext3 rootwait
>> ......
>> [    2.847625] omapfb omapfb: no displays
>> [    2.851562] omapfb omapfb: failed to setup omapfb
>> [    2.856719] omapfb: probe of omapfb failed with error -22
>
> Note that the command line parameters are ignored since 2.6.36, you

I don't think the 'vram=16M' is ignored by kernel, which can be found below:

[    0.000000] Memory: 1008MB = 1008MB total
[    0.000000] Memory: 1006160k/1006160k available, 42416k reserved,
245760K highmem

The 16M bytes is reserved by the para vram=16M'.

> need to specify CONFIG_OMAP2_VRAM_SIZE.

Same with before even CONFIG_OMAP2_VRAM_SIZE is configured
as 16M Bytes.

thanks,
-- 
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[Felipe Contreras]

On Sat, Feb 19, 2011 at 11:24 AM, Ming Lei <tom.leiming@gmail.com> wrote:
> Hi,
>
> Thanks for your reply.
>
> 2011/2/19 Felipe Contreras <felipe.contreras@gmail.com>:
>> On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei <tom.leiming@gmail.com> 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 still the failure
>>> message on my pandaboard(2.6.38-rc5-next-20110217):
>>>
>>> [    0.000000] Kernel command line: console=ttyO2,115200n8 vram=16M
>>> root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext3 rootwait
>>> ......
>>> [    2.847625] omapfb omapfb: no displays
>>> [    2.851562] omapfb omapfb: failed to setup omapfb
>>> [    2.856719] omapfb: probe of omapfb failed with error -22
>>
>> Note that the command line parameters are ignored since 2.6.36, you
>
> I don't think the 'vram=16M' is ignored by kernel, which can be found below:

Are you sure? AFAIK early_param is executed _after_ memory blocks are reserved.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: omapfb: no driver for display

[Ming Lei]

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,
-- 
Lei Ming

Re: omapfb: no driver for display

[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.

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,

Re: omapfb: no driver for display

[Ming Lei]

Hi,

2011/2/19 archit taneja <archit@ti.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.

Pandaboard.

> 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.

I also selected all the options above.

thanks,
-- 
Lei Ming

Re: omapfb: no driver for display

[Semwal, Sumit]

Hi,

On Sat, Feb 19, 2011 at 6:10 PM, Ming Lei <tom.leiming@gmail.com> wrote:
> Hi,
>
> 2011/2/19 archit taneja <archit@ti.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.
>
> Pandaboard.
DVI support for pandaboard is slated to be in for 2.6.39. There are
around 6-7 patch series which enable it. You could look at the top
patches at:

git://dev.omapzoom.org/pub/scm/anand/linux-omap-usb.git, branch:
display-patches-for-v2.6.38-rc4.

Best regards,
~Sumit.
>
>> 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.
>
> I also selected all the options above.
>
> thanks,
> --
> Lei Ming
>