mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Stefan Christ <s.christ@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/10] Rework towards phytec-som-imx6 and new variants
Date: Mon, 9 Nov 2015 13:09:20 +0100	[thread overview]
Message-ID: <20151109120920.GG2347@lws-christ> (raw)
In-Reply-To: <20151109064924.GU8526@pengutronix.de>

Hi Sascha,

> > the patchstack first refactors the phyCARD-i.MX6 and phyFLEX-i.MX6 to a common
> > phytec-som-imx6. Then some phyFLEX-i.MX6 variants and the new phyCORE-i.MX6 are
> > added plus some environment updates and one image rename patch.
> >
>
> The Phytec i.MX6 boards all have an EEPROM, right?

No, it's possible to get a board without an EEPROM and we have some of them
lying around here.

> Does it have the memory setup encoded somewhere?

So no, the memory is not encoded anywhere on the module.

> It gets increasingly hard picking the right image for the Phytec boards.

Yeah. We are discussing some solutions for that like GPIOs, EEPROM or EFuses,
but nothing has emerged from that and they are only viable for new products.

One simple thing would be to encode the memory configuration into the barebox
image filename. So a user can look at the module, count the memory chips and
banks, and pick the correct image for that.

Mit freundlichen Grüßen / Kind regards,
	Stefan Christ

On Mon, Nov 09, 2015 at 07:49:24AM +0100, Sascha Hauer wrote:
> Hi Stefan,
> 
> On Fri, Nov 06, 2015 at 11:21:48AM +0100, Stefan Christ wrote:
> > Hi,
> > 
> > the patchstack first refactors the phyCARD-i.MX6 and phyFLEX-i.MX6 to a common
> > phytec-som-imx6. Then some phyFLEX-i.MX6 variants and the new phyCORE-i.MX6 are
> > added plus some environment updates and one image rename patch.
> >
> 
> The Phytec i.MX6 boards all have an EEPROM, right? Does it have the
> memory setup encoded somewhere? It gets increasingly hard picking the
> right image for the Phytec boards.
> 
> Sascha
> 
> -- 
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2015-11-09 12:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 10:21 Stefan Christ
2015-11-06 10:21 ` [PATCH 01/10] ARM: imx6: phycard: use numeric suffix in device tree Stefan Christ
2015-11-06 10:21 ` [PATCH 02/10] boards: Add phytec-som-imx6 Stefan Christ
2015-11-06 10:21 ` [PATCH 03/10] ARM: phytec-som-imx6: set loadaddr to start of DDR memory Stefan Christ
2015-11-06 10:21 ` [PATCH 04/10] ARM: phytec-som-imx6: update environment Stefan Christ
2015-11-06 10:21 ` [PATCH 05/10] ARM: pfla02: append suffix 1bank Stefan Christ
2015-11-06 10:21 ` [PATCH 06/10] ARM: imx6q: pfla02: Add support for 512MiB RAM on one bank Stefan Christ
2015-11-06 10:21 ` [PATCH 07/10] ARM: imx6dl: pfla02: Add support for 128MB and 256MB RAM Stefan Christ
2015-11-06 10:21 ` [PATCH 08/10] ARM: imx6q: pfla02: add phyFLEX-i.MX6 DualLite 1GiB on one bank Stefan Christ
2015-11-06 10:21 ` [PATCH 09/10] ARM: imx6q: Add support for Phytec phyCORE-i.MX6 SOM Stefan Christ
2015-11-06 10:21 ` [PATCH 10/10] ARM: imx6dl: " Stefan Christ
2015-11-09  6:45   ` Sascha Hauer
2015-11-09  8:50     ` Stefan Christ
2015-11-09  6:49 ` [PATCH 00/10] Rework towards phytec-som-imx6 and new variants Sascha Hauer
2015-11-09 12:09   ` Stefan Christ [this message]
2015-11-10  8:36     ` Sascha Hauer

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=20151109120920.GG2347@lws-christ \
    --to=s.christ@phytec.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox