linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jani Monoses <jani@iv.ro>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: New API: porting docs ?
Date: Tue, 8 Oct 2002 15:16:04 +0000	[thread overview]
Message-ID: <20021008151604.0cc5933e.jani@iv.ro> (raw)
In-Reply-To: <20021008150157.1b4b8a9d.jani@iv.ro>

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]


> 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

forgot it

[-- Attachment #2: t.bz2 --]
[-- Type: application/octet-stream, Size: 8952 bytes --]

  parent reply	other threads:[~2002-10-08 12:07 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
2002-10-08 15:16       ` Jani Monoses [this message]
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=20021008151604.0cc5933e.jani@iv.ro \
    --to=jani@iv.ro \
    --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).