U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8] kirkwood: add NAS62x0 board support
Date: Sat, 2 Jun 2012 10:31:46 +0200	[thread overview]
Message-ID: <201206021031.47297.marex@denx.de> (raw)
In-Reply-To: <20120602071348.GA6626@w500.lan>

Dear Luka Perkov,

> Hi Michael,
> 
> On Fri, Jun 01, 2012 at 11:03:16PM +0200, Michael Walle wrote:
> > > +/*
> > > + * Machine type
> > > + */
> > > +#define CONFIG_MACH_TYPE	MACH_TYPE_NAS6210
> > 
> > btw i guess this will break in about half a year. because:
> >  - uboot follows mach-types.h from the kernel
> >  - the kernel will only keep mach-types for boards which are supported by
> >  the
> >  
> >    kernel AND using the old-style machine init, that is no boards with no
> >    device tree support for booting.
> >  
> >  - no old style machine setups are accepted for kirkwood platforms
> >  anymore.
> > 
> > that means at some point of time in the future MACH_TYPE_NAS6210 wont be
> > defined anymore ;)
> > 
> > just wanted to letting you know.
> 
> I'm aware of that :)
> 
> This board is already accepted upstream, for more info look here:
> 
> commit f6a26ae7699416d86bea8cb68ce413571e9cab3c
> Merge: cdd3a35 48a5765
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Tue May 22 13:32:53 2012 -0700
> 
> Once 3.5 is out we'll patch uboot. Simon is the one that pushed support
> for this board upstream using device tree. Thanks Simon.

Why would you wait for 3.5 ? You can use -next .

> Luka

Best regards,
Marek Vasut

  reply	other threads:[~2012-06-02  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 19:22 [U-Boot] [PATCH v8] kirkwood: add NAS62x0 board support Luka Perkov
2012-04-20  5:56 ` Prafulla Wadaskar
2012-06-01 21:03 ` Michael Walle
2012-06-02  7:13   ` Luka Perkov
2012-06-02  8:31     ` Marek Vasut [this message]
2012-06-02  9:40       ` Luka Perkov

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=201206021031.47297.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.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