From: Oliver Neukum <oliver@neukum.org>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Problem found: kaweth fails to work on 2.6.12-rc[456]
Date: Wed, 15 Jun 2005 18:52:25 +0200 [thread overview]
Message-ID: <200506151852.25582.oliver@neukum.org> (raw)
In-Reply-To: <20050615165358.GA10993@animx.eu.org>
Am Mittwoch, 15. Juni 2005 18:53 schrieb Wakko Warner:
> Oliver Neukum wrote:
> > > I meant I didn't know the name to number translation.
> >
> > Sorry, ENOENT.
>
> Ok.
>
> > > For the next tests, I think it would be best to remove the 3 printks I added
> > > to show beginning, u->status, and ending. Spews too much stuff =)
> >
> > Please do so and try removing and reattaching the cable.
>
> I removed the printks that were spewing lines that are now no longer useful.
> I left the ones that are in the block for the if statement. There is no
> change when I unplug and replug the ethernet cable. The link light on the
> device does go off. Is it possible that the hardware cannot report link
> state?
It is unfortunately possible. It is even more unfortunately a violation
of the specifications I've got from the manifacturer. Even worse, I don't
know which devices have a working link detection and which don't.
This means that I'll make a patch disabling it for all for the time being.
Regards
Oliver
prev parent reply other threads:[~2005-06-15 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 0:41 Problem found: kaweth fails to work on 2.6.12-rc[456] Wakko Warner
2005-06-12 1:16 ` Wakko Warner
2005-06-12 7:57 ` Oliver Neukum
2005-06-12 13:05 ` Wakko Warner
2005-06-12 15:22 ` Oliver Neukum
2005-06-15 1:02 ` Wakko Warner
2005-06-15 6:29 ` Oliver Neukum
2005-06-15 11:31 ` Wakko Warner
2005-06-15 11:30 ` Oliver Neukum
2005-06-15 16:53 ` Wakko Warner
2005-06-15 16:52 ` Oliver Neukum [this message]
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=200506151852.25582.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=wakko@animx.eu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.