--- Ian Romanick <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
>
> > These PCI changes duplicate things that are in framebuffer. Shouldn't
> we be
> > having a giant argument about them? I would think that is worse that
> DRM is is
>
> Heh...you sure do like to start fights, don't you? :)
>
> > duplicating something in FB. The two IOCTLs I needed for reset don't
> exist in
> > either FB or DRM. Anyway I think these changes need to go in. The
> existing code
> > is broken in respect to PCI hotplug.
> >
> > The DRM drivers can't use the existing Linux PCI probe method because
> the PCI ID
> > tables are in the wrong format. They need two more fields for
> subvendor,
> > subdevice IDs.
> >
> > {0x5333, 0x8c20, 0, "Savage 3D"},
> > {0x5333, 0x8c20, 0, 0, 0, "Savage 3D"},
>
> What is the extra 0? It's present in both "versions", but I'm not sure
> what its purpose is.
>
This is the enable/disable field. I used it for things like
DRM_HAVE_AGPGART ect.
I'm not sure about your other question regarding chip familys.
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
