linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Jani Monoses <jani@iv.ro>
Cc: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
	jsimmons@transvirtual.com,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: new api example or docs ?
Date: Mon, 5 Aug 2002 10:04:11 +0200	[thread overview]
Message-ID: <20020805080411.GA1204@iliana> (raw)
In-Reply-To: <20020805091325.441ad7de.jani@iv.ro>

On Mon, Aug 05, 2002 at 09:13:25AM +0000, Jani Monoses wrote:
> 
> > > 
> > > No skeletonfb is pretty much up to data. The driver to look at is the 3Dfx
> > > driver. Its is the best new api driver.
> > 
> > Ok i will look at the 3Dfx driver.
> I started porting tridentfb this weekend and to me too tdfx seemed the best example to use.

Ok (altough it seems romain will have a look at this, so i will probably
let him do it, since i am busy anyway).

> > But when i look at the neofb for example, but it is the same in
> > matroxfb, i see that pci_register_driver is called with a structure
> > containing the neofb_probe function, which is something absolutely not
> > present in the skeletonfb.
> that's unrelated to the new fb API.It's the 'new' PCI API which is in 2.4 too
> and lets you detect the PCI cards your driver knows about without calling
> pci_find_devices & co by instead supplying the probe/remove functions and a PCI id table.
> It also help with power management..

Well, but i thought the skeletonfb was to be used as a model/skeleton/guide
to creating a new framebuffer device.

So it should include this as well, should it not ?

Especially as there is no other documentation around.

Friendly,

Sven Luther


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-08-05  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-01 15:18 new api example or docs ? Sven LUTHER
2002-08-02 15:46 ` James Simmons
2002-08-02 16:54   ` Sven LUTHER
2002-08-05  9:13     ` Jani Monoses
2002-08-05  8:04       ` Sven LUTHER [this message]
2002-08-05 11:19         ` Romain Dolbeau
2002-08-05 11:47           ` Sven LUTHER
2002-08-06  6:26         ` James Simmons

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=20020805080411.GA1204@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=jani@iv.ro \
    --cc=jsimmons@transvirtual.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).