All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Rottmann <JRottmann@LiPPERT-AT.de>
To: Andres Salomon <dilinger@queued.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	linux-geode@bombadil.infradead.org, linux-kernel@vger.kernel.org,
	jordan.crouse@amd.com, Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org
Subject: Re: lxfb driver regression
Date: Tue, 13 May 2008 12:29:23 +0200	[thread overview]
Message-ID: <48296D83.3020007@LiPPERT-AT.de> (raw)
In-Reply-To: <20080512185148.104fc4c3@ephemeral>

I wrote:
> > Yes, of course that was my first idea, too. [...] But I'm
> > almost prepared to bet this is not the root of the evil.

Andres Salomon wrote:
> It works much better on an XO, so I've ack'd it.

Oops. Lucky I didn't bet, I'd have lost!
But it wasn't all fair, this strange fb resolution switch got me off track. ;-)


But it still surprises me that you get a white screen if you run the XO panel
with the specified frequency, and it only works as long as this is unavailable.
Are you sure the dotclock setting in olpc_dcon_modedb[] is correct?

Anyway, glad the problem is solved, now.

Again, many thanks for your help!
Jens

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

WARNING: multiple messages have this Message-ID (diff)
From: Jens Rottmann <JRottmann@LiPPERT-AT.de>
To: Andres Salomon <dilinger@queued.net>
Cc: jordan.crouse@amd.com, linux-kernel@vger.kernel.org,
	linux-geode@bombadil.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	torvalds@linux-foundation.org
Subject: Re: lxfb driver regression
Date: Tue, 13 May 2008 12:29:23 +0200	[thread overview]
Message-ID: <48296D83.3020007@LiPPERT-AT.de> (raw)
In-Reply-To: <20080512185148.104fc4c3@ephemeral>

I wrote:
> > Yes, of course that was my first idea, too. [...] But I'm
> > almost prepared to bet this is not the root of the evil.

Andres Salomon wrote:
> It works much better on an XO, so I've ack'd it.

Oops. Lucky I didn't bet, I'd have lost!
But it wasn't all fair, this strange fb resolution switch got me off track. ;-)


But it still surprises me that you get a white screen if you run the XO panel
with the specified frequency, and it only works as long as this is unavailable.
Are you sure the dotclock setting in olpc_dcon_modedb[] is correct?

Anyway, glad the problem is solved, now.

Again, many thanks for your help!
Jens

  reply	other threads:[~2008-05-13 10:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  1:08 lxfb driver regression Andres Salomon
2008-05-08  1:08 ` Andres Salomon
2008-05-08  1:11 ` Andrew Morton
2008-05-08  1:11   ` Andrew Morton
2008-05-08 13:56 ` Jens Rottmann
2008-05-08 13:56   ` Jens Rottmann
2008-05-08 14:48   ` Andres Salomon
2008-05-09 10:33     ` Jens Rottmann
2008-05-09 10:33       ` Jens Rottmann
2008-05-08 15:06   ` Jordan Crouse
2008-05-12 22:51   ` Andres Salomon
2008-05-12 22:51     ` Andres Salomon
2008-05-13 10:29     ` Jens Rottmann [this message]
2008-05-13 10:29       ` Jens Rottmann
2008-05-13 15:48     ` Linus Torvalds
2008-05-13 16:35       ` Andrew Morton
2008-05-13 17:50         ` Andres Salomon
2008-05-13 17:50           ` Andres Salomon
2008-05-13 17:55           ` Andres Salomon
2008-05-13 17:55             ` Andres Salomon
2008-05-13 20:05           ` Jordan Crouse
2008-05-13 20:05             ` Jordan Crouse
2008-05-14 12:44           ` Jens Rottmann
2008-05-14 12:44             ` Jens Rottmann

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=48296D83.3020007@LiPPERT-AT.de \
    --to=jrottmann@lippert-at.de \
    --cc=akpm@linux-foundation.org \
    --cc=dilinger@queued.net \
    --cc=jordan.crouse@amd.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-geode@bombadil.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.