public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
Date: Fri, 09 Oct 2015 10:15:02 +0200	[thread overview]
Message-ID: <18718651.GRDoBKLmUe@wuerfel> (raw)
In-Reply-To: <CANAwSgS1AKwg8U0WBW8JmveHd0qdRL6RAOV4F4P22a9F28xopQ@mail.gmail.com>

On Friday 09 October 2015 09:14:33 Anand Moon wrote:
> As long as we use correct exynos5422-odroidxu4.dtb is used in the
> boot.scr/boot.ini ethernet come up,
> build and tested using CONFIG_USB_RTL8152=m using multi_v7_defconfig.
> 
> Not sure what is the policy for NFS booting.
> 
> Do you want CONFIG_USB_RTL8152 to be build as module in
> exynos/multi_v7_defconfig.

The NFS booting is exactly the question here: Would it be a significant
hassle for anyone to require using a ramdisk if they need NFS root?

If we all think it would be an acceptable price, we should probably
make all ethernet drivers loadable modules, as it is commonly
done on distros.

	Arnd

  reply	other threads:[~2015-10-09  8:15 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
2015-10-08 14:41         ` Arnd Bergmann
2015-10-09  3:44           ` Anand Moon
2015-10-09  8:15             ` Arnd Bergmann [this message]
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=18718651.GRDoBKLmUe@wuerfel \
    --to=arnd@arndb.de \
    --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