From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Finn Thain <fthain@linux-m68k.org>,
Imre Kaloz <kaloz@openwrt.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Zoltan HERPAI <wigyori@uid0.hu>
Subject: Re: [PATCH] ARM: dts: ixp4xx: Fix up the Netgear WG302 device tree
Date: Fri, 8 Jul 2022 17:29:20 +0200 [thread overview]
Message-ID: <CAMuHMdUEYmYF+R=1X1Y7rwGYkt6kEOBK=vC3fNoFA4HVfDB9=Q@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZ+2aSCDRm=_pLsa8D6tECL-xSkr9K_NaPyZmwkvyqVGQ@mail.gmail.com>
On Fri, Jul 8, 2022 at 3:15 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Fri, Jul 8, 2022 at 5:16 AM Finn Thain <fthain@linux-m68k.org> wrote:
> > Does anyone still have the configs for that test? Here's what I see when I
> > build and boot ixp4xx_defconfig.
> >
> > RedBoot> load -r -b 0x01600000 zImage
> > Using default protocol (TFTP)
> > Raw file loaded 0x01600000-0x018a4087, assumed entry at 0x01600000
> > RedBoot> exec 0x01600000
> > Using base address 0x01600000 and length 0x002a4088
> >
> > Error: invalid dtb and unrecognized/unsupported machine ID
> > r1=0x000000f5, r2=0x00000000
> > Available machine support:
> >
> > ID (hex) NAME
> > ffffffff Generic DT based system
> > ffffffff IXP4xx (Device Tree)
> >
> > Please check your kernel config and/or bootloader.
>
> Usually this is because the DTB is corrupt.
Usually because it gets overwritten due to a bad combination of load
addresses for kernel and DTB, or during copying by the boot loader.
However, this is redboot, using a single load command.
Finn: Does your zImage have an appended DTB?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-08 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 0:28 [PATCH] ARM: dts: ixp4xx: Fix up the Netgear WG302 device tree Linus Walleij
2022-07-08 3:16 ` Finn Thain
2022-07-08 13:07 ` Linus Walleij
2022-07-08 15:29 ` Geert Uytterhoeven [this message]
2022-07-09 7:44 ` Finn Thain
2022-07-09 7:43 ` Finn Thain
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='CAMuHMdUEYmYF+R=1X1Y7rwGYkt6kEOBK=vC3fNoFA4HVfDB9=Q@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=fthain@linux-m68k.org \
--cc=kaloz@openwrt.org \
--cc=khalasa@piap.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=wigyori@uid0.hu \
/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.