linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kronos <kronos@people.it>
To: Otto Wyss <otto.wyss@orpatec.ch>
Cc: 'linux-fbdev-devel' <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Framebuffer drivers in kernel 2.6.x
Date: Wed, 18 Aug 2004 22:35:09 +0200	[thread overview]
Message-ID: <20040818203509.GA25325@dreamland.darkstar.lan> (raw)
In-Reply-To: <4123B35C.64E07B02@orpatec.ch>

Il Wed, Aug 18, 2004 at 09:51:56PM +0200, Otto Wyss ha scritto: 
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> Jan-Benedict Glaw wrote:
> > 
> > On Tue, 2004-08-17 18:57:10 +0200, Otto Wyss <otto.wyss@orpatec.ch>
> > 
> > The API changed, but it isn't too hard to port old-style drivers to the
> > new API. If this hasn't happened yet, it's just because nobody yet
> > really missed that particular driver. However, there are a lot of
> > drivers available...
> > 
> I miss radeonfb :-(

radeonfb also exists in 2.6. I know for sure since I wrote a small part
of it :)

You must say y to "Support for frame buffer devices", under "Graphics
support" to see supported framebuffer drivers.

Luca
-- 
Home: http://kronoz.cjb.net
"Su cio` di cui non si puo` parlare e` bene tacere".
 Ludwig Wittgenstein


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  reply	other threads:[~2004-08-18 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 16:57 Framebuffer drivers in kernel 2.6.x Otto Wyss
2004-08-18  5:36 ` Jan-Benedict Glaw
2004-08-18 19:51   ` Otto Wyss
2004-08-18 20:35     ` Kronos [this message]
2004-08-19 15:35       ` Otto Wyss

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=20040818203509.GA25325@dreamland.darkstar.lan \
    --to=kronos@people.it \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=otto.wyss@orpatec.ch \
    /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).