On Friday 21 January 2005 9:49 am, Olav Kongas wrote:
>
> I have kept an eye on the hcd glue changes and they are
> indeed easy to incorporate. The problem is that the driver
> is still buggy.
It does take a while to get USB controller drivers working!
Though it sounds like you're almost past the
On Thu, 20 Jan 2005, David Brownell wrote:
> I think those 2.6.11 changes can all be characterized as
> streamlining the HCD glue, which will make adding new HCDs
> easier in the future. Most of the 2.4.11 changes are ones
> that should trigger compile time errors with older code.
> So prepping
On Thu, 20 Jan 2005, Philipp Schmid wrote:
> The only non-porting changes (from 2.6.6 - I can't upgrade because of
> customer requirements ...) are the following. As isp116x_write_data16() is
> already correctly swapping bytes for big/little endian, but the PTD payload
> is a byte stream, I nee
Am 2005-01-20 21:32 +0200 schrieb Olav Kongas:
> I have never used the chip with edge-triggered interrupts,
> while it is working in two different designs here as level
> triggered. If your processor supports level-triggered
> interrupts, you should perhaps try using them.
Nice to know, ok. I try
: linux-usb-devel@lists.sourceforge.net
Subject: RE: [linux-usb-devel] isp116x-hcd update
On Thu, 20 Jan 2005, Philipp Schmid wrote:
>
> Yes ... that did it. I've got my USB hard drive back and can do kernel
> compiles on it. However, I don't quite see how that change wou
On Thu, 20 Jan 2005, Konstantin Kletschke wrote:
> The driver indeed runs fine, but nut with our WLAN device.
> Before Debugging this I want to ask if you use your isp116x chip
> interrupts level or edge triggered? I got him edge triggering this day
> but while playing around further (the irq no
On Thursday 20 January 2005 8:07 am, Olav Kongas wrote:
>
> What happened for OUT transfers longer than
> MAX_TRANSFER_SIZE_FULLSPEED was that the first PTD was sent
> and then, without "break-ing" there, the urb was finished
> with return code 0. With this bug, the usbtests worked (at
> least in
Am 2005-01-20 18:07 +0200 schrieb Olav Kongas:
> Great that you see so many tests running flawless, at least
> for 1000 cycles.
The driver indeed runs fine, but nut with our WLAN device.
Before Debugging this I want to ask if you use your isp116x chip
interrupts level or edge triggered? I got him
On Thu, 20 Jan 2005, Philipp Schmid wrote:
>
> Yes ... that did it. I've got my USB hard drive back and can do kernel
> compiles on it. However, I don't quite see how that change would affect
> anything except for preventing the break call under the USB_PID_IN/OUT case
> ...
What happened for
, January 20, 2005 9:35 AM
To: Philipp Schmid
Cc: linux-usb-devel@lists.sourceforge.net
Subject: RE: [linux-usb-devel] isp116x-hcd update
On Wed, 19 Jan 2005, Philipp Schmid wrote:
> I have captured a few dumps when this failure is happening. It ~always~
> happens to the same type of transfer
On Wed, 19 Jan 2005, Philipp Schmid wrote:
> I have captured a few dumps when this failure is happening. It ~always~
> happens to the same type of transfer:
>
> Enqueue: FA 2 ep2in bulk: len 13 short_ok
> pack_fifo @ c5d6/2e9c fmrem
> CC=f EP=2 DIR=2 CNT=0 LEN=13 MPS=64 TGL=1 ACT=1 FA=2 SPD=0 L
DBG("%d: nextpid %d, status %d, err
>
if (ep->nextpid == USB_PID_ACK)
>
ep->nextpid = 0;
spin_unlock(&urb->lock);
spin_unlock(&
On Tue, 18 Jan 2005, Philipp Schmid wrote:
> usb-storage: usb_stor_bulk_transfer_sglist: xfer 1024 bytes, 1 entries
> usb-storage: Status code 0; transferred 832/1024 <= single PTD
> usb-storage: -- short transfer
> usb-storage: Bulk data transfer result 0x1
I haven't seen these mes
age-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Olav
Kongas
Sent: Monday, January 17, 2005 6:39 AM
To: linux-usb-devel@lists.sourceforge.net
Subject: [linux-usb-devel] isp116x-hcd update
Recently there has been some progress with the isp116x
driver. Running usbtests on the dr
Recently there has been some progress with the isp116x
driver. Running usbtests on the driver has revealed bugs,
some of which are fixed by now. The driver has been
under test #10 few nights without errors and I have had all
other tests including unlink and halt tests running
thousands of cycles
15 matches
Mail list logo
