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>, adaplas@pol.net
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [Linux-fbdev-devel] fbdev broken in current bk for PPC
Date: Fri, 10 Sep 2004 16:35:16 +0800	[thread overview]
Message-ID: <200409101635.16803.adaplas@hotpop.com> (raw)
In-Reply-To: <1094796002.14398.118.camel@gaston>

On Friday 10 September 2004 14:00, Benjamin Herrenschmidt wrote:
> On Fri, 2004-09-10 at 15:28, Antonino A. Daplas wrote:
> > 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.
>
> I submited a patch moving offb to the bottom of the Makefile to at
> least restore normal drivers. For ofonly, a bit more hackish, but
> what about failing register_framebuffer for anything but offb ?

Yes, that should solve the ofonly problem, with the offb in the very last of 
the Makefile, though as you said, it's a little hackish, but very simple to 
implement.  This will work for ofonly though, since 
info->fix.name is not necessarily equal to "xxxfb".  For instance, offb set 
"OFfb" in info->fix.name, but the boot option is "offb".

After giving it some thought, I think method 2 might be the best since it 
provides compatibility with the old syntax.  Especially if users expect 
video=xxxfb:off to work.  Also, this brings more flexibility in the offchance 
we decide to add more options to "video=".

I'm willing to work on this, but if you don't like it, then I'll do the 'fail 
at register_framebuffer".

Tony

  parent reply	other threads:[~2004-09-10  8:35 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 ` [Linux-fbdev-devel] " Antonino A. Daplas
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     ` Antonino A. Daplas [this message]
2004-09-10  8:48       ` [Linux-fbdev-devel] " 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=200409101635.16803.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).