From: Otto Wyss <otto.wyss@orpatec.ch>
To: 'linux-fbdev-devel' <linux-fbdev-devel@lists.sourceforge.net>
Subject: Framebuffer drivers in kernel 2.6.x
Date: Tue, 17 Aug 2004 18:57:10 +0200 [thread overview]
Message-ID: <412238E7.C4A7ED2D@orpatec.ch> (raw)
I tried to use kernel 2.6.7 but there are almost no framebuffer drivers.
Why is this, can't the drivers from 2.4.x easily be ported to 2.7.x?
What are the obstacles?
Is there any documentation for writing framebuffer drivers?
Who is working on the radeonfb driver?
O. Wyss
--
See a huge pile of work at "http://wyodesktop.sourceforge.net/"
-------------------------------------------------------
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
next reply other threads:[~2004-08-17 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 16:57 Otto Wyss [this message]
2004-08-18 5:36 ` Framebuffer drivers in kernel 2.6.x Jan-Benedict Glaw
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=412238E7.C4A7ED2D@orpatec.ch \
--to=otto.wyss@orpatec.ch \
--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).