linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: linux@armlinux.org.uk, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: omap2plus_defconfig: add networking over USB device
Date: Tue, 4 Dec 2018 13:52:29 -0800	[thread overview]
Message-ID: <20181204215229.GE6707@atomide.com> (raw)
In-Reply-To: <20181204205901.14620-1-michael.opdenacker@bootlin.com>

Hi,

* Michael Opdenacker <michael.opdenacker@bootlin.com> [181204 12:59]:
> This adds support for networking over USB device,
> which allows boards such as the BeagleBoneBlack Wireless and
> Pocket Beagle to boot on an NFS root filesystem. Such boards
> have no Ethernet port.
> 
> This is for consistency with CONFIG_ROOT_NFS=y
> which makes no sense if there is no networking.

Hmm well this has few issues though:

1. We've had USB as loadable modules for years now to
   cut down on bloat and try to make things more
   distro friendly

2. MUSB has never worked well with PM and enabling
   it almost certainly would break PM for multiple
   devices

3. The USB gadget configuration should be done using
   configfs as it's device and policy  specific and
   Ethernet gadget may not be even desirable

So I suggest just doing what distros do and use a proper
initramfs :)

BTW what works quite nicely for devices with Ethernet
controller is to have u-boot load dtb, kernel and
modules.tar.gz over Ethernet and write it to mmc. That
way the loaded kernel and modules are available on
boot as long as some init script untars modules.tar.gz
first thing when init starts.

Regards,

Tony

      reply	other threads:[~2018-12-04 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 20:59 [PATCH] ARM: omap2plus_defconfig: add networking over USB device Michael Opdenacker
2018-12-04 21:52 ` Tony Lindgren [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=20181204215229.GE6707@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael.opdenacker@bootlin.com \
    /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).