From: Jon Smirl <jonsmirl@yahoo.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Cc: Jon Smirl <jonsmirl@yahoo.com>, kronos <kronos@kronoz.cjb.net>
Subject: Re: New radeonfb 0.2.0 (take 2)
Date: Mon, 8 Sep 2003 20:19:08 -0700 (PDT) [thread overview]
Message-ID: <20030909031908.58173.qmail@web14903.mail.yahoo.com> (raw)
In-Reply-To: <1063039868.1836.31.camel@gaston>
Just a thought, but what do you think about splitting radeonfb into two peices?
Sort of like the way this Rage128 driver is split, http://www.saftware.de/.
First piece does PCI IDs, EDID, mode setting, command parsing, maybe hardware
cursor.
Second does fbcon support such as mapping fb to kernel space, fb accels, etc.
My idea is that this model could evolve over time into having a base driver for
each card, and then the FB or DRI drivers would plug into the base. This would
provide a common place to put locking and state saving code.
=====
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 parent reply other threads:[~2003-09-09 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1063039868.1836.31.camel@gaston>
2003-09-09 3:19 ` Jon Smirl [this message]
2003-09-09 7:58 ` Re: New radeonfb 0.2.0 (take 2) Benjamin Herrenschmidt
2003-09-09 14:52 ` Jon Smirl
2003-09-09 15:22 ` Benjamin Herrenschmidt
2003-09-09 15:58 ` Jon Smirl
2003-09-09 16:17 ` Benjamin Herrenschmidt
2003-09-12 17:51 ` James Simmons
2003-09-12 17:52 ` James Simmons
2003-09-12 17:53 ` 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=20030909031908.58173.qmail@web14903.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=benh@kernel.crashing.org \
--cc=kronos@kronoz.cjb.net \
--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).