mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Masahiro YAMADA <mappyland78@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: Rockchip: let boards depend on 32/64bit
Date: Fri, 24 Mar 2023 11:45:12 +0100	[thread overview]
Message-ID: <20230324104512.GB19113@pengutronix.de> (raw)
In-Reply-To: <CAK7LNATzbQYy0JMkRK=Ni9MykzGX-BcLTFhswgf+nNHGzWQ-=A@mail.gmail.com>

On Fri, Mar 24, 2023 at 04:59:56AM +0900, Masahiro YAMADA wrote:
> On Wed, Mar 22, 2023 at 11:09 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> >
> > So far we can enable support for 32bit and 64bit SoCs at the same time
> > which results in an unbuildable barebox. This is annoying, let the board
> > visibility depend on the selected code model.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> 
> 
> What is weird in the current approach is,
> none of "make ARCH=arm64 allnoconfig"
> "make ARCH=arm64 allyesconfig" sets CONFIG_64BIT.
> 
> 
> 
> 
> I think CONFIG_64BIT should be the highest level option,
> which is not selected by anyone, and does not depend on
> any other CONFIG option.

Yes, I've also already realized there's something fishy with the way
32bit vs. 64bit is handled in our Kconfig options, I just didn't know
what to do about it.

Making CONFIG_64BIT the highest level option really seems to solve it
well. I'll send a patch for it shortly.

Thanks for noting and motivating ;)

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2023-03-24 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 14:07 Sascha Hauer
2023-03-23 19:59 ` Masahiro YAMADA
2023-03-24 10:45   ` Sascha Hauer [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=20230324104512.GB19113@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mappyland78@gmail.com \
    /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