From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] TI: TNETV107X EVM initial support
Date: Sat, 03 Apr 2010 13:51:02 -0500 [thread overview]
Message-ID: <4BB78E16.80205@windriver.com> (raw)
In-Reply-To: <8FFAA0BFC4E5374B8F85F65FE1F2BFA58BABD00A@dlee02.ent.ti.com>
Chemparathy, Cyril wrote:
> Wolfgang,
>
> [...]
>>>> Is "davinci" correct here?
>>> Yes, this SOC has the exact same controller as on Davinci, and therefore
>>> the NAND driver is reused.
>> But you don't call this a "Davinci"-Board, or do you?
>
> "Davinci NAND" is a bit of a misnomer since this particular EMIF block is
> commonly used across multiple TI devices. Unfortunately, this misnomer
> (amongst others) carries forward into the kernel too. Consequently, if we
> use a different device name here, the mtdparts variable won't be usable as
> a kernel command-line argument.
>
> Regards
> Cyril.
Cyril,
This is a good reason, let us make sure it is propagated.
Please add this explanation as a comment in the config file.
Tom
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2010-04-03 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 20:16 [U-Boot] [PATCH 0/3] TI: tnetv107x patch series Cyril Chemparathy
2010-03-29 20:16 ` [U-Boot] [PATCH 1/3] ARM1176: Coexist with other ARM1176 platforms Cyril Chemparathy
2010-03-29 20:16 ` [U-Boot] [PATCH 2/3] ARM1176: TI: TNETV107X soc initial support Cyril Chemparathy
2010-03-29 20:16 ` [U-Boot] [PATCH 3/3] TI: TNETV107X EVM " Cyril Chemparathy
2010-03-30 20:54 ` Wolfgang Denk
2010-03-30 21:01 ` Chemparathy, Cyril
2010-03-30 21:35 ` Wolfgang Denk
2010-03-31 15:03 ` Chemparathy, Cyril
2010-04-03 18:51 ` Tom [this message]
2010-03-30 20:49 ` [U-Boot] [PATCH 2/3] ARM1176: TI: TNETV107X soc " Wolfgang Denk
2010-03-30 20:59 ` Chemparathy, Cyril
2010-03-30 21:34 ` Wolfgang Denk
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=4BB78E16.80205@windriver.com \
--to=tom.rix@windriver.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