Re: kdrive porting question
"Franco Catrin L." <[email protected]>
| Newsgroups | gmane.comp.freedesktop.xserver |
|---|---|
| Organization | TUXPAN |
| Message-ID | <[email protected]> |
El dom, 28-03-2004 a las 15:45, Brent Cook escribió: > Hello, > > As a first forray into the graphics programming, I have started porting > the neomagic driver from xizzle to kdrive. So far, the driver can detect > the chip and map the framebuffer and MMIO stuff. Hi Brent We are working on the same. I have some acceleration code also, but for some reason MMIO is not working for me, we should join our efforts. > I'm a bit confused about > how ScreenInit is supposed to work. > Looking at how other drivers get screen information, some such as the ati > and mga drivers get info using vesa or fbdev, but the i810 driver seems to > get screen information itself. What should I do? The xizzle neomagic > driver claims to get information from the 'framebuffer layer's > ScreenInit function', but is this the same as getting information from > fbdev? Just let VESA map the framebuffer and you can access it directly. > Also, can I put the work-in-progress driver into CVS, or should I wait > until it is functional before submitting? I hate to clutter the CVS > changelogs, but it would be nice to have some version control. Publish it if you want to. I have mine in a CVS repositoriy but without anonymous access (there are other project which are not mine there). If you can use FDO CVS just upload it and let us work together -- Franco Catrin L. TUXPAN http://www.tuxpan.com/fcatrin