From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Maxime Ripard" <maxime.ripard@free-electrons.com>
Cc: barebox@lists.infradead.org
Subject: Re[2]: New dt-only arm/mach
Date: Tue, 12 Mar 2013 21:50:26 +0400 [thread overview]
Message-ID: <1363110626.497378554@f165.mail.ru> (raw)
In-Reply-To: <513CF27B.6080802@free-electrons.com>
> Le 10/03/2013 15:13, Alexander Shiyan a écrit :
> > Hello All.
> >
> > I want to add new arch into barebox. n the kernel this arch is
> > dt-only. I talking about mach-sunxi.
>
> Wow, that would be great :)
>
> I've been thinking about doing this for quite some time now, but I don't
> have so much time to do both the kernel and barebox ports, so it didn't
> go further than "it would be cool".
>
> > 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?
>
> There's no strong requirements here. It can be anywhere as long as
> barebox knows how and where to find it, basically like the kernel image,
> so it can be from a MMC, TFTP, etc.
>
> But really, the fact that sunxi is only bootable through device tree
> doesn't change a thing compared to other platforms with device tree
> support: the bootloader has to load the kernel image, the dtb and that's it.
>
> > I think about dtb-file in /env, but not sure... Thanks.
>
> It can be done as well I guess, but that doesn't sound that familiar
> from what I've seen in the other barebox boards.
Kernel no contain any board for mach-sunxi.
This mean than all stuff is described via DT.
In the barebox we should have "mach" & "board", so I think we
should create empty (fake) board for architectures like this.
Any other opinions?
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-03-12 17:50 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 ` Re[2]: " Alexander Shiyan
2013-03-10 20:52 ` Maxime Ripard
2013-03-12 17:50 ` Alexander Shiyan [this message]
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=1363110626.497378554@f165.mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.org \
--cc=maxime.ripard@free-electrons.com \
/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