mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org,
	"Maxime Ripard" <maxime.ripard@free-electrons.com>
Subject: Re[2]: New dt-only arm/mach
Date: Wed, 13 Mar 2013 08:39:25 +0400	[thread overview]
Message-ID: <1363149565.796232847@f24.mail.ru> (raw)
In-Reply-To: <20130312210408.GV1906@pengutronix.de>

> On Tue, Mar 12, 2013 at 09:50:26PM +0400, Alexander Shiyan wrote:
> > > > 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?
> 
> Where would you put the SDRAM setup then?

I do not know yet :) Development at planning stage. There are many
questions that I am trying to solve. It seems that in order to start, I make
a fixed load initially, and then I will try to use the options from DT.

> I think it shouldn't be a problem to change barebox to compile
> without a board directory if you really don't need one, but I assume
> some board specific code will be left.

---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-03-13  4:39 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   ` Re[2]: " Alexander Shiyan
2013-03-12 18:37     ` Maxime Ripard
2013-03-12 21:04     ` Sascha Hauer
2013-03-13  4:39       ` Alexander Shiyan [this message]
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=1363149565.796232847@f24.mail.ru \
    --to=shc_work@mail.ru \
    --cc=barebox@lists.infradead.org \
    --cc=maxime.ripard@free-electrons.com \
    --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