mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: barebox@lists.infradead.org,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCH 3/5] arm: initial support for Marvell Dove SoCs
Date: Mon, 13 May 2013 17:14:17 +0200	[thread overview]
Message-ID: <51910349.5040906@gmail.com> (raw)
In-Reply-To: <20130513162313.4f5849a9@skate>

On 05/13/13 16:23, Thomas Petazzoni wrote:
> Dear Sebastian Hesselbarth,
>
> On Mon, 13 May 2013 15:06:55 +0200, Sebastian Hesselbarth wrote:
>
>>> Please note that normally barebox images are expected to be runnable
>>> second stage (bootm barebox.bin). Though not really mandatory this still
>>> is a nice feature for development. This becomes difficult to support if
>>> the initial code expects the registers at 0xd0000000, hence I suggested
>>> remapping it in the kwb image so that all second stage code can already
>>> work on the remapped registers.
>>
>> Yeah, this is bugging Thomas and me for some time. The tricky part in
>> this is, that the register for setting the internal register base is in
>> the internal registers itself. You don't know the base address, you
>> cannot remap it - you can't even read it. Thomas is working on
>> something, but he will have to comment on that.
>
> One solution for Barebox is to have a DATA line in our kwbimage.cfg
> that does:
>
> DATA 0xd0020080 0xf1000000
>
> and so when Barebox boots, the remapping to 0xf1 is already done, and
> we don't have to worry about it. This way, a Barebox can chainload a
> second Barebox.

Yeah, maybe that is the best plan. There is that bootrom feature, and
this way we don't have to mess with it in barebox. But we should also
remap the other registers for memctrl similar.

>> I will flip through the patches we have for DT and see if we have a
>> stable MVEBU like what is in -next now first or rework it before it
>> moves to stable. I want Thomas to fully comment on my DT patches first,
>> but I guess he is busy ATM.
>>
>> Regarding DT, I sent a patch that adds basic address translation we need
>> because we are heavily using "ranges" property in our dtbs. We should
>> also add pci and isa bus style mapping, but that can come later.
>>
>> There is more issues I found with boolean properties but haven't
>> investigated yet.
>
> I believe we should get your existing Dove patches merged, merge the
> Kirkwood patches I have almost ready, and only then converge on the DT +
> remapping support. Would you agree with this plan?

Agree, the DT conversion is straight forward from what we now have. And
if current non-DT gets stable before we also push DT, we do it in the
next cycle.

Sebastian


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

  reply	other threads:[~2013-05-13 15:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 13:09 [PATCH 0/5] Initial " Sebastian Hesselbarth
2013-05-12 13:09 ` [PATCH 1/5] scripts: kwbimage: add references to Marvell Dove SoC Sebastian Hesselbarth
2013-05-12 13:09 ` [PATCH 2/5] scripts: kwboot: add support for Marvell Dove Sebastian Hesselbarth
2013-05-12 16:48   ` Thomas Petazzoni
2013-05-12 13:09 ` [PATCH 3/5] arm: initial support for Marvell Dove SoCs Sebastian Hesselbarth
2013-05-12 16:49   ` Thomas Petazzoni
2013-05-12 16:51     ` Sebastian Hesselbarth
2013-05-12 17:19       ` Thomas Petazzoni
2013-05-12 17:26         ` Sebastian Hesselbarth
2013-05-13  7:58   ` Sascha Hauer
2013-05-13  9:17     ` Sebastian Hesselbarth
2013-05-13 10:57       ` Sascha Hauer
2013-05-13 13:06         ` Sebastian Hesselbarth
2013-05-13 14:11           ` Sascha Hauer
2013-05-13 14:23           ` Thomas Petazzoni
2013-05-13 15:14             ` Sebastian Hesselbarth [this message]
2013-05-13 16:12             ` Sebastian Hesselbarth
2013-05-13 16:21               ` Thomas Petazzoni
2013-05-13 16:30                 ` Sebastian Hesselbarth
2013-05-13 16:34                   ` Thomas Petazzoni
2013-05-13 16:48                     ` Sebastian Hesselbarth
2013-05-13 17:14                       ` Thomas Petazzoni
2013-05-13 17:42                         ` Sebastian Hesselbarth
2013-05-15  5:55       ` Sascha Hauer
2013-05-15  6:20         ` Sebastian Hesselbarth
2013-05-15  6:39           ` Sascha Hauer
2013-05-15  6:48             ` Sebastian Hesselbarth
2013-05-15  7:29           ` Thomas Petazzoni
2013-05-15  8:03             ` Lucas Stach
2013-05-15  8:11               ` Thomas Petazzoni
2013-05-15  7:26         ` Thomas Petazzoni
2013-05-15  8:11           ` Sascha Hauer
2013-05-15  8:19             ` Thomas Petazzoni
2013-05-12 13:09 ` [PATCH 4/5] arm: add basic support for SolidRun CuBox Sebastian Hesselbarth
2013-05-12 20:28   ` [PATCH v2 " Sebastian Hesselbarth
2013-05-12 13:09 ` [PATCH 5/5] arm: mach-mvebu: rename Armada 370/XP core code Sebastian Hesselbarth
2013-05-12 16:50   ` Thomas Petazzoni
2013-05-12 16:53     ` Sebastian Hesselbarth
2013-05-12 20:29   ` [PATCH v2 " Sebastian Hesselbarth

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=51910349.5040906@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=thomas.petazzoni@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