On 08.03.2013, at 12:50, Alexander Graf wrote:

On 08.03.2013, at 10:43, Guillaume Gardet wrote:

...

Hi,

in attachment omapdrm log OK (openSUSE 12.2 kernel: 3.4.*) and KO (vanilla kernel 3.9-rc1).

I think, we had a hack for omapdrm for openSUSE 12.2 (forcing 1024x768 because of broken things?).

Alex, it is you who have backported omapdrm on 12.2 kernel. Any idea about that?

Rob, do you have any idea what's going on here?

Once more with the correct email address. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 08.03.2013, at 14:44, Rob Clark wrote:

On Fri, Mar 8, 2013 at 6:53 AM, Alexander Graf wrote:

...

On 08.03.2013, at 12:50, Alexander Graf wrote:

...

On 08.03.2013, at 10:43, Guillaume Gardet wrote:

...

Hi,

in attachment omapdrm log OK (openSUSE 12.2 kernel: 3.4.*) and KO (vanilla kernel 3.9-rc1).

I think, we had a hack for omapdrm for openSUSE 12.2 (forcing 1024x768 because of broken things?).

Alex, it is you who have backported omapdrm on 12.2 kernel. Any idea about that?

Rob, do you have any idea what's going on here?

Once more with the correct email address.

if you take out the video= in the bootargs, does it successfully pick *some* mode?

What kernel version are the good vs bad logs from? Depending on which clock is used for dpi/dvi that could impact which timings are available

The "good" one is from 3.4 + omapdrm backported + the omap4 hack to get more bandwidth. The "bad" one is 3.9-rc1 vanilla. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Fri, Mar 8, 2013 at 8:53 AM, Guillaume Gardet wrote:

Le 08/03/2013 14:48, Alexander Graf a écrit :

...

On 08.03.2013, at 14:44, Rob Clark wrote:

...

On Fri, Mar 8, 2013 at 6:53 AM, Alexander Graf wrote:

...

On 08.03.2013, at 12:50, Alexander Graf wrote:

...

On 08.03.2013, at 10:43, Guillaume Gardet wrote:

...

Hi,

in attachment omapdrm log OK (openSUSE 12.2 kernel: 3.4.*) and KO (vanilla kernel 3.9-rc1).

I think, we had a hack for omapdrm for openSUSE 12.2 (forcing 1024x768 because of broken things?).

Alex, it is you who have backported omapdrm on 12.2 kernel. Any idea about that?

Rob, do you have any idea what's going on here?

Once more with the correct email address.

if you take out the video= in the bootargs, does it successfully pick *some* mode?

No, it does not. I just tried to add video= to check if it would work or not and nothing better.

hmm, ok.. well, I'm without my pandaboard for a week or so (just in the process of moving).. is HDMI working (the other connector)? BR, -R

Guillaume

...

...

What kernel version are the good vs bad logs from? Depending on which clock is used for dpi/dvi that could impact which timings are available

The "good" one is from 3.4 + omapdrm backported + the omap4 hack to get more bandwidth. The "bad" one is 3.9-rc1 vanilla.

Alex

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 09/03/2013 21:57, guillaume.gardet@free.fr a écrit :

----- Rob Clark a écrit :

...

...

Le 08/03/2013 14:48, Alexander Graf a écrit :

...

On 08.03.2013, at 14:44, Rob Clark wrote:

...

On Fri, Mar 8, 2013 at 6:53 AM, Alexander Graf wrote:

...

On 08.03.2013, at 12:50, Alexander Graf wrote:

> On 08.03.2013, at 10:43, Guillaume Gardet wrote: > >> Hi, >> >> in attachment omapdrm log OK (openSUSE 12.2 kernel: 3.4.*) and KO >> (vanilla kernel 3.9-rc1). >> >> I think, we had a hack for omapdrm for openSUSE 12.2 (forcing 1024x768 >> because of broken things?). >> >> Alex, it is you who have backported omapdrm on 12.2 kernel. Any idea >> about that? > Rob, do you have any idea what's going on here? Once more with the correct email address.

if you take out the video= in the bootargs, does it successfully pick *some* mode?

No, it does not. I just tried to add video= to check if it would work or not and nothing better. hmm, ok.. well, I'm without my pandaboard for a week or so (just in

On Fri, Mar 8, 2013 at 8:53 AM, Guillaume Gardet wrote: the process of moving)..

is HDMI working (the other connector)? It as a beagleboard xM rev. B, not a pandaboard.

Ping. Is there any information or things to do to debug it? Guillaume

Guillaume

...

BR, -R

...

Guillaume

...

...

What kernel version are the good vs bad logs from? Depending on which clock is used for dpi/dvi that could impact which timings are available The "good" one is from 3.4 + omapdrm backported + the omap4 hack to get more bandwidth. The "bad" one is 3.9-rc1 vanilla.

Alex

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

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 Guillaume

Tomi

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 21/03/2013 15:37, Tomi Valkeinen a écrit :

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, please? Guillaume

Tomi

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Le 22/03/2013 11:55, 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? Attached. I don't think there's anything there that could affect this.

You use omapfb, not omapdrm. That is why it is working for you. Or you send me the wrong file. Guillaume

Tomi

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 2013-03-22 12:52, Guillaume Gardet wrote:

Le 21/03/2013 15:37, Tomi Valkeinen a écrit :

...

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, 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. So does omapfb work for you? Tomi

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

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 2013-03-28 10:55, Guillaume Gardet wrote:

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.

Hmm, ok. I don't see any changes in the beagle board file regarding the TFP PD gpio for many kernel versions. It would be rather odd if Beagle xM's DVI output has been non-functional for so long. The board file code regarding the gpios is rather confusing, though, and I don't really get it... Could you try, say, v3.8 on your board? With omapfb? Tomi

----- Tomi Valkeinen a écrit :

On 2013-03-28 10:55, Guillaume Gardet wrote:

...

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.

Btw, I earlier said the patches I mentioned fixed the DVI output for my beagleboard. But it can be fixed without any patches, by setting CONFIG_DRM_OMAP_NUM_CRTCS=2.

With a 3.7.10 kernel, we need to create file "/etc/modprobe.d/50-omapdrm.conf" with: softdep omapdrm pre: panel-tfp410 To ensure panel-tfp410 is loaded before omapdrm. With 3.8.6, I get the screen up but it stays black. But I got kernel traces about problems with clock. Maybe related. 3.9 does not boot ATM but it should be something wrong on my side. Guillaume

Tomi

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

----- guillaume gardet a écrit :

----- Tomi Valkeinen a écrit :

...

On 2013-03-28 10:55, Guillaume Gardet wrote:

...

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.

Btw, I earlier said the patches I mentioned fixed the DVI output for my beagleboard. But it can be fixed without any patches, by setting CONFIG_DRM_OMAP_NUM_CRTCS=2.

With a 3.7.10 kernel, we need to create file "/etc/modprobe.d/50-omapdrm.conf" with: softdep omapdrm pre: panel-tfp410

To ensure panel-tfp410 is loaded before omapdrm.

Modprobe config seems to help but sometime it still does not work. When it does not work, I get lots of "omap_i2c omap_i2c.3: timeout waiting for bus ready" in dmesg. i2c3 is used to communicate with monitor to determine configuration settings. i2c problem seems known according to this thread: http://www.spinics.net/lists/linux-omap/msg79920.html Any idea how to fix the i2c problem? Maybe will fix as well omapdrm. Please note that omapfb is working fine. Guillaume

With 3.8.6, I get the screen up but it stays black. But I got kernel traces about problems with clock. Maybe related.

3.9 does not boot ATM but it should be something wrong on my side.

Guillaume

...

Tomi

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org