From: David Woodhouse <dwmw2@infradead.org>
To: Rick van Rein <rick@groengemak.nl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Flash I/O not enabled in MSR_DIVIL_BALL_OPTS
Date: Wed, 02 Dec 2009 18:11:10 +0000 [thread overview]
Message-ID: <1259777470.3744.484.camel@macbook.infradead.org> (raw)
In-Reply-To: <20091130084004.GE23351@phantom.vanrein.org>
On Mon, 2009-11-30 at 08:40 +0000, Rick van Rein wrote:
> Hello,
>
> Thanks a lot for the detailed FAQ + documentation on the Linux MTD
> subsystem. It brought me from a novice on the Linux implementation
> to someone who feels in control.
>
> I am working to get a modest Linux distro going on what originally was
> a 7 Watt thin client running Win XPe. Since IDE is amazingly slow (it
> consumes 80% CPU time in IRQ handlers) I wanted to try direct access
> through JFFS2 to the NAND chips.
>
> Processor: Geode GX
> Chipset: Geode CS5535
> NAND flash: Toshiba TC58DVM92A1FT00 (512 MB x8, a 3 to 5 of them)
> Controller: If there's a CompactFlash ctlr it is concealed from me
> Linux kernel: 2.6.31.6 without IDE but with CS553x NAND and JFFS2
>
> When I boot this setup (over PXE), it reports:
>
> CS553x NAND controller: Flash I/O not enabled in MSR_DIVIL_BALL_OPTS
>
> Tracing this back in the code, this refers to an either-IDE-or-flash
> setting in the MSR that was either setup by RESET or the BIOS. The
> hardware works like that, the pins for IDE and NAND flash are multiplexed.
> I am not sure in XPe would see this, so if this flag is meaningful...?
>
> What surprised me was that the kernel contained no ways of setting this
> value to inform the NAND driver that it can play freely; is this because
> the hardware is wired purely for IDE operation? Or does the slow IDE
> responsiveness indicate that it is in fact flash, but not properly setup?
>
> Is there a proper way of setting this flag without patching the kernel?
If you have the NAND hardware connected, then surely your firmware ought
to be setting the MSRs appropriately?
See http://david.woodhou.se/olpc-enable-nand.c for an example of how to
make it work if your firmware doesn't, though.
Of course, we didn't need that hack any more as soon as we switched to
OpenFirmware.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-12-02 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 8:40 Flash I/O not enabled in MSR_DIVIL_BALL_OPTS Rick van Rein
2009-12-02 18:11 ` David Woodhouse [this message]
2009-12-05 17:47 ` Rick van Rein
2009-12-05 21:05 ` David Woodhouse
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=1259777470.3744.484.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rick@groengemak.nl \
/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