[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o7vuzyr8.fsf@dell.be.48ers.dk>
Date: Sun, 04 Sep 2022 22:10:51 +0200
From: Peter Korsgaard <peter@...sgaard.com>
To: <Conor.Dooley@...rochip.com>
Cc: <samuel@...lland.org>, <wens@...e.org>, <jernej.skrabec@...il.com>,
<linux-sunxi@...ts.linux.dev>, <palmer@...belt.com>,
<paul.walmsley@...ive.com>, <aou@...s.berkeley.edu>,
<linux-riscv@...ts.infradead.org>, <robh+dt@...nel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <heiko@...ech.de>
Subject: Re: [PATCH 07/12] riscv: dts: allwinner: Add Allwinner D1 Nezha
devicetree
>>>>> <Conor.Dooley@...rochip.com> writes:
> Hey Samuel,
> Finally got around to giving this a go with the fix for loading
> modules which is mostly what was blocking me before..
> On 15/08/2022 06:08, Samuel Holland wrote:
>> "D1 Nezha" is Allwinner's first-party development board for the D1 SoC.
>> It was shipped with 512M, 1G, or 2G of DDR3. It supports onboard audio,
> I am really not keen on the way you have things, with the memory
> nodes removed from the device tree. I know your preferred flow
> for booting these things might be to pass the dtb up from U-Boot,
> but I think the devicetree in the kernel should be usable in a
> standalone manner, even if that is the barest-minimum memory
> config.
Yes, this also confused me. Part of the reason seems to be that u-boot
on RISC-V doesn't fixup the memory node of a provided device tree like
it is done on E.G. ARM for some reason.
--
Bye, Peter Korsgaard
Powered by blists - more mailing lists