On Sunday 03 July 2005 00:04, Jon Smirl wrote: > Is this table right? > > DRM DRI > ffb ffb > i810 i830 > i830 i830 > i915 i915
With the caveat that i830 is old and deprecated. > There are three DRI drivers with no DRM. What is up with these? > gamma > s3v > trident The gamma drm was axed for being incurably ugly. The s3v and trident DRMs exist in 2.4-style form in old CVS branches but no one's brought them forward yet. I brought the DRI drivers forward as an exercise, and because the Mesa changes were the hard part, the DRM and DDX should be trivial if anyone wants to expend the effort. I don't have a trident yet, but far too many virges, so I should get to that one eventually. > During the EGL driver load process it checks /sys/drm/* looking for > card? entries. When it finds one I need a sysfs attribute in > /sys/drm/card?/dri to tell me which dri library to load. Shouldn't this just be a string you pull right out of a drm ioctl? I know the name currently lives in the server, but as with many things the server does I think that's a mistake. Binding EGL driver load to sysfs is not portable. - ajax
pgp4ljclNLQ8C.pgp
Description: PGP signature
