> > 3) By switching to the abbreviation Sig from the > > abbreviation S for what in the merely public standard > > appears twice as "Signature" we're just torturing > > newbies for fun. > > Actually, we're trying to keep the debug data a little concise
Even as a newbie I can see this works well. I tried editing a version of the log to use the standard names - immediately I could see I was drowning signal in noise. But I still don't get the purpose of disordering the fields. Why not log them in time order, like they appear in a trace from a bus analyser, like I imagine they appear in address order in host memory, etc.? > and differentiate signature from status. Sig of CSW makes sense to me. What I don't understand is why we have a Sig of CSW but no Sig of CBW. Instead we have an S of CBW. Whoops. That's what looks to me like fun newbie torture. > ... I trust reply-to-all is proper netiquette here. Cluelessly, curiously, thankfully yours, Pat LaVarre ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
