From: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
To: linux-mtd@lists.infradead.org, linuxppc-embedded@lists.linuxppc.org
Subject: MTD/JFFS2 on Intel 28F160F3
Date: Thu, 08 Aug 2002 16:43:30 -0700 [thread overview]
Message-ID: <3D530222.7040303@redswitch.com> (raw)
Hi *,
I'm trying to enable MTD and JFFS2 on an Intel 28F160F3 chip but have
some problems.
The basic problem is what the physical start address of flash mapping
is? While on PPCBoot, I got flash information using command 'flinfo'.
The start address is FFE00000. Is this address the one used to configure
CFI flash device in physical memeory map? I tried using this address but
'physmap' couldn't find flash device.
-----------------clip-----------------------------------------
root@ib8sw:~# modprobe -a physmap
physmap flash device: 100000 at ffe00000
CFI: Found no Physically mapped flash device at location zero
-----------------clip-----------------------------------------
-----------------clip-----------------------------------------
=> flinfo
Bank # 1: INTEL 28F160F3 (16 Mbit, top boot sector)
Size: 2 MB in 39 Sectors
Sector Start Addresses:
FFE00000 FFE10000 FFE20000 FFE30000 FFE40000
FFE50000 FFE60000 FFE70000 FFE80000 FFE90000
FFEA0000 FFEB0000 FFEC0000 FFED0000 FFEE0000
FFEF0000 FFF00000 (RO) FFF10000 (RO) FFF20000 (RO) FFF30000 (RO)
FFF40000 FFF50000 FFF60000 FFF70000 FFF80000
FFF90000 FFFA0000 FFFB0000 FFFC0000 FFFD0000
FFFE0000 FFFF0000 FFFF2000 FFFF4000 FFFF6000
FFFF8000 FFFFA000 FFFFC000 FFFFE000
=>
-----------------clip-----------------------------------------
I haven't dived into the routine 'do_cfi_probe()' yet since I'm not sure
if the start address I specified is correct. Any help is greatly
appreciated.
- Shawn.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-08-08 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 23:43 Xiaogeng (Shawn) Jin [this message]
2002-08-09 15:01 ` MTD/JFFS2 on Intel 28F160F3 Rabeeh Khoury
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=3D530222.7040303@redswitch.com \
--to=xjin@redswitch.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).