On Fri, 26 Nov 2004 08:07:51 +0100, "Marco Albani P:" <[EMAIL PROTECTED]> wrote:
> I still have the error message "usb-uhci.c: interrupt, status 3, frame# "
Do you have any OTHER problems with your USB?
The message above is not a problem. It ought to be rate-limited, in fact
Red Hat and SuSE sim
Hi
I have a problem since 3 weeks on using an 2 port Switch from ATEN
International
Could you please help me?
I still have the error message "usb-uhci.c: interrupt, status 3, frame# "
Thanks for your Help in advance
Greets Marco
: lspci -v
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB
Hi,
why the function uhci_submit_urbs is called from process_iso? The urb's
tds are already written when passing usb_submit_urb, aren't they?
Thanks
Thomas Feldburg
---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and depl
Hi,
I am trying to understand the isochrounous transfer in usb-uhci.c. Maybe
you can help me.
The scenario is the following:
A cpia camera is supposed to do isochronous image streaming by a given
endpoint 1. The cpia driver requests in his open routine 2 isoasap-URBs
with ten frame per descripto
The code for usb-uhci.c references a data structure dump program.
Does anyone know where I can find it?
TIA...
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth o
On Mon, 20 Oct 2003, R2D2 wrote:
> Hello!
>
> I'm trying to develop an driver for the TUSB3410-Serial To
> USB-Converter-IC. But I'm still having problems developing the firmware
> for the IC. I always get the following message:
> usb-uhci.c: interrupt, status 2, frame# 962
> Where 962 can be a
Hello!
I'm trying to develop an driver for the TUSB3410-Serial To
USB-Converter-IC. But I'm still having problems developing the firmware
for the IC. I always get the following message:
usb-uhci.c: interrupt, status 2, frame# 962
Where 962 can be any number.
I'd don't know what's the reason for
Georg Acher wrote:
...
>It looks like your case (stall in data phase) is treated as a short packet
>with a manually executed status phase, which is wrong. The "stalled" state
>is detected (and IMHO the endpoint state of the device-structure should
>reflect this), but it doesn't survive in the end
On Mon, Oct 15, 2001 at 04:27:19PM -0400, Brad Parker wrote:
>
> Is it my imagination, or does usb-uhci.c fail to report STALL's in
> data phase of a control message? (stock linux-2.4.5)
>
> I have an audio device which returns a STALL when I try to get the
> sampling freq; One HCI reports an er
Is it my imagination, or does usb-uhci.c fail to report STALL's in
data phase of a control message? (stock linux-2.4.5)
I have an audio device which returns a STALL when I try to get the
sampling freq; One HCI reports an error and I get no audio.
usb-uhci.c merrily ignores the error and I get is
10 matches
Mail list logo
