On Sat, 2004-04-17 at 20:46, Ryan Underwood wrote: > On Sat, Apr 17, 2004 at 03:33:16PM +0200, Michel DÃnzer wrote: > > > > I don't think such a complicated scheme is needed? Just encode the > > microcode version in the filename and try to load any supported version, > > from most to least preferred? > > I think that's what I meant. Point being, have the kernel call out to a > userspace loader on the driver's behalf, instead of the user running a > loader like Nathaniel's in an init script or something.
My understanding is that the firmware loader interface he uses works similar to your description, via hotplug events. > I was also reminding folks of the importance of versioning of the driver > vs the firmware, because one of his comments seemed to imply that you > could upgrade the microcode to a new version without changes to the > driver. This is not always true because the command interface may change > from revision to revision of the microcode. Indeed, the microcode should definitely be versioned. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- 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
