From: Dermot Bradley <dermot.bradley@openwave.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Framebuffer Port guide for 2.4->2.6?
Date: Mon, 08 Nov 2004 13:33:02 +0000 [thread overview]
Message-ID: <418F758E.3090403@openwave.com> (raw)
In-Reply-To: <41892D53.1060007@cablespeed.com>
Kelly Price wrote:
> Is there a port guide for framebuffer drivers going from 2.4 to 2.6? I'm
> trying to port the CT65548 Frambuffer driver over to 2.6.
>
> http://members.elysium.pl/ytm/html/linux.html is where the 2.4 version
> is at.
This would interest me as I've got a Fuji PT510 with this chip in it.
I'd wondered about trying to port this driver to 2.6 myself but (a) I
haven't found the time so far and (b) I'm not really a programmer :-)
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
prev parent reply other threads:[~2004-11-08 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 19:11 Framebuffer Port guide for 2.4->2.6? Kelly Price
2004-11-04 1:46 ` Antonino A. Daplas
2004-11-08 13:33 ` Dermot Bradley [this message]
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=418F758E.3090403@openwave.com \
--to=dermot.bradley@openwave.com \
--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).