All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: balbi@ti.com, Tony Lindgren <tony@atomide.com>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: omap: reduce zImage size on omap2plus_defconfig
Date: Fri, 26 Dec 2014 09:24:38 -0600	[thread overview]
Message-ID: <20141226152438.GE17430@saruman> (raw)
In-Reply-To: <549D4FAA.1040207@compulab.co.il>

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

Hi,

On Fri, Dec 26, 2014 at 02:08:10PM +0200, Igor Grinberg wrote:
> >> I think we should move omap2plus_defconfig to be mostly modular and
> >> usable for distros as a base. Most distros prefer to build almost
> >> everything as loadable modules. And my preference is that we should
> >> only keep the minimum rootfs for devices and serial support as
> >> built-in and rely on initramfs for most drivers. And slowly move
> >> also the remaining built-in drivers to be loadable modules.
> >>
> >> The reasons for having drivers as loadable modules are many. It
> >> allows distros to use the same kernel for all the devices without
> >> bloating the kernel. It makes developing drivers easier as just the
> >> module needs to be reloaded. And loadable modules protect us from
> >> cross-framework spaghetti calls in the kernel as the interfaces are 
> >> clearly defined.
> >>
> >> Are there people really using SATA as rootfs right now on omaps?
> > 
> > not that we know :-) The only platforms available today with SATA are
> > OMAP5432 uEVM and DRA7x EVM,
> 
> I'm sorry... that is not true.

That's not what you have said thus far. So far you only said it *can*
have, you have not explicitly said a customer really *is* using rootfs
on SATA.

Personally, I really don't care. It's just a defconfig patch and
kernel configuration is very, very easy to change at any time. You can
even have an out of tree config fragment just turning SATA=y again.

Have a look at scripts/kconfig/merge_config.sh

> > the latter being mostly used by TIers as of
> > now (at least from mainline point of view).
> 
> the keyword is mostly... And I'm also not sure this is true these days...
> 
> But, really, don't mind me. We will find our solutions (we always did).
> I mean, Felipe wants it out so badly...
> Who am I to say anything...

cute :-)

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: reduce zImage size on omap2plus_defconfig
Date: Fri, 26 Dec 2014 09:24:38 -0600	[thread overview]
Message-ID: <20141226152438.GE17430@saruman> (raw)
In-Reply-To: <549D4FAA.1040207@compulab.co.il>

Hi,

On Fri, Dec 26, 2014 at 02:08:10PM +0200, Igor Grinberg wrote:
> >> I think we should move omap2plus_defconfig to be mostly modular and
> >> usable for distros as a base. Most distros prefer to build almost
> >> everything as loadable modules. And my preference is that we should
> >> only keep the minimum rootfs for devices and serial support as
> >> built-in and rely on initramfs for most drivers. And slowly move
> >> also the remaining built-in drivers to be loadable modules.
> >>
> >> The reasons for having drivers as loadable modules are many. It
> >> allows distros to use the same kernel for all the devices without
> >> bloating the kernel. It makes developing drivers easier as just the
> >> module needs to be reloaded. And loadable modules protect us from
> >> cross-framework spaghetti calls in the kernel as the interfaces are 
> >> clearly defined.
> >>
> >> Are there people really using SATA as rootfs right now on omaps?
> > 
> > not that we know :-) The only platforms available today with SATA are
> > OMAP5432 uEVM and DRA7x EVM,
> 
> I'm sorry... that is not true.

That's not what you have said thus far. So far you only said it *can*
have, you have not explicitly said a customer really *is* using rootfs
on SATA.

Personally, I really don't care. It's just a defconfig patch and
kernel configuration is very, very easy to change at any time. You can
even have an out of tree config fragment just turning SATA=y again.

Have a look at scripts/kconfig/merge_config.sh

> > the latter being mostly used by TIers as of
> > now (at least from mainline point of view).
> 
> the keyword is mostly... And I'm also not sure this is true these days...
> 
> But, really, don't mind me. We will find our solutions (we always did).
> I mean, Felipe wants it out so badly...
> Who am I to say anything...

cute :-)

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141226/cc1531f5/attachment-0001.sig>

  reply	other threads:[~2014-12-26 15:25 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 18:05 [PATCH] arm: omap: reduce zImage size on omap2plus_defconfig Felipe Balbi
2014-12-22 18:05 ` Felipe Balbi
2014-12-22 18:11 ` Felipe Balbi
2014-12-22 18:11   ` Felipe Balbi
2014-12-23  7:30 ` Igor Grinberg
2014-12-23  7:30   ` Igor Grinberg
2014-12-23 16:19   ` Felipe Balbi
2014-12-23 16:19     ` Felipe Balbi
2014-12-23 16:56     ` Tony Lindgren
2014-12-23 16:56       ` Tony Lindgren
2014-12-23 17:07       ` Felipe Balbi
2014-12-23 17:07         ` Felipe Balbi
2014-12-24 11:53     ` Igor Grinberg
2014-12-24 11:53       ` Igor Grinberg
2014-12-24 15:49       ` Felipe Balbi
2014-12-24 15:49         ` Felipe Balbi
2014-12-24 19:04         ` Tony Lindgren
2014-12-24 19:04           ` Tony Lindgren
2014-12-25 10:13           ` Igor Grinberg
2014-12-25 10:13             ` Igor Grinberg
2014-12-26  4:42             ` Felipe Balbi
2014-12-26  4:42               ` Felipe Balbi
2014-12-26 11:56               ` Igor Grinberg
2014-12-26 11:56                 ` Igor Grinberg
2014-12-26 13:42                 ` Javier Martinez Canillas
2014-12-26 13:42                   ` Javier Martinez Canillas
2014-12-26 15:19                   ` Felipe Balbi
2014-12-26 15:19                     ` Felipe Balbi
2014-12-26 19:38                     ` Javier Martinez Canillas
2014-12-26 19:38                       ` Javier Martinez Canillas
2014-12-26 19:47                       ` Felipe Balbi
2014-12-26 19:47                         ` Felipe Balbi
2014-12-26 15:09                 ` Felipe Balbi
2014-12-26 15:09                   ` Felipe Balbi
2014-12-26 16:43                   ` Igor Grinberg
2014-12-26 16:43                     ` Igor Grinberg
2014-12-26 13:04             ` Grygorii.Strashko@linaro.org
2014-12-26 13:04               ` Grygorii.Strashko@linaro.org
2014-12-26 15:26               ` Felipe Balbi
2014-12-26 15:26                 ` Felipe Balbi
2014-12-26 16:13                 ` Tony Lindgren
2014-12-26 16:13                   ` Tony Lindgren
2014-12-26 16:26                   ` Felipe Balbi
2014-12-26 16:26                     ` Felipe Balbi
2015-01-08  0:43                     ` Tony Lindgren
2015-01-08  0:43                       ` Tony Lindgren
2014-12-26  4:37           ` Felipe Balbi
2014-12-26  4:37             ` Felipe Balbi
2014-12-26 12:08             ` Igor Grinberg
2014-12-26 12:08               ` Igor Grinberg
2014-12-26 15:24               ` Felipe Balbi [this message]
2014-12-26 15:24                 ` Felipe Balbi

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=20141226152438.GE17430@saruman \
    --to=balbi@ti.com \
    --cc=grinberg@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 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.