[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAbcLfgYr1gfHNSycDc142aPuNUzxvhQ0GTyvExmMLa36e1nWg@mail.gmail.com>
Date: Wed, 9 Nov 2022 14:44:39 +0000
From: Mark Jackson <mpfj@...flow.co.uk>
To: Tony Lindgren <tony@...mide.com>
Cc: Andreas Kemnade <andreas@...nade.info>,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org
Subject: Re: [PATCH] Update Nanobone
On Wed, 9 Nov 2022 at 07:37, Tony Lindgren <tony@...mide.com> wrote:
>
> The separate defconfig should not be needed. Please send any defconfig
> changes to multi_v7_defconfig or omap2plu_defconfig as separate patches.
>
> Note that you can run make savedefconfig first to produce a minimal diff.
> Then if adding device drivers, please add them as loadable modules where
> possible.
But using the omap2plus_defconfig increases my kernel to 4.7MB
My "custom" one has been specifically designed for the NANO platform
and currently sits at about 3.7MB (which nicely fits into the ~4MB memory
bank allocated to the kernel)
Hence the use of my custom defconfig.
I don't have modules enabled as the platform functionality is pretty fixed.
The defconfig I posted was created using savedefconfig.
Is it still wrong ?
Cheers
Mark J.
Powered by blists - more mailing lists