All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Otto Solares <solca@guug.org>
Cc: James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Changing modes with fbset
Date: Tue, 06 Jan 2004 11:35:49 +1100	[thread overview]
Message-ID: <1073349349.780.181.camel@gaston> (raw)
In-Reply-To: <20040106002822.GB442@guug.org>

On Tue, 2004-01-06 at 11:28, Otto Solares wrote:
> On Tue, Jan 06, 2004 at 12:06:04AM +0000, James Simmons wrote:
> > 
> > Applied. Thanks for finding that.
> 
> Hi James! now that you are back again, i would like to suggest
> a modification to fbdev core, i am having problems guessing
> which card is attached to a fb device.  I need this info to
> solve the 'more than 1 card' situation.  This could be easily
> fixed if the fbdev api provides the busid of the card, like
> "pci:0000:01:0.0".  That would solve a lot of things in the
> HAL detection routines.  Maybe that could be exported via
> sysfs but i have been waiting for sysfs for a while and don't
> see it coming to a reality.  Maybe an ioctl is enough.

Right, we need that and some way to know which heads are "coupled" for
dual head drivers. One of the reasons I haven't done dual head support
in radeonfb yet is that to get it working properly with X, I need to
update X too, and add a way for X to know which /dev/fb's are actually
"together" as 2 heads of the same card.

Then, we probably want some way to also enable mirroring instead of
dual head...

Ben.




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

  reply	other threads:[~2004-01-06  0:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10  7:03 Changing modes with fbset John Zielinski
2003-12-14  1:14 ` John Zielinski
2003-12-24  8:20   ` fbdev upstream (was: Changing modes with fbset) Benjamin Herrenschmidt
2003-12-24  8:26     ` Carlo E. Prelz
2003-12-24 20:40     ` fbdev upstream John Zielinski
2003-12-24 22:42       ` Benjamin Herrenschmidt
2003-12-25  0:45         ` John Zielinski
2003-12-25  0:57           ` Benjamin Herrenschmidt
2003-12-25  1:53             ` John Zielinski
2003-12-25 10:46               ` Benjamin Herrenschmidt
2003-12-25 16:53                 ` John Zielinski
2004-01-05 14:41         ` Geert Uytterhoeven
2004-01-06  0:51         ` James Simmons
2004-01-06  1:03           ` Benjamin Herrenschmidt
2004-01-06 10:08             ` Geert Uytterhoeven
2004-01-09 20:05               ` James Simmons
2004-01-06  0:47       ` James Simmons
2004-01-08  2:17         ` John Zielinski
2004-01-08 20:37           ` James Simmons
2004-01-06  0:06   ` Changing modes with fbset James Simmons
2004-01-06  0:28     ` Otto Solares
2004-01-06  0:35       ` Benjamin Herrenschmidt [this message]
2004-01-06  1:08         ` Otto Solares
2004-01-06  1:09           ` Benjamin Herrenschmidt
2004-01-06  1:44             ` Otto Solares
2004-01-06  1:44               ` Benjamin Herrenschmidt
2004-01-06  2:06                 ` Otto Solares
     [not found]                   ` <1073354986.761.208.camel@gaston>
2004-01-06  2:24                     ` Otto Solares
2004-01-06 11:38         ` Michel Dänzer
2004-01-06 15:23           ` Geert Uytterhoeven
2004-01-09  0:03       ` James Simmons
2004-01-09  1:31         ` Otto Solares
2004-01-06  0:33     ` Benjamin Herrenschmidt
2004-01-06  0:38       ` James Simmons
2004-01-08  2:06     ` John Zielinski
2004-01-08 20:38       ` James Simmons

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=1073349349.780.181.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=solca@guug.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.