Le 26/03/2013 16:53, Guillaume Gardet a écrit :
Le 22/03/2013 14:41, Tomi Valkeinen a écrit :
On 2013-03-22 12:52, Guillaume Gardet wrote:
On 2013-03-21 16:16, Guillaume Gardet wrote:
Le 21/03/2013 15:08, Tomi Valkeinen a écrit :
On 2013-03-21 16:00, Guillaume Gardet wrote:
> Ping. > Is there any information or things to do to debug it? Can you summarize the problem? I couldn't figure it out from the posts... On a Beagleboard xM rev. B, omapdrm does not output anything on my screen (screen goes in power save mode) with vanilla kernel 3.9-rc1 whereas it did work with openSUSE 12.2 kernel (3.4*).
First post with logs: http://lists.opensuse.org/opensuse-arm/2013-03/msg00042.html * kernel 3.4: omapdrm OK * kernel 3.9-rc1 : omapdrm KO Ok. I can repro on -rc3 with beagle.
I applied the attached patches, that have been sent to mailing list. This seemed to fix it. Can you try them out? I didn't study which of them actually fixes this issue, though (I don't know much about omapdrm). It does not fix the problem for me. Could you send me your config file,
Le 21/03/2013 15:37, Tomi Valkeinen a écrit : please? I tested it again. Here's my kernel config, with DSS and DRM built-in.
After applying the patches, I get penguin on the screen on boot, and this on the console:
[ 3.831115] omapdrm omapdrm.0: DMM not available, disable DMM support [ 3.845336] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 3.852569] [drm] No driver support for vblank timestamp query. [ 3.930511] Console: switching to colour frame buffer device 160x60 [ 3.958435] omapdrm omapdrm.0: fb0: omapdrm frame buffer device [ 3.964843] omapdrm omapdrm.0: registered panic notifier [ 3.970611] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0
The resolution is 1280x960, though... I don't know why it picked up such a low resolution. And it's a beagle, not beagle xM.
I have still no ouput but now it uses 1280x1024 as resolution (on a 1440x900 screen).
So does omapfb work for you?
Not tried with 3.9-rc3 but a previous kernel version was OK with omapfb and KO with omapdrm.
Guillaume
Tomi
I think I identified the problem. The TFP410 (dvi chip) is kept in power down state (PD_n pin). I verified it on hardware, the pin is in reset state (0 V) with recent kernels, whereas it is in normal state (3.3 V) with older kernels. I need to dig a bit further to know where is the problem in the code. Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org