public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: dv@vollmann•ch (Detlef Vollmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform
Date: Thu, 10 Dec 2015 22:14:25 +0100	[thread overview]
Message-ID: <5669EB31.4050700@vollmann.ch> (raw)
In-Reply-To: <1802654.n0lYxNZ2px@wuerfel>

On 12/10/15 21:59, Arnd Bergmann wrote:
> On Thursday 10 December 2015 20:03:18 Detlef Vollmann wrote:
>> On 12/10/15 14:43, Arnd Bergmann wrote:
>>> On Thursday 10 December 2015 14:18:11 Arnd Bergmann wrote:
>>>> On Thursday 10 December 2015 13:56:05 Detlef Vollmann wrote:
>>
>>>>> The bad news:
>>>>> My own config (which is massivly stripped down) produces a kernel
>>>>> image that's more than 26K bigger than on v4.4-rc3 without any
>>>>> added functionality.
>>>>> The DNS-323 is extremly constrained in space (the whole system
>>>>> including boot loader, kernel and filesystem has to fit into 8M flash).
>>>>> Any ideas how I can get rid of this additional overhead?
>>>>
>>>> Can you send me your config file? I can have a look.
>>>>
>>>
>>> I've done a quick check with an allnoconfig-like test and it seems that
>>> CONFIG_OF is weighing in at around 86K here, with all the other options
>>> it pulls in, comparing an allnoconfig kernel for DS-323 with one that
>>> has CONFIG_OF enabled as well.
>>>
>>> The multiplatform kernel also enables CONFIG_OF unconditionally, but is
>>> otherwise a little smaller than the mach-orion5x based one:
>>>
>>>    text    data     bss     dec     hex filename
>>>  942144   64112   17648 1023904   f9fa0 build/tmp/vmlinux-orion-allno
>>> 1027516   54052   20824 1102392  10d238 build/tmp/vmlinux-multi-plus-orion
>>> 1025320   66020   18744 1110084  10f044 build/tmp/vmlinux-orion-plus-of
>>>
>>> The diff below shows all the differences between orion-allno and
>>> multi-plus-orion.
>> How did you get the orion-allno config and how did you get it compiled?
>> I tried to apply your changes to my config and compile it, but
>> it started silentoldconfig which introduced back 'ARCH_MULTIPLATFORM'
> 
> The first and third row are without my patches, once they are applied,
> ARCH_ORION becomes a sub-option of ARCH_MULTIPLATFORM.
So with your patches it's no longer possible to build a small kernel, correct?

  Detlef

  reply	other threads:[~2015-12-10 21:14 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 15:49 [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform Arnd Bergmann
2015-11-25 15:49 ` [PATCH 1/5] ARM: orion: move watchdog setup to mach-orion5x Arnd Bergmann
2015-11-25 15:49 ` [PATCH 2/5] ARM: orion: always use MULTI_IRQ_HANDLER Arnd Bergmann
2015-11-25 15:49 ` [PATCH 3/5] ARM: orion: use SPARSE_IRQ everywhere Arnd Bergmann
2015-11-25 15:49 ` [PATCH 4/5] ARM: orion: clean up mach/*.h headers Arnd Bergmann
2015-11-25 15:49 ` [PATCH 5/5] ARM: orion: multiplatform support Arnd Bergmann
2015-11-25 16:09 ` [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform Andrew Lunn
2015-11-25 17:34   ` Gregory CLEMENT
2015-11-25 17:44     ` Andrew Lunn
2015-11-25 19:58       ` Arnd Bergmann
2015-11-26 14:50         ` Jason Cooper
2015-11-25 18:37   ` Russell King - ARM Linux
2015-11-25 19:16     ` Andrew Lunn
2015-11-25 19:29       ` Russell King - ARM Linux
2015-11-25 23:19       ` Russell King - ARM Linux
2015-11-25 20:05     ` Arnd Bergmann
2015-11-25 22:47       ` Russell King - ARM Linux
2015-11-25 20:14 ` Andrew Lunn
2015-11-30 13:37 ` Gregory CLEMENT
2015-11-30 13:43   ` Gregory CLEMENT
2015-12-01 17:22     ` Detlef Vollmann
2015-12-02 11:08       ` Gregory CLEMENT
2015-12-02 14:55         ` Andrew Lunn
2015-12-10 12:56     ` Detlef Vollmann
2015-12-10 13:18       ` Arnd Bergmann
2015-12-10 13:43         ` Arnd Bergmann
2015-12-10 19:03           ` Detlef Vollmann
2015-12-10 20:59             ` Arnd Bergmann
2015-12-10 21:14               ` Detlef Vollmann [this message]
2015-12-10 21:29                 ` Arnd Bergmann
2015-12-10 22:00                   ` Detlef Vollmann
2015-12-10 23:10                     ` Arnd Bergmann
2015-12-11 13:36                       ` Jason Cooper
2015-12-11 14:46                         ` Arnd Bergmann
2015-12-11 14:55                           ` Jason Cooper
2015-12-11 22:41                             ` Detlef Vollmann
2015-12-11 18:27                         ` Josh Triplett
2015-12-11 18:46                           ` Jason Cooper
2015-12-11 19:08                             ` Josh Triplett
2015-12-11 19:14                               ` Jason Cooper
     [not found]         ` <5669808F.2050909@vollmann.ch>
2015-12-11 21:33           ` Arnd Bergmann
2015-12-11 23:18             ` Detlef Vollmann
2015-12-01 22:51   ` Andrew Lunn
2015-12-01 22:55     ` Arnd Bergmann
2015-12-02 11:03     ` Gregory CLEMENT
2015-12-02 12:33   ` Russell King - ARM Linux
2015-12-02 15:49     ` Arnd Bergmann
2015-12-02 19:28       ` Russell King - ARM Linux
2015-12-02 19:37         ` Russell King - ARM Linux
2015-12-02 19:54           ` Arnd Bergmann
2015-12-02 19:51         ` Arnd Bergmann
2015-12-02 20:22           ` Russell King - ARM Linux
2015-12-02 20:38             ` Andrew Lunn
2015-12-02 21:03               ` Russell King - ARM Linux
2015-12-02 21:15               ` Arnd Bergmann
2015-12-02 23:59                 ` Andrew Lunn

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=5669EB31.4050700@vollmann.ch \
    --to=dv@vollmann$(echo .)ch \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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