All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: device trees, dtc and beaglebone black
Date: Mon, 7 Jul 2014 06:16:38 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407070615570.3134@localhost> (raw)
In-Reply-To: <20140707073623.GJ23235@pengutronix.de>

On Mon, 7 Jul 2014, Sascha Hauer wrote:

> On Sat, Jul 05, 2014 at 10:45:25AM -0400, Robert P. J. Day wrote:
> >
> >   next, with the BBB, i realize there are two configs and builds that
> > must be done:
> >
> >  $ make omap3530_beagle_xload_defconfig
> >  $ make omap3530_beagle_defconfig
>
> Nope. These configs are for the beaglebo*ard*, not the beaglebone. Maybe
> we should rename the config files. At the time they were introduced
> there was no beaglebone.
>
> The configs you need for the beaglebone are:
>
> am335x_mlo_defconfig
> am335x_defconfig

  yes, i should have known that ... i'll dig into the rest of your
note later.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

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

      reply	other threads:[~2014-07-07 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 14:45 device trees, dtc and beaglebone black Robert P. J. Day
2014-07-07  7:36 ` Sascha Hauer
2014-07-07 10:16   ` Robert P. J. Day [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=alpine.LFD.2.11.1407070615570.3134@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    --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 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.