From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alex Vazquez <avazquez.dev@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Fwd: boot kernel with append device tree
Date: Mon, 7 Nov 2016 10:48:02 +0100 [thread overview]
Message-ID: <20161107094802.bhy2wowbri7q3sra@pengutronix.de> (raw)
In-Reply-To: <CAOTEMUR=cw8C7K6SwUtUs1PjJB2f8OCBMsmPd1Pe_gwGWJpGfA@mail.gmail.com>
On Mon, Nov 07, 2016 at 09:25:41AM +0100, Alex Vazquez wrote:
> Hi Sasha!
>
> > Which version are you using. Is it something older?
>
> I am using barebox-2016.03.0
>
>
> Regards!
>
> 2016-11-07 8:49 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
> > Hi Alex,
> >
> > Added the list to Cc
> >
> > Please configure your mailer to send plain text, then the server won't
> > reject your mails.
> >
> > On Fri, Nov 04, 2016 at 01:10:30PM +0100, Alex Vazquez wrote:
> >> Hi, all!
> >> I have create a zImage with the device tree appended.
> >> I have removed oftree_loc in the configuration file.
> >> My problem is when I try to launch the kernel, it indicates that it has
> >> the device tree added but fails to boot.
> >>
> >> barebox:/# boot
> >> booting kernel from /dev/[1]nand0.kernel.bb
> >> Loading ARM Linux zImage '/dev/[2]nand0.kernel.bb'
> >> zImage: concatenated oftree detected
> >> commandline: console=ttyS0,115200 rw ip=none ...
> >> arch_number: 0
> >>
> >> If I don't removed oftree_loc in the configuration file. Load oftree
> >> (nand) and boot fine.
> >>
> >> barebox:/# boot
> >> booting kernel from /dev/[3]nand0.kernel.bb
> >> Loading ARM Linux zImage '/dev/[4]nand0.kernel.bb'
> >> zImage: concatenated oftree detected
> >> Loading devicetree from '/dev/[5]nand0.oftree.bb'
> >> commandline: console=ttyS0,115200 rw ip=none ...
> >> Booting Linux on physical CPU 0x0
Is CONFIG_OFTREE enabled in your build?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-11-07 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOTEMUR=FtB_Ox++XPvomyHXsk5Jcm7CG7aEM6WmN++t0211Aw@mail.gmail.com>
[not found] ` <CAOTEMUQt95XDorid8sj9FHkpCpUJYnqNeRbBU+33aLYz2oM+gw@mail.gmail.com>
2016-11-07 7:49 ` Sascha Hauer
2016-11-07 8:25 ` Alex Vazquez
2016-11-07 9:48 ` Sascha Hauer [this message]
2016-11-07 11:01 ` Alex Vazquez
2016-11-08 7:29 ` Sascha Hauer
2016-11-09 8:41 ` Alex Vazquez
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=20161107094802.bhy2wowbri7q3sra@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=avazquez.dev@gmail.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox