From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933537AbbJHOmL (ORCPT ); Thu, 8 Oct 2015 10:42:11 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:63427 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933269AbbJHOmJ (ORCPT ); Thu, 8 Oct 2015 10:42:09 -0400 From: Arnd Bergmann To: Sjoerd Simons Cc: linux-arm-kernel@lists.infradead.org, Krzysztof Kozlowski , Lukasz Majewski , linux-samsung-soc@vger.kernel.org, Russell King , Anand Moon , linux-kernel@vger.kernel.org, Javier Martinez Canillas , Kukjin Kim Subject: Re: [PATCHv3 1/2] ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4 Date: Thu, 08 Oct 2015 16:41:15 +0200 Message-ID: <5551783.9EQ5GEjhxX@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1444296433.9895.234.camel@collabora.co.uk> References: <1444276117-3657-1-git-send-email-linux.amoon@gmail.com> <26439960.pU0jZ9hpjg@wuerfel> <1444296433.9895.234.camel@collabora.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:CaA4ieryrqsbUs6gnW647EORRtWr2JxNJAntjVbxrcrJQLsX0nv xOqURiI+1PG1MgxfMxGkN3It+PXPRnuT7yhRtpDiSXdOO6PzkMxO38w7T/x5ZpcskEFomp4 ZJmYbbKcmYUJt01xSRBlH0rX85l8mYUxnAbcJOgW+E1mGcqJ8hyRxFgja9s3Q2Y3FlzWoDV 7VyRhA82LTJVsGZMRsuhw== X-UI-Out-Filterresults: notjunk:1;V01:K0:p4UwBEjX8pU=:0TfDR/x2AGqxrBrYCXBgN9 zOtKGDqmg0dYuAfOl7Tw1kW/KJ9OMpjCLJFbCVqGrkwMBsXWswSkwJbOS9NcQ46nnWSPL/Pi8 neTGDkpVQffdW9t6GVviJXAN9LkTx87YbcWNInILAx/3LClIBlLtqIuOp8K4sgb+M2odi6PI+ 9vPEgHbcpMBW05B77uMVMsKB6JrQuNIL+mXo5vEaAhKruOSqyHokZGOU+K1gCX2mCtV3HJbVk TjQDRU3gzvYQSBnGBlMP/WItg0KUsmk4LdGbfo1UR07ne4PdfJQEm6xNqDyQURRTFqvbT0Dx2 HUSdD6u0k+P9DOb+twkg6f+kI1UrLnjt1kohdg134m6F8QCyGp4uQn0GKs/PDP9wgR1FsFILe g40ZLN/rDjiFWKDs1Ex7Z2/s5eRJF7h+sMwDwMObuvdrwnIn9Jy/vNkAFHTZaBuX0D1Vnh0fb mFggvmoSa/OrFrUqhwhHoUsTZ+0JAmRhdaCid+xMgnHqqaeoMs9xprcFJ7IcL5hkz95vCzmfk S9Ao2N3edYKTXIR6EiPoMN/TZ693mK0IH93INfKqvGaFbPA0E9Bu1d79/BwJSCOykEwLbA5im kNGSP0ujbDFL0CXXHFNeYjOb7ZZRQhj8pEmKKoBSeijp6dEGJXMdeqxNOGbyDwIZp+6rMVY+e OMcypKVMS+5LxwsNgTZMdsqZlOp2C7Uh2iNnJM2RmNygFt3re2V77UCkLizuNHtwIsK0iPAt3 8SxWCZzbN3rAr51L Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 08 October 2015 11:27:13 Sjoerd Simons wrote: > 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 Yes, agreed, that what I'm trying to do here ;-) I realize that building things as modules is a hassle, it is so for some things more than for others, so I keep asking the question to everyone to find out what a good balance is to make as much as possible modules without hurting too much. Once we have a firm policy in place, we should probably change all the existing symbols. Arnd