#tyndur · 2010-04-20

27 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. eddybXanClic: it is normal to have to unset the port reset bit after 50ms?
  2. XanClicYes, of course
  3. XanClicSometimes it might be useful to read the specs *g*
  4. eddyb"The bit status will not read as a zero until after the reset has completed."
  5. eddybwhat's that supposed to mean?
  6. XanClicWe're talking about EHCI or UHCI, right?
  7. eddybEHCI
  8. XanClicPort ResetR/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.
  9. eddybI've read it
  10. XanClicAnd the bit status doesn't change until the reset sequence is completetd
  11. XanClic*completed
  12. XanClicHigh speed chirp, etc.
  13. eddybso HC should unset it or not?
  14. XanClicAh, reading != understanding, ok *g*
  15. XanClic"Software writes a zero to this bit to terminate the bus reset sequence."
  16. XanClicI guess it should say: "The HC doesn't do anything on its own"
  17. eddybaha
  18. XanClicAnd consider "Software must keep this bit at a one long enough to ensure the reset sequence"
  19. eddyband qemu does implement this behavior
  20. XanClicWhich is correct for both UHCI and EHCI
  21. eddybno plug and play, Pedigree
  22. eddybat least for now
  23. eddybok, time to remove UsbManager
  24. eddybnow
  25. eddybis EHCI supposed to give an IRQ when there is no device with the address in the token?
  26. XanClicYes, CRC/timeout
  27. eddybqemu's doesn't :|