From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re[2]: New dt-only arm/mach
Date: Sun, 10 Mar 2013 19:05:06 +0400 [thread overview]
Message-ID: <1362927906.6739510@f386.i.mail.ru> (raw)
In-Reply-To: <20130310145206.GO1906@pengutronix.de>
> Hi Alexander,
>
> On Sun, Mar 10, 2013 at 06:13:43PM +0400, Alexander Shiyan wrote:
> > Hello All.
> >
> > I want to add new arch into barebox. n the kernel this arch is dt-only.
> > I talking about mach-sunxi. So, how we should handle such platform
> > in the barebox? We need always provide dtb to the kernel, then where
> > it should be in barebox?
>
> You asked me privatly whether we should put dtc and friends into
The previous question was about the architecture that can be loaded
without dtb. Now a little another. :)
> barebox, by that time I answered it needs some more time. Maybe this
> time has come now. I currently have a branch in the making to add dtc
> support and also integration into barebox.
>
> With this we are able to compile a dts(p) and link the binary into
> barebox, so...
>
> > I think about dtb-file in /env, but not sure...
>
> ...you could provide a dtb in the binary *)
>
> Furthermore you could probe barebox itself from the devicetree.
>
> I'm still not sure whether we should add fullblown devicetrees into
> barebox or stripped down versions with only the devices barebox needs.
> I think time will tell.
>
> Give me some hours time, I think then I can post a first version of the
> patches.
OK. Np. I just want to tell that we already have dt-only archs.
>
> *) This of course shouldn't mean it can't be overwritten with another
> dtb during runtime.
Or provide dts in /env and compile it in runtime.
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-03-10 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 14:13 Alexander Shiyan
2013-03-10 14:52 ` Sascha Hauer
2013-03-10 15:05 ` Alexander Shiyan [this message]
2013-03-10 20:52 ` Maxime Ripard
2013-03-12 17:50 ` Re[2]: " Alexander Shiyan
2013-03-12 18:37 ` Maxime Ripard
2013-03-12 21:04 ` Sascha Hauer
2013-03-13 4:39 ` Re[2]: " Alexander Shiyan
2013-03-11 11:04 ` 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=1362927906.6739510@f386.i.mail.ru \
--to=shc_work@mail.ru \
--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