From: Thomas Gleixner <tglx@linutronix.de>
To: Nicolas Pouillon <nipo@ssji.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Patch !
Date: Mon, 04 Oct 2004 19:59:11 +0200 [thread overview]
Message-ID: <1096912750.21297.433.camel@thomas> (raw)
In-Reply-To: <20041004183827.7bcc5071.nipo@ssji.net>
On Mon, 2004-10-04 at 18:38, Nicolas Pouillon wrote:
> > Is the chip configured for 16-bit interface mode ?
>
> PXA boots of it and its BOOT_SEL is configured to "Asynchronous 16bit
> ROM", elsewhere, in mem controller, it is configured as "16bit fast
> flash or rom, non burst read". so I assume it is.
>
> > If yes, there are more tweaks neccecary.
>
> I can see some NAND_BUSWIDTH_16 options, but how can this be enabled at
> probe time ?
The configuration register reflects the state of the IF_CFG pin.
The NAND_BUSWIDTH_16 option must be set before calling nand_scan, but
AFAICS you must also add 16bit aware read/write... functions for
doc2001plus.
tglx
next prev parent reply other threads:[~2004-10-04 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 13:46 Issues with a Doc Milplus Nicolas Pouillon
2004-10-01 13:57 ` David Woodhouse
2004-10-01 14:27 ` Nicolas Pouillon
2004-10-02 13:55 ` Patch ! Nicolas Pouillon
2004-10-02 20:42 ` Thomas Gleixner
2004-10-03 1:11 ` Nicolas Pouillon
[not found] ` <20041003030653.2e0452a7.nipo@ssji.net>
[not found] ` <1096768161.21297.129.camel@thomas>
2004-10-03 20:18 ` Nicolas Pouillon
2004-10-04 8:05 ` Thomas Gleixner
2004-10-04 16:38 ` Nicolas Pouillon
2004-10-04 17:59 ` Thomas Gleixner [this message]
2004-10-04 20:47 ` Nicolas Pouillon
2004-10-04 21:04 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2007-04-28 21:47 PATCH: Mark Lord
2004-11-21 23:58 Patch, Andreas Fenkart
2004-11-22 6:37 ` Patch, Jaroslav Kysela
2000-07-12 16:24 PATCH: Juan J. Quintela
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=1096912750.21297.433.camel@thomas \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=nipo@ssji.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.