All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Hollis Blanchard <hollis_blanchard@mentor.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH] include usbinit package with usbgadget feature
Date: Thu, 01 Mar 2012 15:02:43 -0800	[thread overview]
Message-ID: <4F500013.1080000@linux.intel.com> (raw)
In-Reply-To: <4F4FFFDE.4090407@mentor.com>



On 03/01/2012 03:01 PM, Hollis Blanchard wrote:
> On 03/01/2012 02:45 PM, Darren Hart wrote:
>> On 03/01/2012 02:26 PM, Hollis Blanchard wrote:
>>> The g_ether kernel module, in the kernel-module-g-ether package, allows
>>> targets to use a USB connection as a network interface. However, that's
>>> not useful until the module is loaded.
>>>
>>> The usbinit package provides the /etc/init.d/usb-gether script to load
>>> the g_ether module at boot, so it should be included along with
>>> kernel-module-g-ether.
>> So if the g-ether kernel module is built-in to the kernel, the
>> kernel-module-g-ether will not be installed (as it's RRECOMMENDS). The
>> usbinit package still will be (unless for some reason it can't be built
>> for the target).
>>
>> I assume this doesn't pose a problem?
> 
> Well, hmm, I don't know. The usb-gether script is not very intelligent, 
> so I suppose that would result in yet another boot time error message. 
> Perhaps testing the result of 'modinfo g_ether' in the script would be a 
> good follow-up patch?
> 

Sounds reasonable to me.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-03-01 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 22:26 [PATCH] include usbinit package with usbgadget feature Hollis Blanchard
2012-03-01 22:45 ` Darren Hart
2012-03-01 23:01   ` Hollis Blanchard
2012-03-01 23:02     ` Darren Hart [this message]
2012-03-06 21:36 ` Hollis Blanchard

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=4F500013.1080000@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=hollis_blanchard@mentor.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.