On Fri, 2011-08-05 at 09:47 -0400, Kent A. Reed wrote: ... snip > Lots of good info here, Kirk, but I don't think your guess is correct. I > looked at the source code for lspci and all it does is read the value of > a bit, conventionally called PCI_COMMAND_IO, in a word, conventionally > called PCI_COMMAND in the device interface. If it is unset, then lspci > appends the "disabled" label in its report. > > I believe it is the driver that sets this bit as part of its > initialization but I'm not in a position to test this. > > Nothing earthshaking here. Just a minor correction to make sure no one > over-estimates the intelligence of lspci. > > Regards, > Kent
Thanks for the correction. Actually, anything I present should be independently verified before use. Mostly what I was trying to get across is that the workings of the parallel port can be fairly complicated, but the good news is that most of the information needed to solve problems is available somewhere through study, experimentation, or knowing what questions to ask, which of course, is the bane of "just works". For "just works" I suppose one could just copy a known good system's software and hardware versions, which could turn out to be a bit of work in itself. Probably the most "just works" method is to buy a just working system. Each method is valid and has its trade-offs, but I guess I'm not saying anything new. -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/index.html California, USA ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
