linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Kronos <kronos@kronoz.cjb.net>
Subject: Re: Re: New radeonfb 0.2.0 (take 2)
Date: Tue, 09 Sep 2003 18:17:17 +0200	[thread overview]
Message-ID: <1063124237.1356.1.camel@gaston> (raw)
In-Reply-To: <20030909155822.47988.qmail@web14904.mail.yahoo.com>

On Tue, 2003-09-09 at 17:58, Jon Smirl wrote:
> --- Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > On Tue, 2003-09-09 at 16:52, Jon Smirl wrote:
> > What would 'base' be without all of this ? just the PCI probing ?
> > 
> Base does PCI IDs, EDID, mode setting, command parsing, maybe hardware cursor,
> VT switching and state saving.
> Second piece does fbcon support such as mapping fb to kernel space, fb accels,
> etc.

The current fbdev layer, afaik, impose vt switching, mode setting,
cursor support etc... to imply fbcon. The mapping of fb is just a
2 liner remaining that isn't worth a separate module.

Also, the accel API in 2.6 is meant to be used by more than just
fbcon afaik.

James, can you comment on this ?

Ben.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-09-09 16:17 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 ` New radeonfb 0.2.0 (take 2) Jon Smirl
2003-09-09  7:58   ` 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 [this message]
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=1063124237.1356.1.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jonsmirl@yahoo.com \
    --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).