All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>, Arnd Bergmann <arnd@arndb.de>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Alexey Romanov <avromanov@sberdevices.ru>,
	Rob Herring <robh+dt@kernel.org>,
	krzysztof.kozlowski+dt@linaro.org, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@sberdevices.ru
Subject: Re: [PATCH v1 0/3] Meson A1 32-bit support
Date: Thu, 09 Mar 2023 13:52:41 -0800	[thread overview]
Message-ID: <7hedpxwq1i.fsf@baylibre.com> (raw)
In-Reply-To: <20230228084952.mgx3d3nw65yo5ebu@CAB-WSD-L081021>

Dmitry Rokosov <ddrokosov@sberdevices.ru> writes:

> On Mon, Feb 27, 2023 at 07:19:38PM +0100, Arnd Bergmann wrote:
>> On Mon, Feb 27, 2023, at 17:50, Dmitry Rokosov wrote:
>> > On Mon, Feb 27, 2023 at 05:38:49PM +0100, Neil Armstrong wrote:
>> >> On 27/02/2023 17:15, Arnd Bergmann wrote:
>> >> > On Mon, Feb 27, 2023, at 16:51, Dmitry Rokosov wrote:
>> >> > 
>> >> > Most of these don't apply in userspace, so the incentive to
>> >> > run smaller 32-bit userland on systems with less than 1GB of
>> >> > RAM usually outweighs the benefits of 64-bit userspace.
>> >> 
>> >> Thanks for the details!
>> >
>> > Looks like Thomas has already prepared a basic patch series for buildroot,
>> > but maintainers declined it.
>> >
>> > https://lore.kernel.org/all/20220730194331.GA2515056@scaer/
>> 
>> I see. I know very little about buildroot, but it sounds like
>> there are other ways of doing the same thing here. In general,
>> this is pretty much an Arm specific problem. While you clearly
>> want compat mode for small userland on any architecture but don't
>> want 32-bit kernels, arm is the only one that has a different
>> kernel "ARCH=" value and needs a separate gcc toolchain.
>> 
>> If the problem is only the toolchain, an easy way out may
>> be to use clang instead of gcc as your compiler, as a single
>> clang binary can target both 32-bit userland and 64-bit kernel
>> on all supported architectures.
>
> Agreed with you. We will try different local approaches to support
> compat build configurations. For now, prebuilt toolchain (buildroot make
> sdk goal) is best way from my point of view. Anyway, we will try to
> solve this problem in the our sandbox and stay on the 64-bit kernel.
> Thank you for all the helpful details you shared, appreciate it!

Just to clarify one thing...

More specifically, this is a buildroot *build system* problem.  If you
build the kernel separately from the rootfs, it works fine. 

I use 32-bit buildroot (and debian) rootfs images all the time on
Amlogic SoCs with 64-bit kernels and it works fine.  

Kevin

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>, Arnd Bergmann <arnd@arndb.de>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Alexey Romanov <avromanov@sberdevices.ru>,
	Rob Herring <robh+dt@kernel.org>,
	krzysztof.kozlowski+dt@linaro.org, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@sberdevices.ru
Subject: Re: [PATCH v1 0/3] Meson A1 32-bit support
Date: Thu, 09 Mar 2023 13:52:41 -0800	[thread overview]
Message-ID: <7hedpxwq1i.fsf@baylibre.com> (raw)
In-Reply-To: <20230228084952.mgx3d3nw65yo5ebu@CAB-WSD-L081021>

Dmitry Rokosov <ddrokosov@sberdevices.ru> writes:

> On Mon, Feb 27, 2023 at 07:19:38PM +0100, Arnd Bergmann wrote:
>> On Mon, Feb 27, 2023, at 17:50, Dmitry Rokosov wrote:
>> > On Mon, Feb 27, 2023 at 05:38:49PM +0100, Neil Armstrong wrote:
>> >> On 27/02/2023 17:15, Arnd Bergmann wrote:
>> >> > On Mon, Feb 27, 2023, at 16:51, Dmitry Rokosov wrote:
>> >> > 
>> >> > Most of these don't apply in userspace, so the incentive to
>> >> > run smaller 32-bit userland on systems with less than 1GB of
>> >> > RAM usually outweighs the benefits of 64-bit userspace.
>> >> 
>> >> Thanks for the details!
>> >
>> > Looks like Thomas has already prepared a basic patch series for buildroot,
>> > but maintainers declined it.
>> >
>> > https://lore.kernel.org/all/20220730194331.GA2515056@scaer/
>> 
>> I see. I know very little about buildroot, but it sounds like
>> there are other ways of doing the same thing here. In general,
>> this is pretty much an Arm specific problem. While you clearly
>> want compat mode for small userland on any architecture but don't
>> want 32-bit kernels, arm is the only one that has a different
>> kernel "ARCH=" value and needs a separate gcc toolchain.
>> 
>> If the problem is only the toolchain, an easy way out may
>> be to use clang instead of gcc as your compiler, as a single
>> clang binary can target both 32-bit userland and 64-bit kernel
>> on all supported architectures.
>
> Agreed with you. We will try different local approaches to support
> compat build configurations. For now, prebuilt toolchain (buildroot make
> sdk goal) is best way from my point of view. Anyway, we will try to
> solve this problem in the our sandbox and stay on the 64-bit kernel.
> Thank you for all the helpful details you shared, appreciate it!

Just to clarify one thing...

More specifically, this is a buildroot *build system* problem.  If you
build the kernel separately from the rootfs, it works fine. 

I use 32-bit buildroot (and debian) rootfs images all the time on
Amlogic SoCs with 64-bit kernels and it works fine.  

Kevin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>, Arnd Bergmann <arnd@arndb.de>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Alexey Romanov <avromanov@sberdevices.ru>,
	Rob Herring <robh+dt@kernel.org>,
	krzysztof.kozlowski+dt@linaro.org, jbrunet@baylibre.com,
	martin.blumenstingl@googlemail.com,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@sberdevices.ru
Subject: Re: [PATCH v1 0/3] Meson A1 32-bit support
Date: Thu, 09 Mar 2023 13:52:41 -0800	[thread overview]
Message-ID: <7hedpxwq1i.fsf@baylibre.com> (raw)
In-Reply-To: <20230228084952.mgx3d3nw65yo5ebu@CAB-WSD-L081021>

Dmitry Rokosov <ddrokosov@sberdevices.ru> writes:

> On Mon, Feb 27, 2023 at 07:19:38PM +0100, Arnd Bergmann wrote:
>> On Mon, Feb 27, 2023, at 17:50, Dmitry Rokosov wrote:
>> > On Mon, Feb 27, 2023 at 05:38:49PM +0100, Neil Armstrong wrote:
>> >> On 27/02/2023 17:15, Arnd Bergmann wrote:
>> >> > On Mon, Feb 27, 2023, at 16:51, Dmitry Rokosov wrote:
>> >> > 
>> >> > Most of these don't apply in userspace, so the incentive to
>> >> > run smaller 32-bit userland on systems with less than 1GB of
>> >> > RAM usually outweighs the benefits of 64-bit userspace.
>> >> 
>> >> Thanks for the details!
>> >
>> > Looks like Thomas has already prepared a basic patch series for buildroot,
>> > but maintainers declined it.
>> >
>> > https://lore.kernel.org/all/20220730194331.GA2515056@scaer/
>> 
>> I see. I know very little about buildroot, but it sounds like
>> there are other ways of doing the same thing here. In general,
>> this is pretty much an Arm specific problem. While you clearly
>> want compat mode for small userland on any architecture but don't
>> want 32-bit kernels, arm is the only one that has a different
>> kernel "ARCH=" value and needs a separate gcc toolchain.
>> 
>> If the problem is only the toolchain, an easy way out may
>> be to use clang instead of gcc as your compiler, as a single
>> clang binary can target both 32-bit userland and 64-bit kernel
>> on all supported architectures.
>
> Agreed with you. We will try different local approaches to support
> compat build configurations. For now, prebuilt toolchain (buildroot make
> sdk goal) is best way from my point of view. Anyway, we will try to
> solve this problem in the our sandbox and stay on the 64-bit kernel.
> Thank you for all the helpful details you shared, appreciate it!

Just to clarify one thing...

More specifically, this is a buildroot *build system* problem.  If you
build the kernel separately from the rootfs, it works fine. 

I use 32-bit buildroot (and debian) rootfs images all the time on
Amlogic SoCs with 64-bit kernels and it works fine.  

Kevin

  reply	other threads:[~2023-03-09 21:52 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 11:50 [PATCH v1 0/3] Meson A1 32-bit support Alexey Romanov
2023-02-22 11:50 ` Alexey Romanov
2023-02-22 11:50 ` Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 1/3] meson: pinctrl: use CONFIG_PINCTRL_A1 with CONFIG_ARM Alexey Romanov
2023-02-22 11:50   ` Alexey Romanov
2023-02-22 11:50   ` Alexey Romanov
2023-03-06 13:45   ` Linus Walleij
2023-03-06 13:45     ` Linus Walleij
2023-03-06 13:45     ` Linus Walleij
2023-03-06 13:49     ` neil.armstrong
2023-03-06 13:49       ` neil.armstrong
2023-03-06 13:49       ` neil.armstrong
2023-03-06 13:52       ` Linus Walleij
2023-03-06 13:52         ` Linus Walleij
2023-03-06 13:52         ` Linus Walleij
2023-02-22 11:50 ` [PATCH v1 2/3] firmware: meson: use CONFIG_MESON_SM " Alexey Romanov
2023-02-22 11:50   ` Alexey Romanov
2023-02-22 11:50   ` Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 3/3] arch/arm: dts: introduce meson-a1 device tree Alexey Romanov
2023-02-22 11:50   ` Alexey Romanov
2023-02-22 11:50   ` Alexey Romanov
2023-02-23  9:08   ` Krzysztof Kozlowski
2023-02-23  9:08     ` Krzysztof Kozlowski
2023-02-23  9:08     ` Krzysztof Kozlowski
2023-02-23  9:09     ` Krzysztof Kozlowski
2023-02-23  9:09       ` Krzysztof Kozlowski
2023-02-23  9:09       ` Krzysztof Kozlowski
2023-02-27 14:39       ` Dmitry Rokosov
2023-02-27 14:39         ` Dmitry Rokosov
2023-02-27 14:39         ` Dmitry Rokosov
2023-02-27 14:41         ` Krzysztof Kozlowski
2023-02-27 14:41           ` Krzysztof Kozlowski
2023-02-27 14:41           ` Krzysztof Kozlowski
2023-02-27  8:15 ` [PATCH v1 0/3] Meson A1 32-bit support neil.armstrong
2023-02-27  8:15   ` neil.armstrong
2023-02-27  8:15   ` neil.armstrong
2023-02-27 14:28   ` Dmitry Rokosov
2023-02-27 14:28     ` Dmitry Rokosov
2023-02-27 14:28     ` Dmitry Rokosov
2023-02-27 14:46     ` neil.armstrong
2023-02-27 14:46       ` neil.armstrong
2023-02-27 14:46       ` neil.armstrong
2023-02-27 16:01       ` Dmitry Rokosov
2023-02-27 16:01         ` Dmitry Rokosov
2023-02-27 16:01         ` Dmitry Rokosov
2023-02-27 14:58     ` Arnd Bergmann
2023-02-27 14:58       ` Arnd Bergmann
2023-02-27 14:58       ` Arnd Bergmann
2023-02-27 15:51       ` Dmitry Rokosov
2023-02-27 15:51         ` Dmitry Rokosov
2023-02-27 15:51         ` Dmitry Rokosov
2023-02-27 16:15         ` Arnd Bergmann
2023-02-27 16:15           ` Arnd Bergmann
2023-02-27 16:15           ` Arnd Bergmann
2023-02-27 16:37           ` Dmitry Rokosov
2023-02-27 16:37             ` Dmitry Rokosov
2023-02-27 16:37             ` Dmitry Rokosov
2023-02-27 16:38           ` Neil Armstrong
2023-02-27 16:38             ` Neil Armstrong
2023-02-27 16:38             ` Neil Armstrong
2023-02-27 16:50             ` Dmitry Rokosov
2023-02-27 16:50               ` Dmitry Rokosov
2023-02-27 16:50               ` Dmitry Rokosov
2023-02-27 18:19               ` Arnd Bergmann
2023-02-27 18:19                 ` Arnd Bergmann
2023-02-27 18:19                 ` Arnd Bergmann
2023-02-28  8:49                 ` Dmitry Rokosov
2023-02-28  8:49                   ` Dmitry Rokosov
2023-02-28  8:49                   ` Dmitry Rokosov
2023-03-09 21:52                   ` Kevin Hilman [this message]
2023-03-09 21:52                     ` Kevin Hilman
2023-03-09 21:52                     ` Kevin Hilman
2023-03-10 15:20                     ` Dmitry Rokosov
2023-03-10 15:20                       ` Dmitry Rokosov
2023-03-10 15:20                       ` Dmitry Rokosov

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=7hedpxwq1i.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=arnd@arndb.de \
    --cc=avromanov@sberdevices.ru \
    --cc=ddrokosov@sberdevices.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@sberdevices.ru \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.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 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.