public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: u-boot@lists.denx.de
Subject: [PATCH] sunxi: board: Splitting CHIP defconfig for nand.
Date: Mon, 22 Feb 2021 10:44:17 +0100	[thread overview]
Message-ID: <20210222094417.guka2ebrixrhizer@gilmour> (raw)
In-Reply-To: <a323809d-1f12-a882-a8e0-58f412672d11@arm.com>

On Fri, Feb 19, 2021 at 06:00:13PM +0000, Andr? Przywara wrote:
> On 24/01/2021 16:19, Alexandre GRIVEAUX wrote:
> 
> Hi Alexandre,
> 
> (CCing: Kory, plus using Maxime's and Boris' newer emails)
> 
> > This patch split CHIP defconfig to add nand 4G and 8G support.
> > 
> > Some CONFIG was put at the end of defconfig to ease comparison between:
> > - CHIP Pro
> > - CHIP with Toshiba 4G
> > - CHIP with Hynix 8G
> > 
> > Witch are essentialy the same board with differents nand and memory.
> > 
> > Values was taken from now defunct compagny script "chip-update-firmware.sh"
> 
> Mmh, I am puzzled how this is supposed to work? I thought that the NAND
> in the non-Pro version was not supported (MLC?). So booting via USB was
> the only option?
> Has this changed?
> 
> Can someone confirm that this works?

The CHIP-Pro is indeed different, it's using a different SoC and NAND
(SLC) chip.

All the variants of the CHIP use an MLC NAND that isn't supported at all
by U-Boot.

I would discourage you from merging any MLC NAND related patch until
some form of MLC support is merged into U-Boot.

Maxime
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210222/06156843/attachment.sig>

      reply	other threads:[~2021-02-22  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 16:19 [PATCH] sunxi: board: Splitting CHIP defconfig for nand Alexandre GRIVEAUX
2021-02-19 18:00 ` André Przywara
2021-02-22  9:44   ` Maxime Ripard [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=20210222094417.guka2ebrixrhizer@gilmour \
    --to=maxime@cerno.tech \
    --cc=u-boot@lists.denx.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