mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 1/2] kirkwood: add support for booting via oftree probe
Date: Mon, 23 Jun 2014 08:51:05 +0200	[thread overview]
Message-ID: <20140623065102.GB9990@omega> (raw)
In-Reply-To: <53A74E95.40403@gmail.com>

On Sun, Jun 22, 2014 at 11:45:57PM +0200, Sebastian Hesselbarth wrote:
> On 06/22/2014 10:34 PM, Alexander Aring wrote:
> > This patch initialize memory only if we boot a kirkwood arch with
> > device-tree probing. Otherwise some devices like timer or uart will
> > be probed twice.
> > 
> > Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> > ---
> > I don't know if this is right. The guruplug is the other kirkwood platform
> > but don't have devictree support.
> 
> Alexander,
> 
> I'd rather remove non-DT booting for kirkwood completely. I have patches
> ready somewhere. Let me sort them out tomorrow.
> 

Ok, I'll be waiting. Thanks.

- Alex

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

      reply	other threads:[~2014-06-23  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 20:34 Alexander Aring
2014-06-22 20:34 ` [RFC 2/2] dns325: initial support for D-Link DNS-325 Alexander Aring
2014-06-22 21:50   ` Sebastian Hesselbarth
2014-06-23  6:48     ` Alexander Aring
2014-06-26  4:27     ` Alexander Aring
2014-06-26  6:53       ` Sebastian Hesselbarth
2014-06-26  9:14         ` Alexander Aring
2014-06-24 11:54   ` Sebastian Hesselbarth
2014-06-25  6:57     ` Sascha Hauer
2014-06-22 21:45 ` [RFC 1/2] kirkwood: add support for booting via oftree probe Sebastian Hesselbarth
2014-06-23  6:51   ` Alexander Aring [this message]

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=20140623065102.GB9990@omega \
    --to=alex.aring@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=sebastian.hesselbarth@gmail.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