headers
Alice Hennessy | 1 Sep 2000 03:05

Re: MTD support for 8x16 devices

David Woodhouse wrote:

> ahennessy <at> mvista.com said:
> >  Has any of this already been checked in recently?  And what is the
> > procedure?
>
> Stéphane already pointed you at the latest CVS. If you want write access,
> let me have a SSH public key and a sample of your work :)

Ok, I will do that.  I also just found out  that I need to subscribe to the
mtd-cvs list to follow what is being checked in?

>
>
> Can you confirm the mapping of the flash chips - you've got two interleaved
> 16-bit devices ('2_by_16') but you can only actually access them a byte at
> a time? What is the CPU? What happens if you _do_ try to read a whole word
> instead of only a byte?

One product has two interleaved 16 devices and is recognized as such by
cfi_probe_new_chip() and can be read as a whole word.

The other product has a single strata chip (8x16 variety) set in byte mode so
the bus width is 1.  The cfi ident info is requested at address 0xaa and read
starting at 0x20 so this is new code that I've added.   I'll  merge my code to
make use of the new define CFI_DEVICETYPE_X8 which I'm assuming was added for
this purpose?

The CPU is  PPC405GP.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ciro Cattuto | 1 Sep 2000 01:10
Picon

Re: GRUB on DOC: 2Mb issues

On Thu, Aug 31, 2000 at 05:20:48PM +0100, David Woodhouse wrote:

> I just committed it - it's working on 512-byte devices. I see no reason why 
> it shouldn't work on 256-byte devices if I copied Ciro's code correctly.

I tried it after your last commit and it works fine on my 2 Mb DOC.
I only needed to fix makecsum.c (reset checksum to zero - committed).

Ciro

--

-- 
Ciro Cattuto, Open Source Developer, Linuxcare Italia SpA
Tel. +39.338.3002140  Fax +39.049.8036484 
ciro <at> linuxcare.com    http://www.linuxcare.com/
ciro <at> prosa.it         http://www.prosa.it/
Linuxcare. Support for the revolution.

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 0 comments |
headers
Volker Sonn | 1 Sep 2000 10:18
Picon

Connot calculate an NFTL geometry to match size 0x7cf0

Hi,

sorry, I'm no kernel hacker. I'think my problem was on the list some time ago, but i only understand 5% of the
traffic here. 
Any hints to get my DOC 2000 16MB working ?

Lass die Sonne rein....
Permalink | Reply | 0 comments |
headers
Volker Sonn | 1 Sep 2000 10:28
Picon

Connot calculate an NFTL geometry to match size 0x7cf0

Hi,

sorry, I'm no kernel hacker. I'think my problem was on the list some time ago, but i only understand 5% of the
traffic here. 
Any hints to get my DOC 2000 16MB working ?

Lass die Sonne rein....

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 0 comments |
headers
David Vrabel | 1 Sep 2000 11:14
Picon

Re; MTD support for 8x16 devices
Picon
From: David Vrabel <dvrabel <at> arcom.co.uk>
Subject: Re: MTD support for 8x16 devices
Date: 2000-09-01 08:24:35 GMT
Alice Hennessy wrote:

> The other product has a single strata chip (8x16 variety) set in byte mode so
> the bus width is 1.  The cfi ident info is requested at address 0xaa and read
> starting at 0x20 so this is new code that I've added.   I'll  merge my code to
> make use of the new define CFI_DEVICETYPE_X8 which I'm assuming was added for
> this purpose?

I have some Intel StrataFlash 28F640 which are 16x devices in 8x mode. 
It got it to work by setting the bus width to 2 (not 1) and fudging the
"next chip" detection to look in the right place (ie pretend the bus
width was 1).  This made a single chip look like two interleaved chips
but of course the chip size with the entire chip (not half) hence the
fudging.

I wonder is it might be a good idea to have something in struct map_info
which says that the devices are "interleaved internally"...?

While you're poking about in cfi_cmdset_0001.c you'll possibly need to
change the code which selects the appropriate access routines (it
(Continue reading)

Permalink | Reply | 0 comments |
headers
mark.langsdorf | 1 Sep 2000 16:06
Picon
Favicon

Booting from CFI chips

Assuming I can get my BIOS to treat my flash array as a 
bootable device, how do I set up a flashable image so that
it will boot?  Do I use LILO, doc_loadbios, or some other
set of programs?  Nothing in the util or html directory
seems to address this issue directly.

Mark Langsdorf
Advanced Micro Devices, Inc             Tel: 512.602.3756
5204 E. Ben White Blvd. M/S 590         Fax: 512.602.5051
Austin, TX 78741                        mark.langsdorf <at> amd.com

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 0 comments |
headers
David Woodhouse | 4 Sep 2000 15:16
Favicon

Re: MTD support for 8x16 devices


ahennessy <at> mvista.com said:
>  Ok, I will do that.  I also just found out  that I need to subscribe
> to the mtd-cvs list to follow what is being checked in? 

Yep. I did have that going to the main list at one point, but people 
apparently prefer to have it separated.

ahennessy <at> mvista.com said:
>  The other product has a single strata chip (8x16 variety) set in byte
> mode so the bus width is 1.  The cfi ident info is requested at
> address 0xaa and read starting at 0x20 so this is new code that I've
> added.   I'll  merge my code to make use of the new define
> CFI_DEVICETYPE_X8 which I'm assuming was added for this purpose?

Dunno. That was added after I last looked at the CFI probe code.

ahennessy <at> mvista.com said:
> Sooo,  I need to do the extra logic outside the driver level. ;) 

See (and probably rename) util/doc_loadbios

--
dwmw2

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 2 comments |
headers
Stuart Menefy | 4 Sep 2000 20:15

JEDEC support

Folks

I'm new to MTD, and unfortunately to get it running on my hardware I'm
going to need the JEDEC support. I see the code has atrophied a little,
so before I embark on trying to resurrect it, I was just wondering if
anyone else had done this work? Alternatively any hints on how best to
do it would be welcome.

Longer term, I also need to support Intel 28F016 (which is not JEDEC
or CFI compatible). Anybody else implemented support for these?

Many thanks

Stuart

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 1 comment |
headers
David Woodhouse | 5 Sep 2000 09:38
Favicon

Re: JEDEC support


Stuart.Menefy <at> st.com said:
>  I'm new to MTD, and unfortunately to get it running on my hardware
> I'm going to need the JEDEC support. I see the code has atrophied a
> little, so before I embark on trying to resurrect it, I was just
> wondering if anyone else had done this work? Alternatively any hints
> on how best to do it would be welcome.

It shouldn't be _too_ much out of date. It just needs you to make it take 
the 'bank_size' parameter as an argument to the probe function rather than 
storing it in the map_info structure.

>  Longer term, I also need to support Intel 28F016 (which is not JEDEC
> or CFI compatible). Anybody else implemented support for these? 

The (very) old doc1000 driver does it, I think. Can you probe for these 
chips?

--
dwmw2

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 0 comments |
headers
David Woodhouse | 5 Sep 2000 14:53
Favicon

Grub support in DiskOnChip.

Grub patches to support NFTL properly have just been contributed. 

See mtd/patches/grub* and send virtual beer to void <at> dr.com

--
dwmw2

To unsubscribe, send "unsubscribe mtd" to majordomo <at> infradead.org
Permalink | Reply | 4 comments |

Gmane