Date: Tue, 18 Jan 2005 02:17:50 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: irchat@free.fr Cc: freebsd-usb@freebsd.org Subject: Re: Prism54 USB Wireless Adapters Message-ID: <200501180217.aa70939@salmon.maths.tcd.ie> In-Reply-To: Your message of "Sun, 16 Jan 2005 12:24:07 %2B0100." <1105874647.41ea4ed7f035f@imp6-q.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <1105874647.41ea4ed7f035f@imp6-q.free.fr>, irchat@free.fr writes: >On Sunday 16 January 2005 02:46, Ian Dowse wrote: >> Try removing the USBD_NO_COPY flag from all the transfer setups. I >> happen to have a USB Prism54 device here, and removing that flag >> appears to cause the p54u_int_rx_cb function to get called. > >It worked. But I had to disable EHCI support in my kernel, is that a bug in >FreeBSD ? I'm running the 5.3 version, which seems to have support for >interrupt pipes on EHCI controllers. I see the same thing here - I had been using a UHCI controller originally, but when I use an EHCI controller I don't see p54u_int_rx_cb() getting called. Without a protocol analyser it may be hard to get much more information... The only thing unusual I could see about the Prism54 driver is that it does a lot of opening and closing of pipes, so maybe something like that is tickling EHCI bugs. >Testing my driver with or without USBD_NO_COPY and the EHCI makes the interrupt >callback never called. With UHCI and without USBD_NO_COPY, my code fails when >the xfers using the buffers that don't support DMA are submitted. Are you saying that something doesn't work with UHCI too? If you avoid the USBD_NO_COPY flag you shouldn't have to worry about DMA buffers, since the USB code will handle them itself. Or do you mean something different? Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501180217.aa70939>