Re: rx51: omapfb: no driver for display
On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote: Hi, I've got problems getting a working tty with the mainline 2.6.38 kernel on my Nokia N900. Here is the related output from dmesg: $ grep -E (omapdss|omapfb|acx565akm) dmesg [0.890899] omapdss CORE: clk ick, rate 8300 [0.890930] omapdss CORE: clk dss1_fck, rate 9600 [0.890991] omapdss CORE: clk dss2_fck, rate 1920 [0.891021] omapdss CORE: clk tv_fck, rate 5400 [0.891052] omapdss CORE: clk video_fck, rate 9600 [0.891143] omapdss CORE: initial ctx id 0 [0.950469] omapdss CORE: save context [0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm [0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm [0.950805] omapdss SDI: SDI init [1.004455] omapdss CORE: save context [1.059173] omapdss CORE: save context [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-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 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 display driver directly before. You also need VENC driver for the tv-out: CONFIG_OMAP2_DSS_VENC Granted, DSS could handle this case a bit better, by continuing but refusing to let the user enable the tv-out... Tomi -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: rx51: omapfb: no driver for display
On Mon, Mar 28, 2011 at 09:01:29AM +0300, Tomi Valkeinen wrote: On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote: Hi, I've got problems getting a working tty with the mainline 2.6.38 kernel on my Nokia N900. Here is the related output from dmesg: $ grep -E (omapdss|omapfb|acx565akm) dmesg [0.890899] omapdss CORE: clk ick, rate 8300 [0.890930] omapdss CORE: clk dss1_fck, rate 9600 [0.890991] omapdss CORE: clk dss2_fck, rate 1920 [0.891021] omapdss CORE: clk tv_fck, rate 5400 [0.891052] omapdss CORE: clk video_fck, rate 9600 [0.891143] omapdss CORE: initial ctx id 0 [0.950469] omapdss CORE: save context [0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm [0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm [0.950805] omapdss SDI: SDI init [1.004455] omapdss CORE: save context [1.059173] omapdss CORE: save context [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-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 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 display driver directly before. You also need VENC driver for the tv-out: CONFIG_OMAP2_DSS_VENC thanks, that fixes the problem. Granted, DSS could handle this case a bit better, by continuing but refusing to let the user enable the tv-out... uhm yes :) But first of all it would help to know which driver is missing. Perhaps something like no driver for display1/venc. -- Sebastian signature.asc Description: Digital signature
RE: rx51: omapfb: no driver for display
-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 Hi, I've got problems getting a working tty with the mainline 2.6.38 kernel on my Nokia N900. Here is the related output from dmesg: $ grep -E (omapdss|omapfb|acx565akm) dmesg [0.890899] omapdss CORE: clk ick, rate 8300 [0.890930] omapdss CORE: clk dss1_fck, rate 9600 [0.890991] omapdss CORE: clk dss2_fck, rate 1920 [0.891021] omapdss CORE: clk tv_fck, rate 5400 [0.891052] omapdss CORE: clk video_fck, rate 9600 [0.891143] omapdss CORE: initial ctx id 0 [0.950469] omapdss CORE: save context [0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm [0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm [0.950805] omapdss SDI: SDI init [1.004455] omapdss CORE: save context [1.059173] omapdss CORE: save context [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- 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 omapfb [Hiremath, Vaibhav] it looks like you do not have all display's connected/selected in you board hook up file. Please refer to the file board-rx51-video.c, where you can find number of displays registered for rx51 platform. In case of rx51, you have 2 registered displays, lcd and TV. Thanks, Vaibhav 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 display driver directly before. [0] http://pkg-n900.alioth.debian.org/kernel/2.6.38/config-2.6.38-1-omap [1] http://pkg-n900.alioth.debian.org/kernel/2.6.38/dmesg -- Sebastian -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
rx51: omapfb: no driver for display
Hi, I've got problems getting a working tty with the mainline 2.6.38 kernel on my Nokia N900. Here is the related output from dmesg: $ grep -E (omapdss|omapfb|acx565akm) dmesg [0.890899] omapdss CORE: clk ick, rate 8300 [0.890930] omapdss CORE: clk dss1_fck, rate 9600 [0.890991] omapdss CORE: clk dss2_fck, rate 1920 [0.891021] omapdss CORE: clk tv_fck, rate 5400 [0.891052] omapdss CORE: clk video_fck, rate 9600 [0.891143] omapdss CORE: initial ctx id 0 [0.950469] omapdss CORE: save context [0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm [0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm [0.950805] omapdss SDI: SDI init [1.004455] omapdss CORE: save context [1.059173] omapdss CORE: save context [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-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 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 display driver directly before. [0] http://pkg-n900.alioth.debian.org/kernel/2.6.38/config-2.6.38-1-omap [1] http://pkg-n900.alioth.debian.org/kernel/2.6.38/dmesg -- Sebastian signature.asc Description: Digital signature
Re: omapfb: no driver for display
Hi, On Sat, Feb 19, 2011 at 6:10 PM, Ming Lei tom.leim...@gmail.com wrote: Hi, 2011/2/19 archit taneja arc...@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 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei tom.leim...@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.00] 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
Hi, Thanks for your reply. 2011/2/19 Felipe Contreras felipe.contre...@gmail.com: On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei tom.leim...@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.00] 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.00] Memory: 1008MB = 1008MB total [0.00] 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
On Sat, Feb 19, 2011 at 11:24 AM, Ming Lei tom.leim...@gmail.com wrote: Hi, Thanks for your reply. 2011/2/19 Felipe Contreras felipe.contre...@gmail.com: On Sat, Feb 19, 2011 at 9:41 AM, Ming Lei tom.leim...@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.00] 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
Hi, 2011/2/19 Felipe Contreras felipe.contre...@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.00] Memory: 1008MB = 1008MB total but if 'vram=8M' is taken, will be [0.00] Memory: 1016MB = 1016MB total You may have a try on your board to confirm it. thanks, -- Lei Ming -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
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 Contrerasfelipe.contre...@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.00] Memory: 1008MB = 1008MB total but if 'vram=8M' is taken, will be [0.00] Memory: 1016MB = 1016MB total You may have a try on your board to confirm it. thanks, -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
Hi, 2011/2/19 archit taneja arc...@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 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
Hi, 2011/2/18 archit taneja arc...@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 Wubryan...@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 Parkshpa...@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.00] 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
omapfb: no driver for display
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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
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 shpa...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Bryan Wu bryan...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
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...@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 shpa...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Bryan Wu bryan...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
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 Wubryan...@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 Parkshpa...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display
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 arc...@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 Wubryan...@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 Parkshpa...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: omapfb: no driver for display error with linux-2.6.37-rc7
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: no driver for display error with linux-2.6.37-rc7 On Dec 27, 2010, at 4:39 AM, Felipe Contreras wrote: [2.175872] omapfb omapfb: no driver for display [Mayuresh]: This clearly shows that there is something went wrong in registering displays. So OMAPFB has not found any registered displays. Try passing omapdss.debug=1, omapfb.debug=1 in your bootargs and the log would be self explanatory. [2.180999] omapfb omapfb: failed to setup omapfb My bootargs are as follows: mmcargs=setenv bootargs console=ttyO2,115200n8 vram=12M omapfb.vram=0:2M omapfb.mode=480x272mr...@60 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Do you have a proper CONFIG_OMAP2_VRAM_SIZE in your config? I've set the VRAM to 12, but the number of framebuffers to 1. Should it be 1 ? [Mayuresh]: No that should not matter. 12MB of vram for 1 FB is fine. And your bootargs state that you need 480*272*2 Bytes of memory. So 12 MB of total VRAM size is more than enough. But your bootargs state that you are providing only 2MB to FB0. Please try using omapfb.vram=0:5M. But if the problem is with the memory then OMAPFB would throw an error: Failed to allocate memory. (Yet your kernel execution has not reached there). CONFIG_OMAP2_VRAM_SIZE=12 CONFIG_FB_OMAP2=y CONFIG_FB_OMAP2_NUM_FBS=1 I've pasted a section of my .config file below. This is with omap2plus_defconfig, for a custom beagleboard. # # Graphics support # # CONFIG_DRM is not set # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_ARMCLCD is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_TMIO is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set CONFIG_OMAP2_VRAM=y CONFIG_OMAP2_VRFB=y CONFIG_OMAP2_DSS=y CONFIG_OMAP2_VRAM_SIZE=12 CONFIG_OMAP2_DSS_DEBUG_SUPPORT=y # CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set CONFIG_OMAP2_DSS_DPI=y # CONFIG_OMAP2_DSS_RFBI is not set CONFIG_OMAP2_DSS_VENC=y # CONFIG_OMAP2_DSS_SDI is not set # CONFIG_OMAP2_DSS_DSI is not set # CONFIG_OMAP2_DSS_FAKE_VSYNC is not set CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0 CONFIG_FB_OMAP2=y # CONFIG_FB_OMAP2_DEBUG_SUPPORT is not set CONFIG_FB_OMAP2_NUM_FBS=1 # # OMAP2/3 Display Device Drivers # # CONFIG_PANEL_GENERIC is not set # CONFIG_PANEL_SHARP_LS037V7DW01 is not set # CONFIG_PANEL_SHARP_LQ043T1DG01 is not set # CONFIG_PANEL_TOPPOLY_TDO35S is not set # CONFIG_PANEL_TPO_TD043MTEA1 is not set [Mayuresh]: I guess, you need to enable atleast one panel driver over here. Try enabling PANEL_GENERIC or SHARP_LS037V7DW01. CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_L4F00242T03 is not set # CONFIG_LCD_LMS283GF05 is not set # CONFIG_LCD_LTV350QV is not set # CONFIG_LCD_TDO24M is not set # CONFIG_LCD_VGG2432A4 is not set CONFIG_LCD_PLATFORM=y # CONFIG_LCD_S6E63M0 is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_GENERIC=y # CONFIG_BACKLIGHT_ADP8860 is not set # # Display device support # CONFIG_DISPLAY_SUPPORT=y # # Display hardware drivers # # # Console display driver support # CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set # CONFIG_FONT_MINI_4x6 is not set # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # CONFIG_LOGO is not set Elvis Dowson -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info
Re: omapfb: no driver for display error with linux-2.6.37-rc7
On Mon, Dec 27, 2010 at 12:10 AM, Elvis Dowson elvis.dow...@mac.com 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 omapfb My bootargs are as follows: mmcargs=setenv bootargs console=ttyO2,115200n8 vram=12M omapfb.vram=0:2M omapfb.mode=480x272mr...@60 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Do you have a proper CONFIG_OMAP2_VRAM_SIZE in your config? -- Felipe Contreras -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: omapfb: no driver for display error with linux-2.6.37-rc7
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=12M omapfb.vram=0:2M omapfb.mode=480x272mr...@60 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Do you have a proper CONFIG_OMAP2_VRAM_SIZE in your config? I've set the VRAM to 12, but the number of framebuffers to 1. Should it be 1 ? CONFIG_OMAP2_VRAM_SIZE=12 CONFIG_FB_OMAP2=y CONFIG_FB_OMAP2_NUM_FBS=1 I've pasted a section of my .config file below. This is with omap2plus_defconfig, for a custom beagleboard. # # Graphics support # # CONFIG_DRM is not set # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_ARMCLCD is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_TMIO is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set CONFIG_OMAP2_VRAM=y CONFIG_OMAP2_VRFB=y CONFIG_OMAP2_DSS=y CONFIG_OMAP2_VRAM_SIZE=12 CONFIG_OMAP2_DSS_DEBUG_SUPPORT=y # CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set CONFIG_OMAP2_DSS_DPI=y # CONFIG_OMAP2_DSS_RFBI is not set CONFIG_OMAP2_DSS_VENC=y # CONFIG_OMAP2_DSS_SDI is not set # CONFIG_OMAP2_DSS_DSI is not set # CONFIG_OMAP2_DSS_FAKE_VSYNC is not set CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0 CONFIG_FB_OMAP2=y # CONFIG_FB_OMAP2_DEBUG_SUPPORT is not set CONFIG_FB_OMAP2_NUM_FBS=1 # # OMAP2/3 Display Device Drivers # # CONFIG_PANEL_GENERIC is not set # CONFIG_PANEL_SHARP_LS037V7DW01 is not set # CONFIG_PANEL_SHARP_LQ043T1DG01 is not set # CONFIG_PANEL_TOPPOLY_TDO35S is not set # CONFIG_PANEL_TPO_TD043MTEA1 is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_L4F00242T03 is not set # CONFIG_LCD_LMS283GF05 is not set # CONFIG_LCD_LTV350QV is not set # CONFIG_LCD_TDO24M is not set # CONFIG_LCD_VGG2432A4 is not set CONFIG_LCD_PLATFORM=y # CONFIG_LCD_S6E63M0 is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_GENERIC=y # CONFIG_BACKLIGHT_ADP8860 is not set # # Display device support # CONFIG_DISPLAY_SUPPORT=y # # Display hardware drivers # # # Console display driver support # CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set # CONFIG_FONT_MINI_4x6 is not set # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # CONFIG_LOGO is not set Elvis Dowson -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
