µ½ÕâÀï¿´¿´°Éhttp://www.coolzz.com/?id=dasenlind
---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
Am Samstag, 14. Dezember 2002 22:23 schrieb Kari Hameenaho:
> On Sat, 14 Dec 2002 16:44:30 +0100
>
> "Oliver Neukum" <[EMAIL PROTECTED]> wrote:
> > Yes. Either you have a private array, which will lead people to do
> > proper locking, or you have a function and reference counting.
> > But a functio
On Sat, 14 Dec 2002 16:44:30 +0100
"Oliver Neukum" <[EMAIL PROTECTED]> wrote:
> Yes. Either you have a private array, which will lead people to do
> proper locking, or you have a function and reference counting.
> But a function which returns a pointer to a memory area that
> could go away is a re
Toby Milne wrote:
Hi,
I've been experimenting with the Zaurus support and have come across two
problems.
Good to hear from you, and great to see the results of your debugging!
The first (patch against 2.4.20 included) is that the tx_fixup adds 6 bytes
for the CRC and padding, but the logic t
Tony Spinillo wrote:
I changed the 250 to 25 as specified below, in 2.4.21-pre1.
Everything seems to be working. I'm back in EHCI heaven ;)
Well, at least one of us gets to be there ... :)
I will bang it around abit and report any problems.
Great, thanks for the quick feedback! This sh
This should be innocuous; I expect most folk won't notice anything
better (or worse) from this patch unless they're using Intel EHCI.
removing tasklet
- parts of davem's patch (passing pt_regs down)
- remove 'max_completions'
- update cleanup after hc died
- fix an urb unlink oops
This is the rest of the work to remove the tasklet: the non-syntax
portions which affect work scheduling. It's not quite davem's version;
it's got locking updates, which among other things prevent a hang when
the timer kicks in.
This scheduling change is split out from the other parts in case mor
> > The memory footprint is small. The cache footprint is actually increased.
>
> Yes, a bit. But this is the way that device lookups are moving toward.
> Look at the block devices now, no more fixed arrays. Character devices
> are next, and I'm trying to prepare for this.
Nothing a little hash
Hi,
I've been experimenting with the Zaurus support and have come across two
problems.
The first (patch against 2.4.20 included) is that the tx_fixup adds 6 bytes
for the CRC and padding, but the logic to pad the packet if it is a multiple
of the block size in usbnet_start_xmit is working off th
I changed the 250 to 25 as specified below, in 2.4.21-pre1.
Everything seems to be working. I'm back in EHCI heaven ;)
I will bang it around abit and report any problems.
Thanks David and Richard!
Tony
>> handshake() is always returning non-zero due to ETIMEOUT, I've also
tried
>> increasin
Richard CHAN Shih-Ping wrote:
Hi David and list,
Hi Richard ... good problem report, we like! Though I expect
you mean 2.4.21-pre1, not 2.4.20 ...
hcd.c: ehci-hcd @ 00:1d.7, Intel Corp. 82801DB USB EHCI Controller
hcd.c: irq 10, pci mem e0ae7c00
usb.c: new USB bus registered, assigned bus nu
11 matches
Mail list logo
