Bug 58785
Summary: | Errors on SA1110 bulk IN transfers | ||
---|---|---|---|
Product: | [Retired] eCos | Reporter: | Bart Veer <bartv> |
Component: | USB driver | Assignee: | Bart Veer <bartv> |
Status: | CLOSED WONTFIX | QA Contact: | eCos bugs internal list <es-ecos-bugs-int> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | CVS | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | strongarm | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-01-24 15:46:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bart Veer
2002-01-24 14:51:14 UTC
Unfortunately there is no way of knowing whether this is a problem with the SA11x0 USB hardware (yet another one), with the Linux host, with the target-side USB driver, or with either the target-side or host-side USB testing infrastructure. Even with proper debugging tools such as a CATC USB protocol analyser it would not be easy to track down this problem. Without such tools it is nearly impossible. Using the best estimation tools available to me for this kind of problem, i.e. a set of dice, I believe that fixing this will take nine months, one week, 3 days, and 7 hours.Approximately. If you have seriously no idea on how long it will take to find and fix this problem, then no time can be allocated to fix this. Estimation needs to be taken seriously and until it is done so, no time can be allocated to fixing this problem. No sane manager will allocate time to an unknown entity. Please come up with a realistic estimate or change the status to WONTFIX :-/ Realistic estimation is only possible on the basis of certain assumptions, for example that the hardware mostly conforms to the specification. If you cannot make such assumptions then no sane engineer is going to commit to any kind of estimate. In this case the problem is most likely caused by another bug in the SA11x0 silicon. It is impossible to predict how long it will take to work around this bug, or even whether or not a viable workaround can be developed at all. Previous experience with the SA1110 USB device suggests that it could take hours, days, weeks, or even months to make any kind of progress. There is no way of knowing, so the existing estimate is just as valid as any other I might put forward. So as instructed I am marking this bug as WONTFIX and closing the report. Note that this will make it impossible to do any type of automated USB testing in the testfarm, at least not with SA11x0 hardware. If the SA1110 is so broken that it cannot run automated tests, what about the MIPS LAKI USB hardware? |