From: "Michael Rothwell" <rothwell@holly-springs.nc.us>
To: "Eric Sandeen" <sandeen@sgi.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: "kaweth" usb ethernet driver in 2.4?
Date: Sun, 4 Feb 2001 18:17:26 -0800 [thread overview]
Message-ID: <002301c08f19$c9020100$8501a8c0@gromit> (raw)
In-Reply-To: <200102040727.f147RAQ14787@513.holly-springs.nc.us> <3A7D919F.F2213EA2@sgi.com>
Thanks. Has Brad Hards made his version available somewhere?
-M
----- Original Message -----
From: "Eric Sandeen" <sandeen@sgi.com>
To: "Michael Rothwell" <rothwell@holly-springs.nc.us>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, February 04, 2001 9:30 AM
Subject: Re: "kaweth" usb ethernet driver in 2.4?
> Michael Rothwell wrote:
>
> > > It also doesn't seem to work in 2.2. :) The original development of
> > > this driver was going on at http://drivers.rd.ilan.net/kaweth/ but
there
> > > have been no updates for quite some time.
> >
> > Well, it doesn't work you _you_ on 2.2, obviously. But it works for us
> > and other people. Can you provide any information to diagnose the
> > problem you're having?
>
> I'm sorry, I should have provided that info. I searched the 'net, and
> saw many people with problems on several mailing lists, and saw no
> solutions, or reports of success, so I assumed that it was a widespread,
> possibly even known, problem with the driver.
>
> I'll preface this by saying that Brad Hards sent me an updated version
> that works much better, at least as long as the module is loaded before
> the device is plugged in.
>
> But here's what I get with a 2.2 kernel and the stock driver:
>
> Kawasaki USB->Ethernet Driver loading...
> usb.c: registered new driver kaweth
> usb.c: USB new device connect, assigned device number 2
> Kawasaki Device Probe (Device number:2): 0x0846:0x1001
> Device at c2192600
> Descriptor length: 12 type: 1
> NetGear EA-101 connected...
> Reading kaweth configuration
> Request type: c0 Request: 0 Value: 0 Index: 0 Length: 12
> usb-uhci.c: interrupt, status 2, frame# 1929
> kaweth control message failed (urb addr: c2c05ca0)
> usb_control/bulk_msg: timeout
> usb-uhci.c: interrupt, status 2, frame# 851
> Actual length: 0, length 18
> Resetting...
> usb-uhci.c: interrupt, status 2, frame# 854
> Downloading firmware at c48abb6c to kaweth device at c31be000...
> Firmware length: 3838
> Request type: 40 Request: ff Value: 0 Index: 0 Length: efe
> usb-uhci.c: interrupt, status 2, frame# 871
> kaweth control message failed (urb addr: c213ab60)
> usb-uhci.c: interrupt, status 2, frame# 877
> usb-uhci.c: interrupt, status 2, frame# 882
> Actual length: 0, length 3838
> Error downloading firmware (-110), no net device created
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 20:22 "kaweth" usb ethernet driver in 2.4? Eric Sandeen
2001-02-04 6:32 ` Michael Rothwell
2001-02-04 17:30 ` Eric Sandeen
2001-02-05 2:17 ` Michael Rothwell [this message]
2001-02-05 16:23 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 4:54 Dunlap, Randy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002301c08f19$c9020100$8501a8c0@gromit' \
--to=rothwell@holly-springs.nc.us \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox