Hi,
Olav Kongas wrote:
Hi,
I'm contemplating removing the option to provide clock() and
reset() functions for isp116x-hcd in platform code. However,
these functions may be necessary for power saving, which
hasn't been a priority for me as none of my platforms is
battery powered.
We have
Hi,
I'm contemplating removing the option to provide clock() and
reset() functions for isp116x-hcd in platform code. However,
these functions may be necessary for power saving, which
hasn't been a priority for me as none of my platforms is
battery powered.
clock() - if implemented by user, th
On Fri, 15 Apr 2005, Konstantin Kletschke wrote:
> Am 2005-04-15 16:47 +0300 schrieb Olav Kongas:
> > time if=a_16MB_file_on_stick of=/dev/null bs=16k
> >
> > yielded here 717 kiB/s.
>
> [EMAIL PROTECTED] ~ # time dd if=/dev/sda of=/dev/null bs=16k count=1024
> 1024+0 records in
> 1024+0 recor
Am 2005-04-15 16:47 +0300 schrieb Olav Kongas:
> More info would be needed to pinpoint the culprit. Does this
> happen with other USB host controllers (no idea, whether you
> need to install linux-wlan-ng driver on test boxen or not)?
I will try another host controller. And no, linux-wlan-ng is
On Fri, 15 Apr 2005, Lothar Wassmann wrote:
> Hi,
>
> On Fri, 15 Apr 2005, Olav Kongas wrote:
> > Leaving aside what may be "the best" way to measure the USB
> > performance, I did it with usb-2.0 memory stick, which was
> > the only device attached at the measurement time. With this
> > con
Hi,
On Fri, 15 Apr 2005, Olav Kongas wrote:
> Leaving aside what may be "the best" way to measure the USB
> performance, I did it with usb-2.0 memory stick, which was
> the only device attached at the measurement time. With this
> controller, it's in full speed mode, of course. Mounting a
> st
On Fri, 15 Apr 2005, Konstantin Kletschke wrote:
> 1.) In 10% of all plug events of the WLAN stick the usb core tells
> "Device Descriptor Read Error" with both of the ohci emulation framework
> and with the isp116x-hcd driver. Is it save to blame the WLAN stick
> itself to be being buggy? In al
Hi people!
Sorry for not informing about the state regarding the isp116x drivers.
I recently posted a lot of questions and weird issues trying to get ehis
beast stable but then came a time of vacation and illness so I will
inform now.
Olav, I took your "[PATCH] isp116x-hcd ready for review" poste
On Friday 04 March 2005 5:32 am, Ian Campbell wrote:
>
> There seem to be a few strange things about the sl811 driver that I
> don't understand, and the changelog says compile tested only so I'll
> bring them up here, and CC you David, since your name is in the
> signed-off-by.
Yes, and you might
Hi,
I have finally put up the possibly last version of the
isp116x driver for 2.6.10: http://www.artecdesign.ee/~ok/isp116x/
A week ago I discussed off-list with David of how to proceed
with the driver. First I will try to improve the
suspend/resume support, which exists currently only for
ports
Hi Olav,
I don't know if you've done any of this already, but I rather
mechanically created the two attached patches by blindly following the
patches made to the sl811h driver... Not really a recipe for success I
admit :-) Fortunately it does seem to work, after some tweaking. I'm not
sure I see a
On Fri, 21 Jan 2005, Alan Stern wrote:
> > What can cause khubd sleeping uninterruptibly? How do debug
> > this?
> >
> > Below is a log about how it all happens. Hints are needed
> > and appreciated.
>
> This was a locking bug in the hub driver for 2.6.9. It has been fixed in
> 2.6.10 (in fact t
On Fri, 21 Jan 2005, Olav Kongas wrote:
> Hi,
>
> When I do plug/unplug cycles with a particular memory stick,
> which has an embedded hub, I get easily khubd hanging into
> uninterruptible sleep. I have made about 100 plug/unplug
> cycles for each of the following devices/combinations
> (keyboar
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 Fri, 21 Jan 2005, Olav Kongas wrote:
>
> Hi,
>
> When I do plug/unplug cycles with a particular memory stick,
> which has an embedded hub, I get easily khubd hanging into
> uninterruptible sleep. I have made about 100 plug/unplug
Forgot to mention, that the testing/logging was done under
2.6
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
Hi,
When I do plug/unplug cycles with a particular memory stick,
which has an embedded hub, I get easily khubd hanging into
uninterruptible sleep. I have made about 100 plug/unplug
cycles for each of the following devices/combinations
(keyboard, externalhub+keyboard [plugging/unplugging hub
cable
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
: [email protected]
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: [email protected]
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: [email protected]
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
Hi, everybody
I find the condition "bstat & ITL1(0)BufferDone" in hc_interrupt() can
never be met.
But when i add "bstat & ITL1(0)BufferFull"flags,it become true in turn
with
certain interval.What the possible problem is? Did i not set the register
correctly,
or it has problems with hardware?
31 matches
Mail list logo
