From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: ** X-Spam-Status: No, score=2.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1430C433DB for ; Fri, 19 Feb 2021 04:53:56 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 332D764E77 for ; Fri, 19 Feb 2021 04:53:56 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 332D764E77 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94) (envelope-from ) id 1lCxnP-0001Mp-Kb; Thu, 18 Feb 2021 23:53:39 -0500 Received: from mail-vs1-xe29.google.com ([2607:f8b0:4864:20::e29]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1lCxnN-0001Mk-RU for kernelnewbies@kernelnewbies.org; Thu, 18 Feb 2021 23:53:38 -0500 Received: by mail-vs1-xe29.google.com with SMTP id a123so2094959vsc.9 for ; Thu, 18 Feb 2021 20:53:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=U1rlXuxnPVaO7l1+kprzg332P1o38x3/Hn/C9BsDr1U=; b=q4QYVUTeiIUEZXN23cBby2ws3WqaoRqb1l6cHNYFeVDQVQX5UoR49ZHtJvWiC0PLy5 cqu1iUg/tjbyYhN+hSRs86hRn1qcOOLRrd/urOFdHas3pwXoJASzEalHE4Xz2PEeGMIc Kbmez/BB2gvBBOGPwi6xmqfqSjaQxNlmkPYs5EheLT/q0mTnHWrbEaT/reuBjJ/8ZXUn DMKL/yPlRCCJnA36nND6lI2CQDUynAtc22dajYnE1I3lLK4ircnsgJjY9S2FxFt2HVuI NECvwdnS+DEKloJJQLD+Aq8eg0dnYK/9uu3Gu3gXqjKC2w1iLqY9Ehr78zxutDqe16MN 4dUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=U1rlXuxnPVaO7l1+kprzg332P1o38x3/Hn/C9BsDr1U=; b=O7kEUuxvJY23Um8+2sXZxUMsyuqmTgox17o/8qUfP6zb01RNfZ2wDlFUopq4+hvmqx URMYYSr3p8012vKZrChlNJm3vlh2L7uRKNcL+XX494FMGFj59DBViZrEcEOaD22rRfrC Vh+x+QySd53yBQrxprEsDz8/iHbQdeQ5dZFjx86VYtxPyXZRa167G6RzIxd6S3i7D/kI M8KY+Jm6d6aolXPTQ2wTfd/mTvFNUyAUTJnMQkgZe0JoaSl8lbw/4w2GOCHiZ6GWEmtJ QWwHAoFCDBgd4E9hYYCq/3p30vPh4JenFhKk+akoskpmp8nMykILlGiSk46fWmOvWsuY +cQw== X-Gm-Message-State: AOAM533R+s0pnYUyeUrk2zvjHmV8H77LqkaUlZg33OuRJSw2AuNuRdVp N4M7J5YpILu4LLIVTNCL8Guxuw3OOAIioTddLWE= X-Google-Smtp-Source: ABdhPJwDr06LO6AAOCIZ/jIcezY3O5QTld7uT9XMn4yqzp24Egun6Op1BMBqHr7guN9Zg7l8jb3Sd2GA4AOpjWUCqqw= X-Received: by 2002:a67:ee81:: with SMTP id n1mr5657874vsp.60.1613710416264; Thu, 18 Feb 2021 20:53:36 -0800 (PST) MIME-Version: 1.0 References: <020a01d7066c$5120d5e0$f36281a0$@etri.re.kr> In-Reply-To: <020a01d7066c$5120d5e0$f36281a0$@etri.re.kr> From: jim.cromie@gmail.com Date: Thu, 18 Feb 2021 21:53:09 -0700 Message-ID: Subject: Re: Does 'make oldconfig' work across different architectures? To: ckim@etri.re.kr Cc: kernelnewbies X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7141649528168578234==" Errors-To: kernelnewbies-bounces@kernelnewbies.org --===============7141649528168578234== Content-Type: multipart/alternative; boundary="00000000000021c00305bba93cee" --00000000000021c00305bba93cee Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Feb 18, 2021 at 8:07 PM wrote: > Hello folks, > > When we want to use an old .config file for a new kernel build, we can us= e > (place in build location) that .config and do =E2=80=98make oldconfig=E2= =80=99 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 aarch6= 4. > > 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 --00000000000021c00305bba93cee Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Feb 18, 2021 at 8:07 PM <<= a href=3D"mailto:ckim@etri.re.kr">ckim@etri.re.kr> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

Hello folks,

When we want to use an old .config file for a new ker= nel build, we can use (place in build location) that .config and do =E2=80= =98make oldconfig=E2=80=99 so that the build system lets us to fill the new= config variables.

I'm curious if this 'make oldconfig' will work if t= he old .config is from different architecture (like sparc) and I have to co= nfigure it for aarch64.

The old .config file is a minimal configuration with time= r, interrupt controller and uart for minimal linux booting.

Thanks!=C2=A0

=

Chan Kim

______

you need to define "wor= king".

I bet it would work to produce a confi= g that is syntactically correct.
whether it builds a bootable ker= nel is less clear.

Ive only built and installed to= hw 1 non-x86 kernel,
so my experience isnt=C2=A0relevant to othe= r arches, ymmv

ISTM
you should try defco= nfig for aarch64
your .config, updated with oldconfig
d= iff them, see whats=C2=A0happened to various CONFIG vars
--00000000000021c00305bba93cee-- --===============7141649528168578234== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============7141649528168578234==--