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 23:38:23 +0200 [thread overview]
Message-ID: <ddb713dd-c8d5-4daa-a24f-64c8d213e0ae@lunn.ch> (raw)
In-Reply-To: <CAOYdKdgrpQ9LQvjG7Eg40XtNPonYXmtRmwR=ZERatRJC6osZsA@mail.gmail.com>
On Sun, Jun 25, 2023 at 11:09:21PM +0200, Rogan Dawes wrote:
> I tried adding a &nand block to my device tree, but I think it is not
> quite as simple as that, as I got an error message complaining about
> my additions:
>
> Error: arch/arm/boot/dts/imx28-wink-hub-v1.dts:40.6-11 syntax error
> FATAL ERROR: Unable to parse input tree
Looking at imx28.dtsi, it appears the nand controller is called gpmi,
not nand. So try replacing &namd with &gpmi.
Look at arch/arm/boot/dts/imx28-apf28.dts as an example.
Andrew
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-06-25 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOYdKdhscu_NDetiWDgm7bqh-Tf7kqGMHYOvOE0sQh2dU3t64g@mail.gmail.com>
2023-06-24 14:36 ` Trying to boot mainline on Wink Hub v1 Fabio Estevam
2023-06-25 7:54 ` Rogan Dawes
2023-06-25 15:24 ` Andrew Lunn
2023-06-25 19:31 ` Rogan Dawes
2023-06-25 21:09 ` Rogan Dawes
2023-06-25 21:38 ` Andrew Lunn [this message]
2023-06-26 1:58 ` Rogan Dawes
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=ddb713dd-c8d5-4daa-a24f-64c8d213e0ae@lunn.ch \
--to=andrew@lunn.ch \
--cc=LW@karo-electronics.de \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=rogan@dawes.za.net \
/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