From: Vipin KUMAR <vipin.kumar@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 8/16 bit support for NAND at runtime
Date: Fri, 05 Mar 2010 10:12:48 +0530 [thread overview]
Message-ID: <4B908BC8.9030306@st.com> (raw)
In-Reply-To: <20100304122805.3F29D28BBC@gemini.denx.de>
On 3/4/2010 5:58 PM, Wolfgang Denk wrote:
> Dear Vipin KUMAR,
>
> In message <4B8F8C3F.6050703@st.com> you wrote:
>>
>> This query is wrt NAND 8/16 bit device support at runtime. Currently,
>> the u-boot code can support only one of these at a time.
>
> Yes, indeed. I have yet to see a piece of hardware which implements
> both 8 and 16 bit interfaces on a single board. Hardware designers
> often have funny ideas, but this seems to be too weird even for them
> ;-)
>
>> Although it matches the buswidth selected through chip->options and the
>> the buswidth of device id it reads and returns an error if they don't
>> match, probably a better way can be to reinitialize NAND controller
>> based on 16 bit device and re-read the device id.
>
> Why would that be needed? Do you really expect to see both types of
> interfaces on the same piece of hardware?
>
Yes, that's precisely the case with Spear SoC. It has an FSMC controller
embedded in it. FSMC can support 8 as well as 16 bit devices(off-course
with different initializations) for different banks
>
> Otherwise you just have misconfigured your board, and fixing the
> configuration should all that is needed to make the code work. Or am
> I missing something?
>
I could make the code work with both 8 as well as 16 bit devices. The
only thing is that I have to make a few changes and rebuild the uboot
for a particular interface
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2010-03-05 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 10:32 [U-Boot] 8/16 bit support for NAND at runtime Vipin KUMAR
2010-03-04 12:28 ` Wolfgang Denk
2010-03-05 4:42 ` Vipin KUMAR [this message]
2010-03-21 16:50 ` Wolfgang Denk
2010-03-23 5:42 ` Swarthout Edward L-SWARTHOU
2010-03-23 5:54 ` Vipin KUMAR
2010-03-23 16:15 ` Scott Wood
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=4B908BC8.9030306@st.com \
--to=vipin.kumar@st.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