From: David Miller <davem@davemloft.net>
To: adaplas@gmail.com
Cc: akpm@osdl.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 01/10] fbdev: Clean up of sparc FB options
Date: Wed, 16 May 2007 17:15:26 -0700 (PDT) [thread overview]
Message-ID: <20070516.171526.08322463.davem@davemloft.net> (raw)
In-Reply-To: <1179360635.28568.0.camel@daplas>
From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: Thu, 17 May 2007 08:10:34 +0800
> On Wed, 2007-05-16 at 17:05 -0700, David Miller wrote:
> > From: "Antonino A. Daplas" <adaplas@gmail.com>
> > Date: Thu, 17 May 2007 08:01:58 +0800
> >
> > > The question is, will this work for sparc?
> >
> > It can't be just by type, we need to be able to able to select
> > individual instances of the same kind of device. I can't tell if
> > you're saying your scheme handles this or not :-)))
> >
> > I can have two ffb cards in my machine and I can tell fbcon precisely
> > which of those ffb instances is the primary one. That's what I'd need
> > to work.
>
> As long as each instance is defined by distinct struct fb_info's, it
> should work.
Excellent.
The only missing piece for sparc is how do I get from an fb_info to
the firmware node for that device. What we can do is add a "struct
device_node *" or similar to fb_info. powerpc and all future
openfirmware platforms will be able to make use of this as well.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-05-17 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 21:17 [PATCH 01/10] fbdev: Clean up of sparc FB options Antonino A. Daplas
2007-05-16 21:47 ` David Miller
2007-05-16 23:15 ` Antonino A. Daplas
2007-05-16 23:17 ` David Miller
2007-05-17 0:01 ` Antonino A. Daplas
2007-05-17 0:05 ` David Miller
2007-05-17 0:10 ` Antonino A. Daplas
2007-05-17 0:15 ` David Miller [this message]
2007-05-17 0:36 ` Antonino A. Daplas
2007-05-17 0:42 ` David Miller
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=20070516.171526.08322463.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--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).