#tyndur · 2010-04-20
27 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen
- eddybXanClic: it is normal to have to unset the port reset bit after 50ms?
- XanClicYes, of course
- XanClicSometimes it might be useful to read the specs *g*
- eddyb"The bit status will not read as a zero until after the reset has completed."
- eddybwhat's that supposed to mean?
- XanClicWe're talking about EHCI or UHCI, right?
- eddybEHCI
- XanClicPort ResetR/W. 1=Port is in Reset. 0=Port is not in Reset. Default = 0. When software writes a one to this bit (from a zero), the bus reset sequence as defined in the USB Specification Revision 2.0 is started. Software writes a zero to this bit to terminate the bus reset sequence. Software must keep this bit at a one long enough to ensure the reset sequence, as specified in the USB Specification Revision 2.0, completes.
- eddybI've read it
- XanClicAnd the bit status doesn't change until the reset sequence is completetd
- XanClic*completed
- XanClicHigh speed chirp, etc.
- eddybso HC should unset it or not?
- XanClicAh, reading != understanding, ok *g*
- XanClic"Software writes a zero to this bit to terminate the bus reset sequence."
- XanClicI guess it should say: "The HC doesn't do anything on its own"
- eddybaha
- XanClicAnd consider "Software must keep this bit at a one long enough to ensure the reset sequence"
- eddyband qemu does implement this behavior
- XanClicWhich is correct for both UHCI and EHCI
- eddybno plug and play, Pedigree
- eddybat least for now
- eddybok, time to remove UsbManager
- eddybnow
- eddybis EHCI supposed to give an IRQ when there is no device with the address in the token?
- XanClicYes, CRC/timeout
- eddybqemu's doesn't :|