linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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:26:20 -0600	[thread overview]
Message-ID: <20141226152620.GF17430@saruman> (raw)
In-Reply-To: <549D5CC0.2090408@linaro.org>

Hi,

On Fri, Dec 26, 2014 at 03:04:00PM +0200, Grygorii.Strashko at linaro.org wrote:
> >>>
> >>> Tony, your call
> 
> May be it will be good thing to split this patch. That way more
> information will be stored in commit log about which set of options
> gives us what benefits.  And also, It will allow to continue with
> agreed changes.  ?

can be done, but then again, it's just a defconfig change. Tony, your
call.

> >> 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?
> > 
> > Yes. That is exactly my point.
> > 
> 
> From my side I'd like to note that I know about few ongoing projects
> on DRA7x EVM where SATA is used as rootfs - now It is the fast
> possible way to start Android.

now this is something different. This is evidence that there are people
relying on SATA on rootfs. I'll leave to Tony again.

-- 
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/42c8b39d/attachment.sig>

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

Thread overview: 26+ 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:11 ` Felipe Balbi
2014-12-23  7:30 ` Igor Grinberg
2014-12-23 16:19   ` Felipe Balbi
2014-12-23 16:56     ` Tony Lindgren
2014-12-23 17:07       ` Felipe Balbi
2014-12-24 11:53     ` Igor Grinberg
2014-12-24 15:49       ` Felipe Balbi
2014-12-24 19:04         ` Tony Lindgren
2014-12-25 10:13           ` Igor Grinberg
2014-12-26  4:42             ` Felipe Balbi
2014-12-26 11:56               ` Igor Grinberg
2014-12-26 13:42                 ` Javier Martinez Canillas
2014-12-26 15:19                   ` Felipe Balbi
2014-12-26 19:38                     ` Javier Martinez Canillas
2014-12-26 19:47                       ` Felipe Balbi
2014-12-26 15:09                 ` Felipe Balbi
2014-12-26 16:43                   ` Igor Grinberg
2014-12-26 13:04             ` Grygorii.Strashko@linaro.org
2014-12-26 15:26               ` Felipe Balbi [this message]
2014-12-26 16:13                 ` Tony Lindgren
2014-12-26 16:26                   ` Felipe Balbi
2015-01-08  0:43                     ` Tony Lindgren
2014-12-26  4:37           ` Felipe Balbi
2014-12-26 12:08             ` Igor Grinberg
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=20141226152620.GF17430@saruman \
    --to=balbi@ti.com \
    --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).