On Wed, 20 Oct 2004 00:40:07 -0400, Jon Smirl <[EMAIL PROTECTED]> wrote: > Does this fix it for you? I haven't figured out how to trigger it yet.
I think the problem here is that vesafb is not attached as a true device driver but it has the resources allocated. DRM comes along and see vesafb so it goes into stealth mode. In stealth mode DRM does not attach as a true driver either. So now we have the pci device in use without a driver attached. The answer here is that because of stealth mode I can't rely on the pointer pdev->driver->name to get the driver name. It may be null in the case of fbdev and "xxxfb" for an fbdev driver. I need to make a different pointer for recording the driver name. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
