I forward the content of this messgae in the Name of torsten, since he can't post to this list sometimes. The ML Software seems to check if a [EMAIL PROTECTED] exists, which fails with our shit account at 1&1.de. May be I force my boss to give us additionally a postmaster account.
Also I have the feeling the ML software most often breaks threads. Even if the subject line changes a reply should be threaded due to the references headers and such. ----- Forwarded message from Torsten Koschorrek <[EMAIL PROTECTED]> ----- Message-ID: <[EMAIL PROTECTED]> Date: Wed, 22 Dec 2004 15:28:43 +0100 From: Torsten Koschorrek <[EMAIL PROTECTED]> Organization: synertronixx GmbH To: Konstantin Kletschke <[EMAIL PROTECTED]> Subject: Re: [linux-usb-devel] ISP116x / 1362 driver progress Philipp Schmid wrote: >What I mean by better results is that as mentioned I observe PTS needing to >be resubmitted repeatedly. When handling SOF and ATL interrupts, I've >observed 3 cases: > >(1) PTDs are resubmitted multiple times but get handled eventually before >USB timeout mechanisms kick in (OK, I guess) >(2) PTDs are resubmitted multiple times but get handled eventually after USB >timeout mechanisms kick in (not good as OHCI then shuts down the offending >endpoint) >(3) PTDs never seem to get handled (I've added some support to detect this >case and pass the offending PTD back as device not responding to avoid >hanging driver, but this shouldn't happen in the first place) > Hmm, maybe our locking/scheduling/timing probs have to do with that?? >Note: This is a very easy 2 line change in Lothar's driver: > >pretending we did not have this masked when reading the status: > dev->int_mask = __isp1362_read_reg16(dev, HCuPINTENB) | > HCuPINT_ISP116x_ATL >| HCuPINT_OPR; > >writing the mask back in the ISR: > __isp1362_write_reg16(dev, HCuPINTENB, dev->int_mask & > ~HCuPINT_ISP116x_ATL >& ~HCuPINT_OPR); > > Will try it. > >On a different note, I have observed an undocumented interrupt bit as shown >below in the InterruptStatus register (0x0080). It is masked out, so I'm >not worried about it. But it would be nice what it is. OHCI considers this >bit reserved, and so does the isp1160 documentation. Has anyone else seen >this? Yes, I've recogniced that interrupt too, but as you said it is reserved. I think or better hope, that this doesn't have any negative effect. @all isp1xxx users, can you tell us the name of the chip you're working with! I have an isp1161a1. Olav has also an isp116x, Lothar has a 1362 as far as I know. And the others? Thanks, Torsten -- synertronixx GmbH Torsten Koschorrek Vahrenwalder Str. 7 30165 Hannover Tel. : 0511 / 93 57 - 670 Fax : 0511 / 93 57 - 679 E-mail : [EMAIL PROTECTED] Internet: http://www.synertronixx.de ----- End forwarded message ----- Regards, Konsti -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
