Re: Trying to boot mainline on Wink Hub v1

From: Andrew Lunn <andrew@lunn.ch>
To: Rogan Dawes <rogan@dawes.za.net>
Cc: "Fabio Estevam" <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"Lothar Waßmann" <LW@karo-electronics.de>,
	"Marek Vasut" <marex@denx.de>
Subject: Re: Trying to boot mainline on Wink Hub v1
Date: Sun, 25 Jun 2023 17:24:22 +0200	[thread overview]
Message-ID: <f2570cf9-d01f-431b-832c-deae7a8f4c61@lunn.ch> (raw)
In-Reply-To: <CAOYdKdhuVbzavb9CJYqOLXX7PYCbOGzmeUg2eTgF1saTviCo-Q@mail.gmail.com>

> I *think* my problem is that U-Boot is not aware of the device tree,
> as I have been passing it as an appended item to the kernel, thinking
> that U-Boot was not Device-Tree compliant. Consequently, it is unable
> to patch it with the contents of the mtdparts environment variable,
> and hence the kernel never knows to go looking for the mtd partitions.

You should be able to fully describe the MTD partition in DT. For
example, from arch/arm/boot/dts/kirkwood-dockstar.dts.

&nand {
        status = "okay";

        partition@0 {
                label = "u-boot";
                reg = <0x0000000 0x100000>;
                read-only;
        };

        partition@100000 {
                label = "uImage";
                reg = <0x0100000 0x400000>;
        };

        partition@500000 {
                label = "data";
                reg = <0x0500000 0xfb00000>;
        };
};

You can then continue with appending the DT blob to the kernel. All
the bootloader needs to do is load the kernel.

    Andrew

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/