netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: chripell@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: problem with kernel ipconfig over usb ethernet on v.2.6.33-rc3
Date: Sun, 10 Jan 2010 13:38:48 -0800 (PST)	[thread overview]
Message-ID: <20100110.133848.200626367.davem@davemloft.net> (raw)
In-Reply-To: <cabda6421001100027u1ca339a6ka46470431caa21ba@mail.gmail.com>

From: christian pellegrin <chripell@gmail.com>
Date: Sun, 10 Jan 2010 09:27:48 +0100

> Hi,
> 
> I noticed that kernel IP auto-configuration is not usable for
> USB-ethenet dongles on newer kernel because it starts before the USB
> devices are found (perhaps as a consequence of parallelization of
> kernel boot; the built-in delay of 500ms is not enough).I'm using the
> following patch (with a command line parameter ipconfigdelay=10) to
> solve this situation, but it's a shameless cut & paste from rootdelay.
> Is there any better solution or I'm just missing something?

How long does it actually take for the USB ethernet device
to become visible at this point?

Is 2 seconds enough?  For example.

If so, let's just change CONF_PRE_OPEN to "2" and change
msleep() to ssleep().

It's rediculious to require that users learn about obscure
kernel command line options in order for basic functionality
to work properly.

  reply	other threads:[~2010-01-10 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10  8:27 problem with kernel ipconfig over usb ethernet on v.2.6.33-rc3 christian pellegrin
2010-01-10 21:38 ` David Miller [this message]
2010-01-11  7:18   ` christian pellegrin
2010-03-10 22:33     ` David Miller
2010-03-12  7:50       ` christian pellegrin
2010-03-12  7:55         ` David Miller

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=20100110.133848.200626367.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=chripell@gmail.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).