From: sjoerd.simons@collabora.co.uk (Sjoerd Simons)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
Date: Thu, 08 Oct 2015 11:27:13 +0200 [thread overview]
Message-ID: <1444296433.9895.234.camel@collabora.co.uk> (raw)
In-Reply-To: <26439960.pU0jZ9hpjg@wuerfel>
On Thu, 2015-10-08 at 10:37 +0200, Arnd Bergmann wrote:
> On Thursday 08 October 2015 16:46:27 Krzysztof Kozlowski wrote:
> > On 08.10.2015 16:41, Arnd Bergmann wrote:
> > > On Thursday 08 October 2015 03:48:36 Anand Moon wrote:
> > > > diff --git a/arch/arm/configs/exynos_defconfig
> > > > b/arch/arm/configs/exynos_defconfig
> > > > index 1ff2bfa..5d1937b 100644
> > > > --- a/arch/arm/configs/exynos_defconfig
> > > > +++ b/arch/arm/configs/exynos_defconfig
> > > > @@ -61,6 +61,7 @@ CONFIG_BLK_DEV_DM=y
> > > > CONFIG_DM_CRYPT=m
> > > > CONFIG_NETDEVICES=y
> > > > CONFIG_SMSC911X=y
> > > > +CONFIG_USB_RTL8152=y
> > > > CONFIG_USB_USBNET=y
> > > > CONFIG_USB_NET_SMSC75XX=y
> > > > CONFIG_USB_NET_SMSC95XX=y
> > >
> > > Can we make that a loadable module for multi_v7_defconfig?
> >
> > What about nfsroot boots? We were discussing this also here:
> > http://linux-arm-kernel.infradead.narkive.com/lG5g4hrB/patch-arm-mu
> > lti-v7-defconfig-enable-usb3503
> >
> > and actually I would be happy to see a confirmed policy about that.
> > Everything should be a module for multi_v7?
>
> We try to make as much as possible modular here, and NFS root is a
> corner
> case: it's possible to do NFS root with an initramfs, but it's easier
> not
> to. Is it something you do a lot on this hardware?
It's a workflow thing though, not a hardware specific thing. I
personally tend to use NFS root quite often and so do various
colleagues irrespective of the hardware (and an XU4 is bound to appear
on my desk someday).
Now I personally really don't mind whether NFS root requires a ramdisk
or not (though some consistency would be nice). However deciding it on
a per device basis just makes everything quite fuzzy (e.g. my recent
rockchip multi_v7 patchset first ended up in a similar discussion,
though v2 was merged without further comments when I indicated in the
cover letter that i used the NFS root use-case as one of the deciding
factors for y vs. m).
It would be really good to see someone put their foot down on the
general policy (e.g. the arm-soc maintainers?), such that this
discussion doesn't need to happen every time :)
--
Sjoerd Simons
Collabora Ltd.
next prev parent reply other threads:[~2015-10-08 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 3:48 [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4 Anand Moon
2015-10-08 3:48 ` [PATCHv3 2/2] ARM: multi_v7_defconfig: " Anand Moon
2015-10-08 7:41 ` [PATCHv3 1/2] ARM: exynos_defconfig: " Arnd Bergmann
2015-10-08 7:46 ` Krzysztof Kozlowski
2015-10-08 8:37 ` Arnd Bergmann
2015-10-08 9:27 ` Sjoerd Simons [this message]
2015-10-08 14:41 ` Arnd Bergmann
2015-10-09 3:44 ` Anand Moon
2015-10-09 8:15 ` Arnd Bergmann
2015-10-09 9:59 ` Sjoerd Simons
2015-10-09 10:28 ` Arnd Bergmann
2015-10-09 10:47 ` Krzysztof Kozlowski
2015-10-09 10:52 ` Anand Moon
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=1444296433.9895.234.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).