65ceb4c931
* Don't set the IOC bit on the link TRB in LinkDescriptorForPipe. We don't
want to know about this' completion, only about the other transfers
completion and statuses. This should halve the interrupt rate.
* Check if this is an Event Data TRB, and return an error if it is.
(I haven't managed to trigger this code, but it is theoretically possible.)
* Rewrite loops for clarity and consistency.
* Use the correct offset when checking for the TRB.
- Don't rely on the trb_count to tell us whether the TRB is in the TD,
but just check the address based on MAX_TRBS_PER_TD.
- Previously, as the link TRB would trigger an interrupt, we could rely
on that to determine when the transfer finished. But that of course
did not tell us the correct status, as the link TRB is techically in a
different TD, as it isn't linked to the previous TRBs. Now we always use
"count - 1", which will be the final TRB in the TD, properly speaking.
* Print errors when we fail to find the TRB for any reason.
Reading multiple GB and abusing "stat" on a usb_disk following this commit
only managed to stall my usb_hid attached mouse once in multiple rounds of
testing, which seems a marked improvement; previously only a few hundred MB
and not that much abuse of "stat" were needed to actually trigger the stall.
So it seems this improves the stall situation considerably.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.