From: Igor Grinberg <grinberg@compulab.co.il>
To: balbi@ti.com
Cc: 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: Wed, 24 Dec 2014 13:53:46 +0200 [thread overview]
Message-ID: <549AA94A.8030209@compulab.co.il> (raw)
In-Reply-To: <20141223161936.GA9147@saruman>
-----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...
>
>>> CONFIG_NETDEVICES=y
>>> # CONFIG_NET_VENDOR_ARC is not set
>>> # CONFIG_NET_CADENCE is not set
>>> @@ -154,8 +151,8 @@ CONFIG_TI_CPSW=y
>>> # CONFIG_NET_VENDOR_WIZNET is not set
>>> CONFIG_AT803X_PHY=y
>>> CONFIG_SMSC_PHY=y
>>> -CONFIG_USB_USBNET=y
>>> -CONFIG_USB_NET_SMSC95XX=y
>>> +CONFIG_USB_USBNET=m
>>> +CONFIG_USB_NET_SMSC95XX=m
>>
>> What about the NFS root for boards with only USB eth?
>
> USB is a module already and it breaks PM when enabled.
Well, USB is not a module currently, but after reading below
I understand you mean HCDs are either disabled or modules.
Ok that's fine with me.
[...]
>>> -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.
- --
Regards,
Igor.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJUmqlKAAoJEBDE8YO64EfaifUQAIdwJFKPozpzVeKJjIYKQgzy
4axv2/Z2TBybF6dlxykrjWwUIX8e24bAtG8uyhnQ/l6NPWVqNqwM/DHALyPBgjMV
EXciALKHyx6DiHoeoTEhhCCocekI/fM9o0mqQHpqzp2M+/UAnHq2Px0pK6Cfk84y
RoyrunlOKOe1rZSbcgZKoZDuMV0qYK2ULpMl3c7QL5sPIGrkWIGe2eTil3/m6jvu
qDaVzGxsBmmCFVxMKv/cXysBd88cswg8sd2ptX7skgptB7lpSKRiAT69c3MXaJyM
zsbE4AE9fiYb0/aZO3hmmWlNp6OM1hxY/8IjL92Sydys/bXxDHQj1fePr9ofsFYM
vSohR6IOopv1xwr6PIKyL+brWJ0p07qKNWA5vrG21D/U0B6H/IPcSbneQtHnMkJl
jf6GccX5gG49MSTDWryFOtErsNXRf6Q5zaZGYTpEsDMXhCKTYJgBhoFX5i3fW4wH
kV/doXku38SAmwRBU0oLjNs07y1I0ijgBHLTtx3XZSd7fkM3CAWsToDapz7df+bx
FAi0+DZk3DVNhJoAeyaRauZQlLU//3McM2zFX8/11K9BP76n6OTanYnjVoJq0SNo
JIjEjmFMFtIF7Zke4JpUCkYlpcW17gQLfUCrcIW1WUq6i0TAGyILmDvZPgMp6+yk
bqMgzSs8ZRXyjqm6Uj7O
=UcBr
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: reduce zImage size on omap2plus_defconfig
Date: Wed, 24 Dec 2014 13:53:46 +0200 [thread overview]
Message-ID: <549AA94A.8030209@compulab.co.il> (raw)
In-Reply-To: <20141223161936.GA9147@saruman>
-----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...
>
>>> CONFIG_NETDEVICES=y
>>> # CONFIG_NET_VENDOR_ARC is not set
>>> # CONFIG_NET_CADENCE is not set
>>> @@ -154,8 +151,8 @@ CONFIG_TI_CPSW=y
>>> # CONFIG_NET_VENDOR_WIZNET is not set
>>> CONFIG_AT803X_PHY=y
>>> CONFIG_SMSC_PHY=y
>>> -CONFIG_USB_USBNET=y
>>> -CONFIG_USB_NET_SMSC95XX=y
>>> +CONFIG_USB_USBNET=m
>>> +CONFIG_USB_NET_SMSC95XX=m
>>
>> What about the NFS root for boards with only USB eth?
>
> USB is a module already and it breaks PM when enabled.
Well, USB is not a module currently, but after reading below
I understand you mean HCDs are either disabled or modules.
Ok that's fine with me.
[...]
>>> -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.
- --
Regards,
Igor.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJUmqlKAAoJEBDE8YO64EfaifUQAIdwJFKPozpzVeKJjIYKQgzy
4axv2/Z2TBybF6dlxykrjWwUIX8e24bAtG8uyhnQ/l6NPWVqNqwM/DHALyPBgjMV
EXciALKHyx6DiHoeoTEhhCCocekI/fM9o0mqQHpqzp2M+/UAnHq2Px0pK6Cfk84y
RoyrunlOKOe1rZSbcgZKoZDuMV0qYK2ULpMl3c7QL5sPIGrkWIGe2eTil3/m6jvu
qDaVzGxsBmmCFVxMKv/cXysBd88cswg8sd2ptX7skgptB7lpSKRiAT69c3MXaJyM
zsbE4AE9fiYb0/aZO3hmmWlNp6OM1hxY/8IjL92Sydys/bXxDHQj1fePr9ofsFYM
vSohR6IOopv1xwr6PIKyL+brWJ0p07qKNWA5vrG21D/U0B6H/IPcSbneQtHnMkJl
jf6GccX5gG49MSTDWryFOtErsNXRf6Q5zaZGYTpEsDMXhCKTYJgBhoFX5i3fW4wH
kV/doXku38SAmwRBU0oLjNs07y1I0ijgBHLTtx3XZSd7fkM3CAWsToDapz7df+bx
FAi0+DZk3DVNhJoAeyaRauZQlLU//3McM2zFX8/11K9BP76n6OTanYnjVoJq0SNo
JIjEjmFMFtIF7Zke4JpUCkYlpcW17gQLfUCrcIW1WUq6i0TAGyILmDvZPgMp6+yk
bqMgzSs8ZRXyjqm6Uj7O
=UcBr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-24 11:54 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 [this message]
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
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=549AA94A.8030209@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=balbi@ti.com \
--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.