From: jim.cromie@gmail.com
To: ckim@etri.re.kr
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Does 'make oldconfig' work across different architectures?
Date: Thu, 18 Feb 2021 21:53:09 -0700 [thread overview]
Message-ID: <CAJfuBxzUPJVZeMre4oxq2mH59tKBvSdpmyecV4fAcO67oVWA0Q@mail.gmail.com> (raw)
In-Reply-To: <020a01d7066c$5120d5e0$f36281a0$@etri.re.kr>
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
On Thu, Feb 18, 2021 at 8:07 PM <ckim@etri.re.kr> wrote:
> Hello folks,
>
> When we want to use an old .config file for a new kernel build, we can use
> (place in build location) that .config and do ‘make oldconfig’ so that the
> build system lets us to fill the new config variables.
>
> I'm curious if this 'make oldconfig' will work if the old .config is from
> different architecture (like sparc) and I have to configure it for aarch64.
>
> The old .config file is a minimal configuration with timer, interrupt
> controller and uart for minimal linux booting.
>
> Thanks!
>
Chan Kim
> ______
you need to define "working".
I bet it would work to produce a config that is syntactically correct.
whether it builds a bootable kernel is less clear.
Ive only built and installed to hw 1 non-x86 kernel,
so my experience isnt relevant to other arches, ymmv
ISTM
you should try defconfig for aarch64
your .config, updated with oldconfig
diff them, see whats happened to various CONFIG vars
[-- Attachment #1.2: Type: text/html, Size: 2170 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
parent reply other threads:[~2021-02-19 4:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <020a01d7066c$5120d5e0$f36281a0$@etri.re.kr>]
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=CAJfuBxzUPJVZeMre4oxq2mH59tKBvSdpmyecV4fAcO67oVWA0Q@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=ckim@etri.re.kr \
--cc=kernelnewbies@kernelnewbies.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).