Re: Which git to clone for testing prior to submitting bugs?

[johnea <me@johnea.net>]

[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]

On 09/28/2012 12:46 PM, linux@johnea.net wrote:
> On 09/28/2012 12:18 PM, Robert Nelson wrote:
>> Ah, so looking at the config, ARCH switched to omapdrm... It kinda
>> works in v3.5.x, but i'd wait till a few more releases...
>>
>> So, based on that config, they have both "CONFIG_FB_OMAP2" and
>> "CONFIG_DRM_OMAP" enabled.. That's a no-no...
>>
>> CONFIG_DRM_OMAP
>> http://cateee.net/lkddb/web-lkddb/DRM_OMAP.html
>> depends on: ( CONFIG_DRM&&   ! CONFIG_CONFIG_FB_OMAP2 )&&   (
>> CONFIG_ARCH_OMAP2PLUS )
>>
>> Option 1: Stay with omapfb
>>
>> CONFIG_FB_OMAP2=m ->   CONFIG_FB_OMAP2=y
>> disable: CONFIG_DRM_OMAP
>>
>> Option 2: Go Experimental route with omapdrm
>>
>> CONFIG_DRM_OMAP=m
>> CONFIG_DRM_OMAP_NUM_CRTCS=1
>>
>> disable: CONFIG_FB_OMAP2
>>
  
> I'll follow up once I'm running the new version...

Good morning,

We opted for the "Stay with omapfb", and disabled CONFIG_DRM_OMAP.

Now the dev tree is showing all 3 fb devices, but still no video out 8-(

Boot messages include:

[root@apm002 johnea]# dmesg | grep omapfb
[    0.000000] Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=spidev camera=none vram=18MB omapfb.mode=dvi omapfb.vram=0:6M,1:6M,2:6M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rootfstype=ext2 rootwait
[    3.165069] omapfb omapfb: no driver for display: dvi
[    3.165130] omapfb omapfb: no driver for display: lcd
[    3.165161] omapfb omapfb: cannot parse default modes

The "cannot parse default modes" message was eliminated by removing "omapfb.vram=0:6M,1:6M,2:6M" from the boot params.

This made me wonder if the omapfb boot params expected by 3.5.4 had changed. So I tried a bunch of different permutations of boot params, with no effect other than eliminating the "default modes" message mentioned above.

I tried digging into the source to determine currently accepted omapfb boot params, but had no success.

It seems like we're really close. The latest config.gz and tar'd dmesg from the running system are attached.

Thank You again! for any advise on config, boot param, or other changes that could make beagle DVI video work with 3.5.4...

johnea

[-- Attachment #2: config-3.5.4-archarm-3.gz --]
[-- Type: application/gzip, Size: 25137 bytes --]

[-- Attachment #3: dmesg-3.5.4-3.gz --]
[-- Type: application/gzip, Size: 6911 bytes --]