From: Steven Seeger <steven.seeger2@gmail.com>
To: u-boot@lists.denx.de
Subject: nand max chips
Date: Fri, 1 Oct 2021 10:35:33 -0400 [thread overview]
Message-ID: <CALcG7R+F1SFerkfi_nDeHHbOGY_1483H20ojG-3Kb52n5bkrmQ@mail.gmail.com> (raw)
U-boot has an interesting mix of CONFIG_SYS_MAX_NAND_CHIPS and
CONFIG_SYS_NAND_MAX_CHIPS.
README.nand actually uses both. CONFIG_SYS_NAND_MAX_CHIPS is documented,
but CONFIG_SYS_MAX_NAND_CHIPS is used as the example with nand_scan_ident().
There are some drivers that use the wrong one.
I would be happy to submit a patch if someone on the list would like to
inform me of which one that they should all be. Or, perhaps I am missing
something and they are two separate things.
Thanks,
Steven
reply other threads:[~2021-10-01 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CALcG7R+F1SFerkfi_nDeHHbOGY_1483H20ojG-3Kb52n5bkrmQ@mail.gmail.com \
--to=steven.seeger2@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).