From: Otto Solares <solca@guug.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Changing modes with fbset
Date: Mon, 5 Jan 2004 20:06:53 -0600 [thread overview]
Message-ID: <20040106020653.GE442@guug.org> (raw)
In-Reply-To: <1073353478.9499.204.camel@gaston>
On Tue, Jan 06, 2004 at 12:44:39PM +1100, Benjamin Herrenschmidt wrote:
>
> > Ben, you that know the internals of fbdev's, it would be difficult to
> > implement the busid stuff? Maybe that info is already known by the
> > drivers somewhere... It could even work for sparcs with sbus or others
> > archs with differents buses, as the busid nomenclature is very standarized
> > i think.
>
> Fairly easy, though it would be even better to do it based on the
> sysfs stuff rather than an ioctl.
Agree. Problem is that sysfs stuff is very invasive i think and it
will be hard to push even on development trees like -mm ones. An
ioctl could be something simple as passing a pointer to a buffer
of fixed length, the best imho would be extend fb_fix_screeninfo
struct to accomodate a 'char busid[16];' but that could break
binary compatibility. If 2.6 break from 2.4 we could put it
there as anyway apps need to recompile. Shame that there are
not sufficient 'reserved' bits.
-solca
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-01-06 2:08 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
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 [this message]
[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=20040106020653.GE442@guug.org \
--to=solca@guug.org \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.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).