linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Hague <jim.hague@acm.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [2.6.11 Permedia-2 Framebuffer] driver broken (?).
Date: Tue, 22 Mar 2005 09:41:06 -0000 (GMT)	[thread overview]
Message-ID: <XFMail.20050322094106.jim.hague@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0503220030230.12537@poirot.grange>

On 21-Mar-2005 Guennadi Liakhovetski wrote:
> On Mon, 21 Mar 2005, Andrew Morton wrote:
>> Guennadi, could you please confirm that
>> 
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.
>> 12-rc1-mm1/broken-out/pm2fb-x-and-vt-switching-crash-fix.patch
>> 
>> fixes this one?
> 
> As discussed with Jim on linux-fbdev-devel this patch fixes the vt / X 
> switching problem. We still don't know why starting with 2.4.11 I have to 
> switch CONFIG_FB_PM2_FIFO_DISCONNECT off to restore colours / images.
> [...]
> I traced this breakage down to the patch to 
> pm2fb.c after 2.6.10-rc2. Jim wanted to try to reproduce this problem with 
> my fb-geometry / colour settings, but I haven't heard from him since then, 

FIrst off, so we're all clear, the problem with vt/X switching was definitely a
pm2fb bug exposed by chages in fbcon, and is definitely fixed by the above
patch. Please apply.

As to Guennadi's problem with colours and images, I've been trying to
reproduce locally without success, hence silence. My pm2fb-on-Sparc
correspondent hasn't seen this either, and I've had no other reports.

I have one possible clue, which I'll pursue with Guennadi off-list.

-- 
Jim Hague - jim.hague@acm.org          Never trust a computer you can't lift.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-22  9:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 23:53 [2.6.11 Permedia-2 Framebuffer] driver broken (?) Guennadi Liakhovetski
2005-03-06  9:52 ` Guennadi Liakhovetski
2005-03-06 13:30   ` Guennadi Liakhovetski
2005-03-07 19:44 ` Jim Hague
2005-03-07 20:24   ` Guennadi Liakhovetski
2005-03-07 22:08     ` Jim Hague
2005-03-08 23:08       ` Jim Hague
2005-03-09 23:48         ` Guennadi Liakhovetski
2005-03-21 22:59 ` Andrew Morton
2005-03-21 23:37   ` Antonino A. Daplas
2005-03-21 23:40   ` Guennadi Liakhovetski
2005-03-22  9:41     ` Jim Hague [this message]
2005-05-25 23:53       ` Andrew Morton
2005-05-26 22:38         ` Guennadi Liakhovetski
2005-05-27 23:31           ` Guennadi Liakhovetski
2005-05-28 10:46             ` Jim Hague
2005-06-09 14:35             ` Jim Hague
2005-06-10  5:30               ` Guennadi Liakhovetski

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=XFMail.20050322094106.jim.hague@acm.org \
    --to=jim.hague@acm.org \
    --cc=akpm@osdl.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).