|
From: Sven L. <lu...@dp...> - 2002-08-05 09:16:43
|
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 |