From: Tony Lindgren <tony@atomide.com>
To: Mark Jackson <mpfj@newflow.co.uk>
Cc: Andreas Kemnade <andreas@kemnade.info>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] Update Nanobone
Date: Thu, 10 Nov 2022 09:11:56 +0200 [thread overview]
Message-ID: <Y2ykPDybdUaxJy4i@atomide.com> (raw)
In-Reply-To: <CAAbcLfgYr1gfHNSycDc142aPuNUzxvhQ0GTyvExmMLa36e1nWg@mail.gmail.com>
Hi,
* Mark Jackson <mpfj@newflow.co.uk> [221109 14:35]:
> On Wed, 9 Nov 2022 at 07:37, Tony Lindgren <tony@atomide.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.
Maybe host your defconfig somewhere on a device related wiki page?
We got rid of the board specific config files in the kernel years ago in
favor of just a few generic ones.
> I don't have modules enabled as the platform functionality is pretty fixed.
OK nothing wrong with that, multi_v7_defconfig and omap2plus_defconfig are
trying to be more generic and distro friendly.
> The defconfig I posted was created using savedefconfig.
> Is it still wrong ?
Nothing wrong with that, except it should be hosted with the device
related documentation and not in the kernel :)
Regards,
Tony
prev parent reply other threads:[~2022-11-10 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 14:39 [PATCH] Update Nanobone Mark Jackson
2022-11-08 17:18 ` Mark Jackson
2022-11-08 18:47 ` Andreas Kemnade
2022-11-09 7:37 ` Tony Lindgren
2022-11-09 14:44 ` Mark Jackson
2022-11-10 7:11 ` Tony Lindgren [this message]
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=Y2ykPDybdUaxJy4i@atomide.com \
--to=tony@atomide.com \
--cc=andreas@kemnade.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpfj@newflow.co.uk \
/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.