From: Greg KH <greg@kroah.com>
To: rob1@rekl.yi.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: IP Autoconfig doesn't work for USB network devices
Date: Mon, 18 Mar 2002 16:57:14 -0800 [thread overview]
Message-ID: <20020319005714.GC27993@kroah.com> (raw)
In-Reply-To: <20020315230131.GC5563@kroah.com> <Pine.LNX.4.40.0203161810290.16559-100000@rekl.dyn.dhs.org>
On Sat, Mar 16, 2002 at 06:25:30PM -0600, rob1@rekl.yi.org wrote:
>
> There is no perceptible delay between these messages, so it seems like the
> code to detect the USB devices executes after the IP autoconfig section,
> which is what is preventing this from working.
It looks like you need to move the delay section of that patch, possibly
changing the logic in the IP autoconfig section to delay until your
device shows up on the USB bus.
> Is this a topic that should be discussed on one of the linux-usb lists
> instead of linux-kernel?
I think this a good enough place for it, as it isn't very specific to a
USB subsystem problem.
greg k-h
next prev parent reply other threads:[~2002-03-19 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 2:29 IP Autoconfig doesn't work for USB network devices rob1
2002-03-15 23:01 ` Greg KH
2002-03-17 0:25 ` rob1
2002-03-19 0:57 ` Greg KH [this message]
2002-03-19 23:29 ` Eric Lammerts
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=20020319005714.GC27993@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob1@rekl.yi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox