All of lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <archit@ti.com>
To: sboyce@blueyonder.co.uk
Cc: linux-omap@vger.kernel.org
Subject: Re: Pandaboard Kernel 3.8.13.6 no HDMI
Date: Tue, 3 Sep 2013 11:26:28 +0530	[thread overview]
Message-ID: <52257A0C.5040005@ti.com> (raw)
In-Reply-To: <522530DB.9080706@blueyonder.co.uk>

Hi,

There are a couple of options here.

On Tuesday 03 September 2013 06:14 AM, Sid Boyce wrote:
> The Pandaboard list seems dormant so I am seeking help here.
>
> The previous kernel with HDMI video output was 3.2.7x5.
>
> I built and installed this new kernel with this xorg.conf, it does not
> work.
> Section "Device"
>          Identifier      "fb0"
>          Driver "omapfb"
>          Option "fb" "/dev/fb0"
> EndSection

Looks like the problem below was buffer allocation. You could use 
omapdrm instead of omapfb which should allocate buffers successfully. I 
think the omapdrm drivers was in staging at that point. You could search 
for it in the .config, and set NUM_CRTCS to 2.

>
> Section "Monitor"
>          Identifier "HP"
>          ModeLine "1920x1080" 148.501  1920 2008 2052 2200  1080 1084 1089
> 1125 -HSync -VSync
> EndSection
>
> Section "Screen"
>          Identifier      "screen0"
>          Device  "fb0"
>          Monitor "HP"
>          DefaultDepth    16
>          SubSection "Display"
>                  Depth   16
>                  Modes   "1920x1080" "800x480"
>          EndSubSection
> EndSection
>
> Mode "800x480"
>      # D: 29.001 MHz, H: 31.251 kHz, V: 59.525 Hz
>      DotClock 29.002
>      HTimings 800 840 888 928
>      VTimings 480 503 506 525
>      Flags    "-HSync" "-VSync"
> EndMode
>
> Using the udlfb driver and an xorg.conf for the Lilliput USB 7" screen
> there is no problem, LXDE is up and running and CRTL-ALT-F1 etc. all
> OK,  but I need the USB screen for the Beaglebone.
>
> root@panda:/etc/X11# lsmod
> Module                  Size  Used by
> omapdss               253516  0
> udlfb                  17703  2
> bluetooth             221172  6
> snd_usb_audio         115881  0
> snd_usbmidi_lib        18680  1 snd_usb_audio
> snd_rawmidi            21747  1 snd_usbmidi_lib
> snd_hwdep               6190  1 snd_usb_audio
> snd_pcm_oss            42617  0
> snd_mixer_oss          14244  1 snd_pcm_oss
> snd_pcm                84961  2 snd_pcm_oss,snd_usb_audio
> snd_page_alloc          5296  1 snd_pcm
> snd_timer              20277  1 snd_pcm
> snd                    61483  8
> snd_pcm_oss,snd_usb_audio,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_usbmidi_lib,snd_mixer_oss
>
> soundcore               7260  1 snd
> ehci_hcd               54613  0
> ohci_hcd               31836  0
> root@panda:/etc/X11# ls /lib/modules/3.8.13.6x-dirty/kernel/drivers/video/
> backlight  omap2  udlfb.ko
> root@panda:/etc/X11# ll
> /lib/modules/3.8.13.6x-dirty/kernel/drivers/video/omap2/omapfb
> total 64
> drwxr-xr-x 2 root root  4096 Sep  2 10:18 ./
> drwxr-xr-x 5 root root  4096 Sep  2 10:18 ../
> -rw-r--r-- 1 root root 56916 Sep  2 02:52 omapfb.ko
> root@panda:/etc/X11# modprobe omapfb
> ERROR: could not insert 'omapfb': No such device
> root@panda:/etc/X11# insmod
> /lib/modules/3.8.13.6x-dirty/kernel/drivers/video/omap2/omapfb/omapfb.ko
> Error: could not insert module
> /lib/modules/3.8.13.6x-dirty/kernel/drivers/video/omap2/omapfb/omapfb.ko: No
> such device
> root@panda:/1/ubuntu-raring# grep CONFIG_FB .config
> CONFIG_FB=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_SYS_FILLRECT=y
> CONFIG_FB_SYS_COPYAREA=y
> CONFIG_FB_SYS_IMAGEBLIT=y
> CONFIG_FB_SYS_FOPS=y
> CONFIG_FB_DEFERRED_IO=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_TILEBLITTING=y
> CONFIG_FB_ARMCLCD=y
> CONFIG_FB_UVESA=y
> CONFIG_FB_TMIO=y
> CONFIG_FB_TMIO_ACCELL=y
> CONFIG_FB_UDL=m
> CONFIG_FB_VIRTUAL=y
> CONFIG_OMAP2_VRFB=y
> CONFIG_OMAP2_DSS_RFBI=y
> CONFIG_FB_OMAP2=m
> CONFIG_FB_OMAP2_DEBUG_SUPPORT=y
> CONFIG_FB_OMAP2_NUM_FBS=3

The other option is to figure out why it's not working with omapfb. 
Could you add a CONFIG_OMAP2_DSS_DEBUG in order to get additional DSS 
prints?

>
> root@panda:/etc/X11# grep HDMI /1/ubuntu-raring/.config
> CONFIG_OMAP4_DSS_HDMI=y
>
> ONFIG_ARCH_OMAP4=y
> CONFIG_MACH_OMAP4_PANDA=y
>
> Displayed on the serial console
> =======================
> root@panda:~# [34587.439270] omapdss error: timeout reading edid
> [34587.445220] omapfb omapfb: failed to allocate framebuffer
> [34587.450958] omapfb omapfb: failed to allocate fbmem
> [34587.456604] omapfb omapfb: failed to setup omapfb
> [34587.461853] failed to register omapfb driver

The debug prints will help with the edid timeout. About the allocation 
of buffers, I think it should work if you enable CMA. And set 
CONFIG_CMA_SIZE_MBYTES to say, 24 Mb. That should allocate the buffers 
successfully.

Archit


      reply	other threads:[~2013-09-03  5:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  0:44 Pandaboard Kernel 3.8.13.6 no HDMI Sid Boyce
2013-09-03  5:56 ` Archit Taneja [this message]

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=52257A0C.5040005@ti.com \
    --to=archit@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sboyce@blueyonder.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.