From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Porting barebox to Novena: misc questions
Date: Mon, 17 Mar 2014 08:31:53 +0100 [thread overview]
Message-ID: <20140317073150.GA21767@omega> (raw)
In-Reply-To: <20140317071857.GH17250@pengutronix.de>
On Mon, Mar 17, 2014 at 08:18:58AM +0100, Sascha Hauer wrote:
> On Mon, Mar 17, 2014 at 12:28:28PM +0800, Sean Cross wrote:
> > Here is the resulting output and BUG from this run:
> >
> > barebox 2014.03.0-00628-g7fed07d-dirty #158 Mon Mar 17 12:25:45 SGT 2014
> >
> >
> > Board: Kosagi i.MX6DL Novena Board
> > detected i.MX6 DualLite revision 1.1
> > Trying to request region ttb (from 0x4fff4000:0x4fff7fff): ok
> > Trying to request region malloc space (from 0x4be00000:0x4fdfffff): ok
> > Trying to request region barebox (from 0x4fe00000:0x4fe4b4a7): ok
> > Trying to request region barebox data (from 0x4fe4b4a8:0x4fe5c8f7): ok
> > Trying to request region bss (from 0x4fe5c8f8:0x4fe6214f): ok
> > Trying to request region stack (from 0x4fff8000:0x4fffffff): ok
> > mmu: find_pte: TTB for address 0x4cd1e000 is not of type table
> > mmu: Memory banks:
> > mmu: #0 0x10000000 - 0xffffffff
>
> So you have one memory bank that starts at 0x10000000 which is the
> standard SDRAM base for i.MX6. Good. But why is the size 0? Have you
> specified this in your devicetree? It should contain the correct size.
> It could also be that we do not parse #ddress-cells / #size-cells
> correctly (in case one of these is not 1 in your devicetree).
>
does this smells like an error case which we should handle with a slightly
eprintf? :-)
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-03-17 7:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 2:04 Sean Cross
2014-03-13 7:38 ` Sascha Hauer
2014-03-13 10:18 ` Sean Cross
2014-03-13 20:27 ` Sascha Hauer
2014-03-14 3:35 ` Sean Cross
2014-03-14 8:22 ` Sascha Hauer
2014-03-17 4:28 ` Sean Cross
2014-03-17 7:18 ` Sascha Hauer
2014-03-17 7:31 ` Alexander Aring [this message]
2014-03-17 7:44 ` Sean Cross
2014-03-17 10:53 ` Sascha Hauer
2014-03-18 3:35 ` Sean Cross
2014-03-18 8:36 ` Sascha Hauer
2014-03-18 8:43 ` Sean Cross
2014-03-18 8:58 ` Sascha Hauer
2014-03-18 9:04 ` Sean Cross
2014-03-13 19:42 ` Jean-Christophe PLAGNIOL-VILLARD
2014-03-13 20:30 ` Sascha Hauer
2014-03-14 3:03 ` Jean-Christophe PLAGNIOL-VILLARD
2014-03-13 20:43 ` Eric Bénard
2014-03-13 21:26 ` Sascha Hauer
2014-03-14 3:13 ` Jean-Christophe PLAGNIOL-VILLARD
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=20140317073150.GA21767@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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