linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Hague <jim.hague@acm.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Andrew Morton <akpm@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [2.6.11 Permedia-2 Framebuffer] driver broken (?).
Date: Sat, 28 May 2005 11:46:22 +0100 (BST)	[thread overview]
Message-ID: <XFMail.20050528114622.jim.hague@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0505280126280.22226@poirot.grange>

On 27-May-2005 Guennadi Liakhovetski wrote:
>> On Wed, 25 May 2005, Andrew Morton wrote:
>> > Guys, did all these things get fixed up in 2.6.12-rc5?
>> 
>> At least I don't see the fix we discussed with Jim included. I'll 
>> test-boot tomorrow. Anyway, I seem to be the only one affected, and 
>> switching CONFIG_FB_PM2_FIFO_DISCONNECT fixes the problem, so, maybe we 
>> could just mark this option "dangerous".
>> 
>> Will (try to) add tomorrow.
> 
> Confirmed - with CONFIG_FB_PM2_FIFO_DISCONNECT fb is still orange, without 
> - no problem.

Quick summary from my point of view: Guennadi is the only report of this
problem, though equally he's the only user I know with an Elsa AG GLoria
Synergy. I have not yet managed to work out why this could be happening; I had
expected that disabling the card reset that pm2fb does on initialisation would
fix matters, leaving the card at its BIOS initialised state. But it doesn't,
and sees to cause bad problems.

PM2_FIFO_DISCONNECT doesn't seem to me to bring much to the party. Since we now
have an example of it causing breakage, I agree with Guennadi that it should be
marked 'dangerous'. I've been away from home/internet connection for some time;
I'm back on Tuesday and I'll submit a patch to do that ASAP.

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


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

  reply	other threads:[~2005-05-28 10:46 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
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 [this message]
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.20050528114622.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 \
    /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).