headers
Eduardo Sabaj | 2 Jan 2004 18:59
Favicon

[Fwd: Re: [ECOS] JFFS2]

Dear sir,

I would be grateful if you could answer some of questions that are
indicated below ...
On top of that, could you please tell me what other file systems (and on
which media - flash, disk, etc) are supported by eCos?

Thanks for all,

Eduardo

-------- Original Message --------
Subject: Re: [ECOS] JFFS2
Date: 02 Jan 2004 09:17:31 -0700
From: Gary Thomas <gary <at> mlbassoc.com>
Organization: MLB Associates
To: Eduardo Sabaj <esabaj <at> hasar.com>
CC: ecos-discuss <at> sources.redhat.com
References: <3FF59306.6704AE5B <at> hasar.com>

On Fri, 2004-01-02 at 08:49, Eduardo Sabaj wrote:
> I am interested in building an embedded application using the eCos, but
> I have some questions about it.. I read that one of the file systems
> that is supported is JFFS2 but the question is, if it is a file system
> that runs only over a flash device (can I have a JFFS2 file system on
> DiskOnModule?)
> On the other hand, I wonder if  JFFS2 is well protected over power fails
> (I mean if the file system avoid losing information after the power
> fail) ?
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Vrabel | 2 Jan 2004 12:12

Re: Unable to access JFFS2 filesystem

thomaspang <at> shaw.ca wrote:
> With David's patches, I am able to access the JFFS2 file system.  Thanks.
> However, the following weird behaviors are observed:
 >
> [...]
 >
> - The write performance is kind of poor.  I have tried to copy
>   files of different sizes from CRAMFS to JFFS2, or from JFFS2
>   to another JFFS2 partition.  On average, the copying speed
>   is approx. 7.5 kbytes/sec.  It seems too slow.

Yes. If you're using the patches I produced write performance will be 
very poor.  It disables erase suspends if you're trying to write because 
they didn't work correctly.

Don't hold your breath waiting for me to fix it.  Performance 
improvements are way down my list of things to do.

David Vrabel
--

-- 
David Vrabel, Design Engineer

Arcom, Clifton Road           Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK         Web: http://www.arcom.com/

_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should
not be disclosed to any other party. Unauthorised recipients are requested to preserve this
confidentiality. Please advise the sender if the addressee is not resident at the receiving end.  Email to
and from Arcom is automatically monitored for operational and lawful business reasons.
(Continue reading)

Permalink | Reply | 501 comments |
headers
dkey | 3 Jan 2004 01:08
Picon

dbox2-flash.c

hi!

would be pleased if somebody can include the header asm/errno.h to
dbox2-flash.c map driver.
because the return values need that header file....otherwise there are always
compile errors.

thx!

greets dkey

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Amit Mistry | 3 Jan 2004 05:57

mtd char and block both on same nand flash

I have to write the MTD NAND driver for K9x1208 FLASH chip. Now, the
requirement is some of the blocks of FLASH need to be accessed like raw
block access as they contains bootloader and rest of the blocks will be
accessed through YAFFS file system. How can I access the some of the blocks
with raw FLASH access method and rest with some file system? May be the
correct question is: How can I distribute the whole NAND flash in a char
device for few blocks and block device for rest of the blocks?  In MTD
directory of linux kernel source, there are mtdchar.c and mtdblock.c they
provide the functionality of char and block driver. Can I use the mtdchar.c
and mtdblock.c of MTD layer or they are samples?  I would appreciate if you
can help me out. Thanks in advance.

Thanks & Regards,
Amit Mistry

Thanks & Regards,
Amit Mistry
Embedded Software Engineer
eInfochips Ltd.
email: amit <at> einfochips.com
phone: +91 - 79 - 6563705 x 535
---------------------------------------------------

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 1 comment |
headers
davis_g | 5 Jan 2004 15:45
Picon

Re: integrator-flash Chip reports voltage low on erase

Ping, any comments/feedback on this?

Happy New Year!

--
Regards,
George

On Mon, Dec 22, 2003 at 02:09:06PM -0500, George G. Davis wrote:
> Greetings,
> 
> First, I'm intentionlly cross posting this because portions of the relevent
> code are contained in both MTD CVS HEAD and linux-2.6.0-rmk1 patch.
> 
> I submitted a fix for this problem against linux-2.6.0-test10-rmk1 here:
> 
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=1728/1
> 
> However RMK has requested further discussion for this issue. So here goes...
> 
> The ARM Integrator/AP (see drivers/mtd/maps/integrator-flash.c) has a single
> contiguous logical bank of flash memory comprised of 4 physical banks x 2 x
> 256kib x 16-bit Intel DT28F320 devices. At least this is the case for my ARM
> Integrator/AP rev D. For my particular hardware rev of the ARM Integrator/AP,
> I get "Chip reports voltage low on erase" errors while running linux-2.6.0-rmk1
> + MTD CVS HEAD as of 19Dec03 +/-. The same problem also exists in past revs of
> linux 2.4, 2.6 and MTD CVS. So this is not a regression in recent kernels or
> MTD.
> 
> Here are the flash details from kernel init messages:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Pang | 6 Jan 2004 01:12
Favicon

mtd char and block both on same nand flash


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Charles Manning | 6 Jan 2004 02:07
Picon

Re: mtd char and block both on same nand flash

On Saturday 03 January 2004 17:57, Amit Mistry wrote:
> I have to write the MTD NAND driver for K9x1208 FLASH chip. Now, the
> requirement is some of the blocks of FLASH need to be accessed like raw
> block access as they contains bootloader and rest of the blocks will be
> accessed through YAFFS file system. How can I access the some of the blocks
> with raw FLASH access method and rest with some file system? May be the
> correct question is: How can I distribute the whole NAND flash in a char
> device for few blocks and block device for rest of the blocks?  In MTD
> directory of linux kernel source, there are mtdchar.c and mtdblock.c they
> provide the functionality of char and block driver. Can I use the mtdchar.c
> and mtdblock.c of MTD layer or they are samples?  I would appreciate if you
> can help me out. Thanks in advance.

The mtdchar laye gices you the ability to read/write data to flash from user 
space.

The mtdblock stuff is only as a way to pass a name into JFFS2 or YAFFS for 
mounting the file system.

Probably he best way to achieve what you want is to partition the device into 
two partitions, one for the bootloader and one for YAFFS.

-- Charles

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Mark Richards | 8 Jan 2004 04:03

Changing parameters on the fly - possible?

Greetings.

I am so grateful for the MTD drivers for Linux. I've had some problems
getting them established in a Mandrake 9.2 environment, but finally got a
successful kernel build completed under the 2.4.22-21mdk kernel version.
That's a few builds later than I had originally planned.  I found out, the
hard way, that Mandrake has a special kernel build that mates with their
desktop, etc.  I also had problems loading the drivers as modules using
insmod, so resorted to the custom kernel route.

My problem is that the build I did is not finding the DOC chip.  I get the
following from dmesg:

Using configured disk on chip address 0xd400
No recognized DskOnChip devices found.

However using the dInfo utility I can see the chip OK.

I was a bit over-zealous, and set the probe address manually in xconfig
before building the kernel.  Maybe this is my problem?  Is there any way to
change the behaviour of the drivers for the DOC 2000 such that, for example,
I can remove the fixed probe address, or change other parameters. or do I
have to build all over again?

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 1 comment |
headers
daniel | 8 Jan 2004 12:28

Re: Changing parameters on the fly - possible?

Hi, 

The docprobe module has a parameter doc_config_location, you can try
that one. 
I have to say though , that in my experience, autoprobing on x86 ISA
busses has always worked for me on numerous boards.

Greetings, 
Daniel 

On Thu, 2004-01-08 at 03:03, Mark Richards wrote:
> Greetings.
> 
> I am so grateful for the MTD drivers for Linux. I've had some problems
> getting them established in a Mandrake 9.2 environment, but finally got a
> successful kernel build completed under the 2.4.22-21mdk kernel version.
> That's a few builds later than I had originally planned.  I found out, the
> hard way, that Mandrake has a special kernel build that mates with their
> desktop, etc.  I also had problems loading the drivers as modules using
> insmod, so resorted to the custom kernel route.
> 
> My problem is that the build I did is not finding the DOC chip.  I get the
> following from dmesg:
> 
> Using configured disk on chip address 0xd400
> No recognized DskOnChip devices found.
> 
> However using the dInfo utility I can see the chip OK.
> 
> I was a bit over-zealous, and set the probe address manually in xconfig
(Continue reading)

Permalink | Reply | 0 comments |
headers
Axel Ludszuweit | 8 Jan 2004 08:33
Favicon

cfi_amdstd_resume vs. cfi_intelext_resume

Hello,

I have compared both function, mentioned in the subject.
I think, there is an error in
  static void cfi_intelext_resume(struct mtd_info *mtd),
which can be fixed with the following patch.

--- ./drivers/mtd/chips/cfi_cmdset_0001.c.orig  2004-01-08 08:28:23.000000000 +0100
+++ ./drivers/mtd/chips/cfi_cmdset_0001.c       2004-01-08 08:29:29.000000000 +0100
 <at>  <at>  -1676,7 +1676,7  <at>  <at> 

                /* Go to known state. Chip may have been power cycled */
                if (chip->state == FL_PM_SUSPENDED) {
-                       cfi_write(map, CMD(0xFF), 0);
+                       cfi_write(map, CMD(0xFF), chip->start);
                        chip->state = FL_READY;
                        wake_up(&chip->wq);
                }

Is this correct, or have I misunderstanding something?

--

-- 

--------------------------------------------

Axel Ludszuweit

Keymile GmbH
Wohlenbergstr. 3, D-30179 Hannover
(Continue reading)

Permalink | Reply | 0 comments |

Gmane