Which is the better scheme for altering DRM to get FB and IO memory info? These would both be keyed off enabling the 1.1+ interface.
1) Return start/length through generic info IOCTL. Then pass back via addmap DRM_FRAME_BUFFER. 2) Addmap with DRM_FRAME_BUFFER and zero address/length. DRM internally queries info from driver. Then use getmap to retrieve it. 3) Make driver specific IOCTLs in all of the drivers for doing it. Does any hardware have more than one range of IO memory? Another set of generic info that needs to be made available is: PCI Vendor, ID, Sub vendor, Sub ID, interrupt # I currently have this info tacked onto the end of the statistics IOCTL (in order to conserve IOCTL numbers) but there should be a better way to do it. ===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
