From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: USB Ethernet problems
Date: Fri, 05 Apr 2013 16:51:25 +0100 [thread overview]
Message-ID: <1484346.WPBZMnUxrg@helios> (raw)
In-Reply-To: <CAFyqS9pp+O=URfqZz1SGY8xvO7a6Meqk7AnhDuO6YqhdbEP-5w@mail.gmail.com>
On Friday 05 April 2013 16:13:32 Hans Beckérus wrote:
> On Fri, Apr 5, 2013 at 3:59 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> > As for the timing, maybe I've just been very lucky :-) I can see that
> > if the device isn't present when the system runs 'ifup eth0' (or the
> > equivalent) you'll have a problem. That's what connman is for - I don't
> > use it, but it might help you out.
>
> I should take a look at it. But it already sounds like something much
> bigger than this simple system should really need.
> Thanks for all the help so far. If anything else comes to your mind, please
> tell me. I guess I will have to live with my Q&D patch for now ;)
One other possibility I can think of would be using a udev rule to run a
script when the actual hardware detection/insertion event happens.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-05 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 9:08 USB Ethernet problems Hans Beckérus
2013-04-05 10:08 ` Iorga, Cristian
2013-04-05 10:31 ` Hans Beckérus
2013-04-05 10:16 ` Gary Thomas
2013-04-05 12:38 ` Hans Beckérus
2013-04-05 12:48 ` Gary Thomas
2013-04-05 12:57 ` Hans Beckérus
2013-04-05 13:23 ` Gary Thomas
[not found] ` <515ED14E.7010102@mlbassoc.com>
2013-04-05 13:50 ` Hans Beckérus
2013-04-05 13:59 ` Gary Thomas
2013-04-05 14:13 ` Hans Beckérus
2013-04-05 15:51 ` Paul Eggleton [this message]
2013-04-05 16:16 ` Hans Beckérus
2013-04-05 16:26 ` Hans Beckérus
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=1484346.WPBZMnUxrg@helios \
--to=paul.eggleton@linux.intel.com \
--cc=hans.beckerus@gmail.com \
--cc=yocto@yoctoproject.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.