From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: New dt-only arm/mach
Date: Tue, 12 Mar 2013 19:37:34 +0100 [thread overview]
Message-ID: <513F75EE.9030209@free-electrons.com> (raw)
In-Reply-To: <1363110626.497378554@f165.mail.ru>
Hi,
Le 12/03/2013 18:50, Alexander Shiyan a écrit :
>> Le 10/03/2013 15:13, Alexander Shiyan a écrit :
>> 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.
Yes, thanks, I'm pretty familiar with the kernel code for mach-sunxi...
Barebox is not the kernel. And there's already a number of other
architectures that are supported in barebox that boot a kernel that
supports only the device tree, like Jean-Christophe said, such as imx,
mxs, highbank, at91, etc...
So, really, there's nothing fancy about supporting an architecture which
*kernel* requires device tree.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-03-12 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 14:13 New dt-only arm/mach 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 ` Re[2]: " Alexander Shiyan
2013-03-12 18:37 ` Maxime Ripard [this message]
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=513F75EE.9030209@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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.