[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Intel Flash



Hi,

I believe that the problem you are seeing is
that the device is using cmdset 0x0003, which
is close to cmdset 0x0001. Cmdset 0x0001 is 
supported by mtd so a quick and not so dirty
fix is to add the following two lines in 
cfi_probe.c, function cfi_cfi_probe(),

if(cfi.cfiq->P_ID == 3)
	cfi.fgiq->P_ID = 1;

after the two lines (around line 343)

/* Do any necessary byteswapping */
cfi.cfiq->P_ID = le16_to_cpu(cfi.cfiq->P_ID);

Hope this helps,

K.D.


-----Original Message-----
From:	Vipin Malik
Sent:	Wed 4/18/2001 6:57 PM
To:	Marcio Koch
Cc:	jffs-dev; mtd
Subject:	Re: Intel Flash

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@xxxxxxx.br
> PUCRS/ELinux
>
> To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
> the body of a message to majordomo@xxxxxxx.com



To unsubscribe, send "unsubscribe mtd" to majordomo@xxxxxxx.org



winmail.dat