Alan Cox wrote:
GFP_DMA means ISA DMAable memory (low 16Mb), its obsolete and you should
be using the pci_alloc/dma_alloc interfaces in 2.6-test
Agree about "don't use GFP_DMA with USB".
But there's no way to use pci_alloc or dma_alloc with USB.
Instead, read Documentation/usb/dma.txt ... those A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 9 Aug 2003 06:40 am, Olaf Hering wrote:
> I got a report about an USB floppy which is detected more than once,
> even with 2.4.22-pre7. A workaround would be the max_scsi_luns=1 or
> similar. Is there a fix?
Quirks (drivers/usb/storage/unusual_
ChangeSet 1.1119.1.13, 2003/08/07 11:00:56-07:00, [EMAIL PROTECTED]
[PATCH] USB: remove dev.name usage from gadget code.
drivers/usb/gadget/net2280.c |1 -
1 files changed, 1 deletion(-)
diff -Nru a/drivers/usb/gadget/net2280.c b/drivers/usb/gadget/net2280.c
--- a/drivers/usb/gadget/net22
Hi,
Here are some more USB fixes for 2.6.0-test2. Again, more audit patches
from Oliver Neukum, and some other good fixes from David Brownell that
solve some bugzilla.kernel.org bug reports.
I've also fixed a stupid issue with the pl2303 driver that some people
were seeing, and got rid of all of
ChangeSet 1.1119.1.8, 2003/08/06 15:51:41-07:00, [EMAIL PROTECTED]
[PATCH] USB: disable both sides of usb device ep0 at once
This eliminates an error case (current cost, memleak) when
disabling endpoints that have control requests queued.
drivers/usb/core/hcd.c |3 ++-
1 files changed, 2 i
On Thu, Aug 07, 2003 at 12:10:33PM +0100, Ian Abbott wrote:
> Ehlo all,
>
> These patches are against clones of Greg's usb-2.4 and usb-2.5 BK
> repositories. It's the first time I've used BK, so I've probably
> done something wrong
>
> Either patch should apply cleanly to either tree, but
On Sat, Aug 09, 2003 at 12:45:43AM +0200, Daniel Blueman wrote:
> When I unplug a USB hub from the root hub, I see this often. I'm on a SiS
> OHCI USB controller.
>
> Let me know if I can provide further information, and please CC me, as
> I'm not on the list.
{sigh, please read the archives...}
I got a report about an USB floppy which is detected more than once,
even with 2.4.22-pre7. A workaround would be the max_scsi_luns=1 or
similar. Is there a fix?
- /proc/bus/usb/devices -
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 12/900 us ( 1%), #I
Alan Stern wrote:
If hcd_endpoint_disable() is called at the same time that an URB is
submitted for that endpoint, there is a nasty race.
This may be just for UHCI.
hcd_endpoint_disable() sets the endpoint maxpacket size to 0, in order to
prevent further submissions. But meanwhile, the HC driv
Am Freitag, 8. August 2003 10:37 schrieb Prageeth:
> hi all,
>
> in my driver i need to provide synchronous read/write
> operations to the application. moreover, operation
> cancellation is also needed.
>
> -what is the most recommended way to wait for
> completion of an urb?
Use a struct compl
Alan Stern writes:
> How does this work? It's a smaller change, against BK-current.
> But maybe David will prefer to change ohci-pci.c instead.
It works fine, and I have been using it for a while now. This, or
something similar, needs to go in, since others have been complaining
about the pro
On Thu, Aug 07, 2003 at 07:17:40PM -0400, Pete Zaitcev wrote:
> Greg, Matt & folks:
>
> There was a tangential report from one of our users that /proc
> seems to get corrupt when usb-storage is rmmod-ed and inserted again.
>
> Kernel 2.6.0-0.test2.1.29 (Arjan's -test2 based RPM).
>
> Problem loo
> But you CAN NOT mark the usb_device_id table as __devinitdata or
> __initdata as that will be touched later on if a new USB device is
> added, or if a new usb module is loaded.
So these need to go.
Regards
Oliver
You can import this changeset into BK by piping this who
Hi. I've been working on writing a USB driver for the Atmel AT43USB355E
device. This chip has an Atmel micro-controller along with a 2 port USB
hub, and a pair of endpoints for the micro-controller. The chip also has
some generic I/O, PWM drivers, ADC, etc. At this point I'm concentrating
on writin
Oliver Neukum wrote:
Halt endpoints by doing a "wrong direction" I/O ... read from an IN endpoint
(instead of writing to the host), or write to an OUT endpoint (instead of
reading what it wrote). ...
That depends on whether you want to design a clean API, or you are
driven by avoiding ioctl, which
15 matches
Mail list logo
