From: Vipin Malik <vipin.malik@daniel.com>
To: Marcio Koch <koch@inf.pucrs.br>
Cc: jffs-dev <jffs-dev@axis.com>, mtd <mtd@infradead.org>
Subject: Re: Intel Flash
Date: Wed, 18 Apr 2001 13:57:16 -0500 [thread overview]
Message-ID: <3ADDE38C.249F0A11@daniel.com> (raw)
In-Reply-To: 20010418155001.A6711@sirrah.inf.pucrs.br
Marcio Koch wrote:
> TE28F320
^^^^^^^^^^^^^ This is the part #. You can ignore the rest of the stuff.
Go to www.intel.com and download the datasheet on this part and see if it is a
CFI compatable NOR flash or not.
If not CFI, but is NOR, then try to use the JDEC module, rather than the CFI
module. If Not NOR (i.e. if NAND)
then I don't know.
Hope this helps.
Vipin
P.S. This is really a MTD issue and you will probably have more luck posting
to that list. I've CC to that list if you
need the email.
>
> B3BA110
> U9490626A
> (c)1998
>
> Does anybody know if this flash is supported by linux ? If so what kernel
> and mtd code should I use ?
>
> For MPC8xx.
>
> I'm using kernel 2.4.3-pre4 and it fails when I try to load the physmap
> module.
>
> Here is what I did and the error I got:
>
> sh-2.03# modprobe -a mtdchar mtdblock cfi_cmdset_0001 map_rom cfi_probe
> sh-2.03# lsmod
> Module Size Used by
> cfi_probe 7920 0 (unused)
> map_rom 1072 0 (unused)
> cfi_cmdset_0001 8000 0 (unused)
> mtdblock 6528 0 (unused)
> mtdchar 5408 0 (unused)
> mtdcore 2976 2 [mtdblock mtdchar]
> sh-2.03# modprobe -a physmap
> physmap flash device: 3fffff at fe000000
> Physically mapped flash: Found no CFI device at location zero
> /lib/modules/2.4.3-pre4/kernel/drivers/mtd/physmap.o: init_module: Device
> not configured
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters
> /lib/modules/2.4.3-pre4/kernel/drivers/mtd/physmap.o: insmod
> /lib/modules/2.4.3-pre4/kernel/drivers/mtd/physmap.o failed
> /lib/modules/2.4.3-pre4/kernel/drivers/mtd/physmap.o: insmod physmap failed
>
> Any help would be appreciated.
>
> Thanks,
>
> Marcio Koch
> koch@inf.pucrs.br
> PUCRS/ELinux
>
> To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
> the body of a message to majordomo@axis.com
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next parent reply other threads:[~2001-04-18 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010418154546.C6248@sirrah.inf.pucrs.br>
[not found] ` <20010418155001.A6711@sirrah.inf.pucrs.br>
2001-04-18 18:57 ` Vipin Malik [this message]
2006-12-20 13:19 Intel flash Darshak
2006-12-20 13:32 ` Josh Boyer
2006-12-20 13:36 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2001-04-18 20:32 Intel Flash Kári Davíðsson
2000-07-26 11:59 Intel flash chester
2000-07-27 1:15 ` Yong-iL Joh
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=3ADDE38C.249F0A11@daniel.com \
--to=vipin.malik@daniel.com \
--cc=jffs-dev@axis.com \
--cc=koch@inf.pucrs.br \
--cc=mtd@infradead.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