From: Antonino Daplas <adaplas@pol.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: New API: porting docs ?
Date: 08 Oct 2002 03:45:00 +0800 [thread overview]
Message-ID: <1034019453.572.26.camel@daplas> (raw)
In-Reply-To: <20021006112909.30306@192.168.4.1>
On Sun, 2002-10-06 at 19:29, Benjamin Herrenschmidt wrote:
> HI !
>
> I have a whole bunch of fbdev's that need porting to the
> new API that is currently in 2.5. Is there any kind of doc
> available or a HOWTO explaining at least briefly what is
> invovled ? (what changed and now ?)
>
> Ben.
The most updated doc that I know of is skeletonfb.c.
Tony
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-07 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 11:29 New API: porting docs ? Benjamin Herrenschmidt
2002-10-07 19:45 ` Antonino Daplas [this message]
2002-10-08 11:38 ` Sven LUTHER
2002-10-08 15:01 ` Jani Monoses
2002-10-08 15:03 ` Benjamin Herrenschmidt
2002-10-08 15:16 ` Jani Monoses
2002-10-08 13:00 ` Sven LUTHER
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=1034019453.572.26.camel@daplas \
--to=adaplas@pol.net \
--cc=benh@kernel.crashing.org \
--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).