On Sat, 1 Feb 2003, david wrote:
>hi i sent you an email some time ago but have not got any reply
>(opps i think that was me not being on the list )
Probably the reason you haven't gotten any replies, is that you
mention the driver is for 3.3.6, which is about 3 years obsolete
now, and nobody is maintaining it or interested in 3.3.6 anymore.
Any work on 3.3.6 is more or less a waste of time as 3.3.6 is
totally dead, so your code most likely will never go into the
3.3.6 tree ever.
>i need some help FAST! as the driver is now veary close to ready
>!! can you let me know even if some one is looking into it i
>think this is a vary good driver and i wont to get it relest as
>soon as!! i am know using ./accel/nvxf for my driver
Again, the 3.3.6 tree is totally dead, and more or less
completely unmaitained. I would guess that it would be unlikely
for maintainers to examine any new code based on 3.3.6.
>A long time ago i registered is an xf-developer working on an S3
>driver but the S3 driver did not go any ware and it is now
>closed but i think i am stall registered for that project so can
>someone help me close the S3 project and open my new one ?
You don't need to close anything or open any new thing. You just
write code, and discuss it on the [EMAIL PROTECTED] mailing list,
and send patches against the current CVS head (4.2.99.4
currently) that build cleanly and work. They would be too late
to get into 4.3.0 at this stage, but after 4.3.0 is released, 4.x
development will continue.
>my new driver is called NVXF for (NVIDIA xfree86) i no there is
>all ready a NV driver for xfree but this driver is so different
>it supports full hardware accel 2D / 3D 32 bpp on (NV04 , NV05)
>chips (NV1x - NV2x) soon it uses DMA for 2D / 3D commands and
>most image transfers and has BIOS level init code for non boot
>cards
You should be on the dri-devel list on sourceforge, communicating
with DRI developers, and also discussing this with Mark
Vojkovich, the "nv" maintainer.
>the driver is about 80% written for 3.3.6 i want to parallel
>build the 4.x.x driver at the same time as the 3.3.6 as the HW
>cores are the same
As I said above, the 3.3.6 tree is very dead, so while your
effort may be great, it isn't likely to garner a lot of interest
IMHO unless it is based off of XFree86 4.2.99.4. Nonetheless,
I'm sure that people would be willing to test it out, and perhaps
even to help finish a port to 4.x. Again, [EMAIL PROTECTED]
is probably the best place to be subscribed.
>can i have the GLX 3D part in the driver itself for 3.3.6 and
>4.x.x ?
It should be done as a Mesa driver basically.
>to start quickly i just roat over the I128 driver in
>xc/programs/Xserver/hw/xfree86/accel/i128 so i need help on how
>to properly link my driver in if possible i wold like the dir
>xc/programs/Xserver/hw/xfree86/accel/nvxf for 3.3.6 and
>xc/programs/Xserver/hw/xfree86/drivers/nvxf for 4.x.x
Just examine the Imakefile in:
xc/programs/Xserver/hw/xfree86/drivers
It should be more or less obvious if you've gotten this far
already.
>can some one help me on where to put the reference to my driver
>in the Makefile and the like
>
>also can i set up a developer mail list for this driver ?
Just use dri-devel list.
Hope this helps.
--
Mike A. Harris
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
