From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Sven LUTHER <luther@dpt-info.u-strasbg.fr>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: new api example or docs ?
Date: Fri, 2 Aug 2002 18:54:35 +0200 [thread overview]
Message-ID: <20020802165435.GA7822@iliana> (raw)
In-Reply-To: <Pine.LNX.4.44.0208020845050.10247-100000@www.transvirtual.com>
On Fri, Aug 02, 2002 at 08:46:39AM -0700, James Simmons wrote:
>
> > Hello James.
> >
> > I did give a quick try at adapting pm3fb to the new api, but without
> > much success.
> >
> > I did look at skeletonfb.c as you suggested (the one in the 2.5.29
> > kernel) and after some work to make it build, it only gave me a segfault
> > when inserting the module.
>
> skeletonfb is meant for only a example. I never expected to work.
Not as a skeleton from which you can build up a new driver ?
> > Looking a bit more to into this, and comparing skeletonfb to both neofb
> > and matroxfb, it seems to me that the skeletonfb that ships with the
> > 2.5.29 kernel is severly outdated.
>
> 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.
BTW, the main difference i see between skeletonfb and the other driver
is about the _init function. if contains lot of stuff to initialize the
fb_info structure and such.
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.
> > In this case, which driver would you suggest i look at ? And is there
> > other documentation about the new api around.
>
> Not yet.
Too bad, ...
I would have been nice to have such a thing before you remove the
backward compatibility from the new kernels.
Anyway, thanks for your help, i will look at the existing drivers then.
Friendly,
Sven Luther
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-08-04 13:53 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 [this message]
2002-08-05 9:13 ` Jani Monoses
2002-08-05 8:04 ` Sven LUTHER
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=20020802165435.GA7822@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.