All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: does beaglebone black device tree need to specify amount of eMMC flash?
Date: Mon, 7 Jul 2014 09:06:12 +0200	[thread overview]
Message-ID: <20140707070610.GA11833@omega> (raw)
In-Reply-To: <20140707065345.GI23235@pengutronix.de>

On Mon, Jul 07, 2014 at 08:53:45AM +0200, Sascha Hauer wrote:
> On Sat, Jul 05, 2014 at 06:47:36AM -0400, Robert P. J. Day wrote:
> > 
> >   (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?
> 
> eMMC size is autodetected by barebox and the kernel. In the end it's
> just a MMC/SD card.
> 

btw.: that's why eMMC is evil.

Raw-Flash:

Disadvantage:
 - you can't replace it.

Advantage:
 - no mcu in the middle, access the raw Flash.


- MMC/SD:

Disadvantage:
 - mcu in the middle, abstract block device. OS doesn't know about this.

Advantage:
 - you can replace it.


Combines these Disadvantage and Advantage you will get:

Disadvantage:
 - mcu in the middle, abstract block device. OS doesn't know about this.
 - you can't replace it.

Advantage:
 - maybe a little bit cheaper...
 - maybe avoid some bad connections (never expired by using sd cards)

For the marketing you can say if your eMMC is broken, then buy a new
complete board. This kind of marketing is very bad. :-(

- Alex

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

  reply	other threads:[~2014-07-07  7:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 10:47 does beaglebone black device tree need to specify amount of eMMC flash? Robert P. J. Day
2014-07-07  6:53 ` Sascha Hauer
2014-07-07  7:06   ` Alexander Aring [this message]
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=20140707070610.GA11833@omega \
    --to=alex.aring@gmail.com \
    --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.