The transfer/setup problem probably indicates that your pci_map_single
code (which you had to write for the SH processor, as I recall) is not
behaving correctly.
Sounds like you may not be using the correct version of the pci_pool
code, or there's some problem caused by other changes you've made.
The pre5 code should behave OK, modulo that problem Paulus just
reported (maybe related to an urb timeout mixup).
- Dave
----- Original Message -----
From: "Orazio Privitera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, April 23, 2001 3:17 AM
Subject: [linux-usb-devel] Usb Driver: problem with pci_pool_alloc.
> Hallo,
>
> I have tried to use the pcipool patch (and the usb-ohci0323 and 0324
> patchs ) for my architecture, but I have a problem with pci_pool_alloc
> call inside td_alloc function:
>
> I get always the same address for my td.
> I haven't yet investigate about this problem, and now I use
> pci_alloc_consistent to allocate my td (and also for dev allocation in
> dev_alloc function).
>
> Could you give any help please?
>
> Another problem is about the buffers used for transfer and setup:
>
> I have changed usb.c and hub.c to allocate all the buffers used for
> setup and transfer (urb-> transfer_buffer and urb->setup_packet) in
> memory behind PCI.In the original code these buffers have been allocated
> in memory regions that from PCI side I could not access.
>
> What is your opinion about this question?
>
>
> Now my usb keyboard and mouse go correctly.
>
> Best regards
>
> Orazio.
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
