linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] fbdev broken in current bk for PPC
Date: Fri, 10 Sep 2004 13:28:57 +0800	[thread overview]
Message-ID: <200409101328.57431.adaplas@hotpop.com> (raw)
In-Reply-To: <1094783022.2667.106.camel@gaston>

On Friday 10 September 2004 10:23, Benjamin Herrenschmidt wrote:
> Recent changes upstream are breaking fbdev on pmacs.
>
> I haven't had time to go deep into that (but I suspect Linus sees it
> too on his own g5 unless he removed offb from his .config).
>
> From what I see, it seems that offb is kicking in by default, reserves
> the mmio regions, and then whatever chip driver loads can't access them.
>
> offb is supposed to be a "fallback" driver in case no fbdev is taking
> over, it should also be "forced" in with video=ofonly kernel command
> line. This logic has been broken.
>

Hi Ben,

Actually, I was thinking about this problem with offb.  I was planning on
adding video=offb:off support for offb, and then place offb at the very top
drivers Makefile (the reason why I placed it there, but forgot to add the
setup support for offb).  So, without the 'off' option, offb becomes the
first driver that gets initialized by reason that it's at the top, and with
the 'off' option, it just exits initialization immediately, giving the other
drivers a chance to get through.

This first method is easy to add.

The second method is not harder but will involve, again, changes to all 
drivers.  The only sane method I can think of is to change fb_get_options so
it returns an error if:

a. "off" option is enabled
b. "ofonly" is enabled but only if name != "offb"

If fb_get_options returns an error, drivers will not proceed with their
initialization. The second method is more compatible with the
previous setup semantics.

I told Geert that if the changes did bite us, then I have no choice
but to add support for the second method.

So, if you think that the first method is not enough, then I will add the
second method. Let me know.

Tony

  reply	other threads:[~2004-09-10  5:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  2:23 fbdev broken in current bk for PPC Benjamin Herrenschmidt
2004-09-10  5:28 ` Antonino A. Daplas [this message]
2004-09-10  6:00   ` Benjamin Herrenschmidt
2004-09-10  8:07     ` Geert Uytterhoeven
2004-09-10  8:35       ` Antonino A. Daplas
2004-09-11  1:04         ` Antonino A. Daplas
2004-09-10  8:35     ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10  8:48       ` Anton Blanchard
2004-09-10 17:52   ` David Eger
2004-09-10 21:27     ` Antonino A. Daplas
2004-09-10 23:40       ` David Eger
2004-09-11  7:19   ` Geert Uytterhoeven
2004-09-10 21:04 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-11  1:00   ` Benjamin Herrenschmidt
2004-09-13  1:52   ` Joseph Fannin
2004-09-20  9:27   ` Benjamin Herrenschmidt
2004-09-20 15:52     ` [Linux-fbdev-devel] " Andrew Morton
2004-09-20 19:38       ` Antonino A. Daplas
2004-09-20 19:59         ` Antonino A. Daplas

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=200409101328.57431.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --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).