From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
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 07:36:51 +0200 [thread overview]
Message-ID: <20040818053646.GC16935@lug-owl.de> (raw)
In-Reply-To: <412238E7.C4A7ED2D@orpatec.ch>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Tue, 2004-08-17 18:57:10 +0200, Otto Wyss <otto.wyss@orpatec.ch>
wrote in message <412238E7.C4A7ED2D@orpatec.ch>:
> I tried to use kernel 2.6.7 but there are almost no framebuffer drivers.
Uh? There are quite a lot of them...
> Why is this, can't the drivers from 2.4.x easily be ported to 2.7.x?
> What are the obstacles?
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...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-18 5:39 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 [this message]
2004-08-18 19:51 ` Otto Wyss
2004-08-18 20:35 ` Kronos
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=20040818053646.GC16935@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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).