mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Stefan Riedmueller <s.riedmueller@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/8] ARM: phytec-som-imx6: Add low cost variant for imx6dl phycore
Date: Thu, 11 Jul 2019 08:43:07 +0200	[thread overview]
Message-ID: <20190711064307.lbnenmog7qwbzu3a@pengutronix.de> (raw)
In-Reply-To: <1562757455-445159-1-git-send-email-s.riedmueller@phytec.de>

Hi Stefan,

On Wed, Jul 10, 2019 at 01:17:28PM +0200, Stefan Riedmueller wrote:
>  
>  PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_nand_256mb, imx6dl_phytec_phycore_som_nand, SZ_256M, true);
> +PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_lc_nand_256mb, imx6dl_phytec_phycore_som_lc_nand, SZ_256M, true);
>  PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_nand_1gib, imx6dl_phytec_phycore_som_nand, SZ_1G, true);
>  PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_emmc_1gib, imx6dl_phytec_phycore_som_emmc, SZ_1G, true);
> +PHYTEC_ENTRY(start_phytec_phycore_imx6dl_som_lc_emmc_1gib, imx6dl_phytec_phycore_som_lc_emmc, SZ_1G, true);
>  PHYTEC_ENTRY(start_phytec_phycore_imx6q_som_nand_1gib, imx6q_phytec_phycore_som_nand, SZ_1G, true);
>  PHYTEC_ENTRY(start_phytec_phycore_imx6qp_som_nand_1gib, imx6qp_phytec_phycore_som_nand, SZ_1G, true);
>  PHYTEC_ENTRY(start_phytec_phycore_imx6q_som_emmc_1gib, imx6q_phytec_phycore_som_emmc, SZ_1G, true);

I am a bit worried that with this series the combinatoric explosion of
the Phytec boards goes into another round. For some reason the lowcost
NAND version has 256MiB SDRAM and the eMMC version has 1GiB SDRAM. I
guess different combinations are not supported because you haven't
produced them yet, but they might appear sooner or later. Even now it is
really hard to pick a board from the shelf and find the right barebox
binary for it. Do you have any ideas/plans to improve this?

It seems all boards have EEPROMs. Wouldn't it be an option to store some
information there?

Another point is: Do we really need image variants for eMMC and NAND? In
the end the drivers detect automatically if one or the other is equipped
on the board.

Let's go crazy now. How about a QR code on the board with a link that
describes which hardware (SoC variant, amount of memory, NAND/eMMC) I
am looking at?

Anyway, applied, thanks. It would just be nice to see some improvements
here.

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

  parent reply	other threads:[~2019-07-11  6:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 11:17 Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 2/8] ARM: dts: imx6qdl: phycore: Add state framework Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 3/8] ARM: dts: imx6ul: phycore: Add eeprom label Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 4/8] ARM: dts: imx6ul: phycore: Add state framework Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 5/8] ARM: imx6ul: phycore: Prepare for eMMC module Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 6/8] ARM: phytec-som-imx: imx6ul: Add eMMC support Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 7/8] ARM: dts: imx6ul: phycore: Add support for eMMC Stefan Riedmueller
2019-07-10 11:17 ` [PATCH v2 8/8] ARM: dts: imx6ul: phycore: Add phyCORE-i.MX 6ULL with eMMC Stefan Riedmueller
2019-07-11  6:43 ` Sascha Hauer [this message]
2019-07-11 10:07   ` [PATCH v2 1/8] ARM: phytec-som-imx6: Add low cost variant for imx6dl phycore Stefan Riedmüller
2019-07-12  6:16     ` 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=20190711064307.lbnenmog7qwbzu3a@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.riedmueller@phytec.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