public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: at91: gardena-smart-gateway-at91sam: Enable CONFIG_SYS_NAND_USE_FLASH_BBT
Date: Fri, 13 Sep 2019 15:15:46 +0200	[thread overview]
Message-ID: <6835cf4f-2bdd-e0ac-ddbc-882adc7bd346@denx.de> (raw)
In-Reply-To: <3334347.rv6oaGkvK3@ada>

Hi Alex,

On 13.09.19 15:09, Alexander Dahl wrote:
> Am Dienstag, 27. August 2019, 08:14:50 CEST schrieb Stefan Roese:
>> This patch enables the BBT in NAND on the AT91SAM based GARDENA smart
>> Gateway. This is especially important, since the Linux driver also
>> enables this option and uses the BBT table pages. Without setting this
>> option, U-Boot will try to re-use these pages again (e.g. UBI).
> 
> Does the Linux kernel driver use those unconditionally or is that a kernel
> config option? Which one? (Search in 5.2 kernel config for BBT is
> inconclusive.)

Linux uses the DT property "nand-on-flash-bbt" for this decision.
But please be aware - this is only for raw NAND and not SPI NAND
(IIRC).

And yes, we should definitely move to this DT property instead of
the Kconfig symbol in U-Boot as well. To automatically match the
configuration of such boards in U-Boot and Linux. But such a change
it too intrusive at this time of release cycle.

Thanks,
Stefan

      reply	other threads:[~2019-09-13 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  6:14 [U-Boot] [PATCH] arm: at91: gardena-smart-gateway-at91sam: Enable CONFIG_SYS_NAND_USE_FLASH_BBT Stefan Roese
2019-08-27  7:54 ` Eugen.Hristev at microchip.com
2019-09-11 13:13   ` Stefan Roese
2019-09-12  6:07     ` Eugen.Hristev at microchip.com
2019-09-12  9:00       ` Stefan Roese
2019-09-13 13:09 ` Alexander Dahl
2019-09-13 13:15   ` Stefan Roese [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=6835cf4f-2bdd-e0ac-ddbc-882adc7bd346@denx.de \
    --to=sr@denx.de \
    --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