From: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
To: Jani Monoses <jani@iv.ro>, Sven LUTHER <luther@dpt-info.u-strasbg.fr>
Cc: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: New API: porting docs ?
Date: Tue, 8 Oct 2002 17:03:34 +0200 [thread overview]
Message-ID: <20021008150334.8249@192.168.4.1> (raw)
In-Reply-To: <20021008150157.1b4b8a9d.jani@iv.ro>
>Attached is tridentfb which works for the new API but only with cfb accels
>the native ones still need work.I'll send this in when that is fixed.
>You can look at it or do a diff against original tridentfb in current 2.5
>to see what's changed
Great, thanks, a diff is what I'm looking for actually :)
Ben.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-08 13:03 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
2002-10-08 11:38 ` Sven LUTHER
2002-10-08 15:01 ` Jani Monoses
2002-10-08 15:03 ` Benjamin Herrenschmidt [this message]
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=20021008150334.8249@192.168.4.1 \
--to=benh@kernel.crashing.org \
--cc=adaplas@pol.net \
--cc=jani@iv.ro \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=luther@dpt-info.u-strasbg.fr \
/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).