From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: reduce zImage size on omap2plus_defconfig
Date: Wed, 24 Dec 2014 09:49:48 -0600 [thread overview]
Message-ID: <20141224154948.GA423@saruman> (raw)
In-Reply-To: <549AA94A.8030209@compulab.co.il>
Hi,
On Wed, Dec 24, 2014 at 01:53:46PM +0200, Igor Grinberg wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/23/14 18:19, Felipe Balbi wrote:
> > On Tue, Dec 23, 2014 at 09:30:45AM +0200, Igor Grinberg wrote:
> >> Hi Felipe,
> >>
> >> On 12/22/14 20:05, Felipe Balbi wrote:
> >>
> >> [...]
> >>
> >>> CONFIG_SCSI_SCAN_ASYNC=y
> >>> -CONFIG_ATA=y
> >>> -CONFIG_SATA_AHCI_PLATFORM=y
> >>> -CONFIG_MD=y
> >>> +CONFIG_ATA=m
> >>> +CONFIG_SATA_AHCI_PLATFORM=m
> >>
> >> Isn't this needed for the rootfs on SATA devices?
> >
> > there's no known boards with rootfs on SATA. Until then, we can reduce
> > the size.
>
> What makes you say so?
> The decision for rootfs on SATA is taken dynamically.
> OMAP5 boards (specifically cm-t54) can have rootfs on SATA...
I'll leave the decision to Tony. Even though they _can_, they really
don't and IIRC, OMAP5's SATA has so many silicon errata that it'd be
annoying to find that special device which works (e.g it can't negotiate
lower speeds with SATA III devices and it won't support SATA I).
As of today, we don't know of anybody really shipping anything with
rootfs on SATA and distros would rather ship initiramfs than a giant
zImage anyway.
Tony, your call.
> >>> -CONFIG_USB=y
> >>> +CONFIG_HID_GENERIC=m
> >>> +CONFIG_USB_HIDDEV=y
> >>> +CONFIG_USB_KBD=m
> >>> +CONFIG_USB_MOUSE=m
> >>> +CONFIG_USB=m
> >>
> >> So, you don't consider USB a valid rootfs storage option?
> >
> > read the original defconfig. This is *only* for usbcore.ko, EHCI is
> > disabled, XHCI is a module, MUSB is disabled. What will you use for
> > rootfs ?
>
> Yes, thanks for pointing. Now I see indeed this is a sensible thing
> to do and probably should have been done a while ago.
>
> Might be worth addressing/explaining this in the commit message.
right, I'll look at it after holiday season.
--
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/20141224/8a34a38b/attachment.sig>
next prev parent reply other threads:[~2014-12-24 15:49 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 [this message]
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
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=20141224154948.GA423@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).