All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: does beaglebone black device tree need to specify amount of eMMC flash?
Date: Sat, 5 Jul 2014 06:47:36 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407050643590.10085@localhost> (raw)


  (aside: i'm digging into device trees in barebox and will certainly
have a number of questions shortly so i can write some tutorials for
an upcoming class, but i'll start simple.)

  i'm particularly interested in configuring and building barebox for
my beaglebone black (henceforth "BBB"), and i can see all of the .dts*
support files under arch/arm/dts/, but a simple question -- the *new*
BBB has upgraded from 2G of eMMC to 4G eMMC, but i don't see that
mentioned anywhere in those .dts files. does that property need to be
mentioned, or is that simply autodetected by the kernel at boot time?

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-05 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 10:47 Robert P. J. Day [this message]
2014-07-07  6:53 ` does beaglebone black device tree need to specify amount of eMMC flash? Sascha Hauer
2014-07-07  7:06   ` Alexander Aring
2014-07-07  8:53     ` Lucas Stach
2014-07-07  9:37       ` Alexander Aring
2014-07-07 21:05     ` Holger Schurig

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.1407050643590.10085@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    /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.