From: Jon Smirl <jonsmirl@yahoo.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Add three new IOCTLs to FB API
Date: Mon, 22 Sep 2003 13:25:11 -0700 (PDT) [thread overview]
Message-ID: <20030922202511.53395.qmail@web14915.mail.yahoo.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0309220919230.4957-100000@vervain.sonytel.be>
--- Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Sun, 21 Sep 2003, Jon Smirl wrote:
> > I'd like to add three new IOCTLs to the FB API to help support standalone
Mesa.
> > The idea is to eliminate the need for config files. Xfree might even use
these
> > in the future.
>
> For 2.4.x or 2.6.0?
For 2.6
> > 2) Get 3D driver name. Return the name of the DRM driver that is associated
> > with this fb device. For example aty128fb would return r128, radeonfb would
> > return radeon. Empty string if there is none. There are eight DRM drivers
> and
> > 15 fb ones.
>
> I think this should be done using sysfs, too. I.e. symbolic links between the
> fbdev and drm drivers in /sys.
Initially the fb device will need to provide strings for the name of the 3D
driver. A user app is going to read these strings and load the DRM driver.
After the DRM driver is loaded it can make links.
Another solution would be for the fb driver to reference a symbol in the
appropriate DRM driver. This would make modprobe load them both.
What should the /sys entries look like for fb devices?
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-22 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 5:28 Add three new IOCTLs to FB API Jon Smirl
2003-09-22 6:13 ` Ian Romanick
2003-09-22 7:21 ` Geert Uytterhoeven
2003-09-22 20:25 ` Jon Smirl [this message]
2003-09-23 0:27 ` Michel Dänzer
2003-09-22 23:18 ` Ian Romanick
2003-09-23 16:36 ` Kronos
2003-09-22 10:23 ` Michel Dänzer
2003-09-23 15:45 ` Ville Syrjälä
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=20030922202511.53395.qmail@web14915.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=geert@linux-m68k.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).