headers
Artem Bityutskiy | 1 Jul 2010 05:44
Picon

Re: [PATCH] mtd: Added an ioctl to query the lock status of a flash sector.

On Mon, 2010-06-14 at 18:10 +0200, Richard Cochran wrote:
> On Sun, Jun 13, 2010 at 12:05:03PM +0300, Artem Bityutskiy wrote:
> > I think it is tiny bit nicer to name 'is_locked', which is a bit more
> > consistent with the already existing 'block_isbad'?
> 
> Okay, here it is again.
> 
> Thanks,
> Richard
> 
> 
> This patchs adds a way for user space programs to find out whether a
> flash sector is locked. An optional driver method in the mtd_info struct
> provides the information.
> 
> Signed-off-by: Richard Cochran <richard.cochran <at> omicron.at>

Pushed to l2-mtd-2.6.git / master.

--

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
oleg ershov | 1 Jul 2010 07:01
Picon

help me


My board is CM-F82 CompuLab.I am using LynxOS-178 2.1.0.
>I use U-boot 1.1.3 as my bootloader.
>I have target platform - PowerPC; Board: CM-F82 CompuLab, busfreq 
>100 MHz; processor MPC8272 Freescale.
>
>I need driver File System for LynxOS for CF of size >= 1Gb.
>
>Any ideas?
>Best regards,
>Oleg Ershov

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 1 comment |
headers
Mike Frysinger | 1 Jul 2010 07:36
Picon

Re: help me

On Thu, Jul 1, 2010 at 01:01, oleg ershov wrote:
> My board is CM-F82 CompuLab.I am using LynxOS-178 2.1.0.
>>I use U-boot 1.1.3 as my bootloader.
>>I have target platform - PowerPC; Board: CM-F82 CompuLab, busfreq
>>100 MHz; processor MPC8272 Freescale.
>>
>>I need driver File System for LynxOS for CF of size >= 1Gb.

why are you asking on a Linux list for LynxOS support ?  Linux !=
Lynx.  try a more appropriate list.
-mike

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Matthieu CASTET | 1 Jul 2010 10:29
Favicon

[UBIFS] 2.6.27-backport bug

Hi,

I know 2.6.27-backport is not supported anymore, but I found a bug, and 
I post it for the record.

The bug happen with a kernel oops [1].

After investigation it happens because of programming a timer that is 
already programmed (we don't check wbuf->no_timer in new_wbuf_timer_nolock)

Matthieu

[1]
Unable to handle kernel NULL pointer dereference at virtual address 
00000008
pgd = c71b0000 

[00000008] *pgd=47853031, *pte=00000000, *ppte=00000000 

Internal error: Oops: 17 [#1] 

CPU: 0    Not tainted  (2.6.27.44-parrot-01137-gbf2d001-dirty #13) 

PC is at rb_insert_color+0x34/0x148 

LR is at enqueue_hrtimer+0x80/0xa8 

pc : [<c00faa54>]    lr : [<c0049ab8>]    psr: 60000093 

sp : c7073c80  ip : c7073ca0  fp : c7073c9c
(Continue reading)

Permalink | Reply | 2 comments |
headers
Artem Bityutskiy | 1 Jul 2010 12:56
Picon

Re: [UBIFS] 2.6.27-backport bug

On Thu, 2010-07-01 at 10:29 +0200, Matthieu CASTET wrote:
> Hi,
> 
> I know 2.6.27-backport is not supported anymore, but I found a bug, and 
> I post it for the record.
> 
> The bug happen with a kernel oops [1].
> 
> After investigation it happens because of programming a timer that is 
> already programmed (we don't check wbuf->no_timer in new_wbuf_timer_nolock)

Thanks, although I do not maintain 2.6.27 port anymore [1], I will of
course push your patch a bit later, when I find time to process my MTD
input queue :-)

[1] http://www.linux-mtd.infradead.org/doc/ubifs.html#L_source

--

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Teemu Peltola | 1 Jul 2010 15:33

Re: mxc_nand: write problem with i.MX-27L + ST NAND512R3A2DZA6E flash

Hi,

> I have a device based on i.MX-27L and I am updating kernel from 2.6.24
> with a custom set of patches to vanilla 2.6.34. I am having problems
> using mxc_nand driver with ST NAND512R3A2DZA6E flash chip (64MB,
> 8-bit, 512 byte page size). I am using
> arch/arm/mach-mx2/mach-mx27ads.c based board file.
>
> The problem is that write operations fail. If I have
> CONFIG_MTD_NAND_VERIFY_WRITE=y, CONFIG_MTD_DEBUG=y,
> CONFIG_MTD_DEBUG_VERBOSE=0 enabled in my kernel config and use
> mtd_pagetest module I see the following output:
> 
> $> modprobe mtd_pagetest dev=4
> =================================================
> mtd_pagetest: MTD device: 4
> mtd_pagetest: MTD device size 1048576, eraseblock size 16384, page
> size 512, count of eraseblocks 64, pages per eraseblock 32, OOB size
> 16
> mtd_pagetest: scanning for bad eraseblocks
> mtd_pagetest: scanned 64 eraseblocks, 0 are bad
> mtd_pagetest: erasing whole device
> mtd_pagetest: erased 64 eraseblocks
> mtd_pagetest: writing whole device
> mtd_pagetest: error: write failed at 0x0
> mtd_pagetest: error -5 occurred
> =================================================

It seems that using CONFIG_MTD_NAND_VERIFY_WRITE option with mxc_nand driver in kernel 2.6.34 causes
every MTD write to fail. That is because in nand_base.c, nand_write_page function there is a call to
(Continue reading)

Permalink | Reply | 0 comments |
headers
BRITISH COLUMBIA | 1 Jul 2010 18:09
Favicon

Re !

Your email has been awarded 1,263,584.00 GBP (One Million Two Hundred and Sixtythree Thousand,Five
Hundred and Eightyfour Pounds Sterling) By British Columbia Lottery,Do send us Names, Address, Tel and
Occupation for processing.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Permalink | Reply | 0 comments |
headers
Guillaume LECERF | 2 Jul 2010 14:39
Picon

[PATCH] mtd: cfi_cmdset_0002: fix the check for valid primary extension versions

Valid primary extension versions are: 1.0, 1.1, 1.2, 1.3 [1][2].
Fix the check in cfi_cmdset_0002 accordingly.

[1] http://www.amd.com/us-en/assets/content_type/DownloadableAssets/cfi_r20.pdf, page 19
[2] http://www.amd.com/us-en/assets/content_type/DownloadableAssets/cfi_100_20011201.pdf

Signed-off-by: Florian Fainelli <florian <at> openwrt.org>
Signed-off-by: Guillaume LECERF <glecerf <at> gmail.com>
---
 drivers/mtd/chips/cfi_cmdset_0002.c |   15 ++++++++++++---
 1 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
index d81079e..749203f 100644
--- a/drivers/mtd/chips/cfi_cmdset_0002.c
+++ b/drivers/mtd/chips/cfi_cmdset_0002.c
 <at>  <at>  -417,16 +417,25  <at>  <at>  struct mtd_info *cfi_cmdset_0002(struct map_info *map, int primary)
 			 */
 			cfi_fixup_major_minor(cfi, extp);

+			/*
+			 * Valid primary extension versions are: 1.0, 1.1, 1.2, 1.3
+			 * see: http://www.amd.com/us-en/assets/content_type/DownloadableAssets/cfi_r20.pdf, page
19 and on
+			 *      http://www.amd.com/us-en/assets/content_type/DownloadableAssets/cfi_100_20011201.pdf
+			 */
 			if (extp->MajorVersion != '1' ||
-			    (extp->MinorVersion < '0' || extp->MinorVersion > '4')) {
+			    (extp->MajorVersion == '1' && ( extp->MinorVersion < '0' || extp->MinorVersion > '3'))) {
 				printk(KERN_ERR "  Unknown Amd/Fujitsu Extended Query "
(Continue reading)

Permalink | Reply | 1 comment |
headers
Arno Steffen | 5 Jul 2010 13:17

uncorrectable error :

While testing my OMAP board powering and unplug power it happens from
time to time that this message occur while mounting / (jffs2).
uncorrectable error :

Mostly the system continues booting, sometimes it crashes. I assume
that this depends on where this error is located.
The partition is writable but in this tests no write access will be done.

BUT: In the next power cycle the "uncorrectable error" is disappeared
- so it might not be really uncorrectable.
I am really helpless what might be the reason for this strange
behavior. As the flash content seems not to be corrupted, can this be
a read failure?
What can I do to find out what is going on here?

Below the complete message while boot..

IP-Config: Complete:
     device=eth0, addr=192.168.90.202, mask=255.255.255.0, gw=192.168.90.1,
     host=192.168.90.202, domain=, nis-domain=(none),
     bootserver=192.168.90.230, rootserver=192.168.90.230, rootpath=
uncorrectable error :
uncorrectable error :
mtd->read(0x400 bytes from 0x2a0000) returned ECC error
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002a0000:
0xff30 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002a0004:
0xff30 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002a0008:
0xff30 instead
(Continue reading)

Permalink | Reply | 2 comments |
headers
Kevin Cernekee | 6 Jul 2010 00:10
Picon

[PATCH 4/5] libmtd: add support for 64-bit offsets, OOB

Change mtd_erase() so that it attempts to use MEMERASE64 first, then falls
back to the old <2.6.31 MEMERASE if MEMERASE64 is unsupported.

Add mtd_read_oob(), mtd_write_oob() functions to wrap the OOB ioctls.
Similar ioctl fallback logic is used in these functions as well.

Signed-off-by: Kevin Cernekee <cernekee <at> gmail.com>
---
 include/libmtd.h |   26 +++++++++++++++++++++
 lib/libmtd.c     |   65 +++++++++++++++++++++++++++++++++++++++++++++++++++--
 2 files changed, 88 insertions(+), 3 deletions(-)

diff --git a/include/libmtd.h b/include/libmtd.h
index 0aea966..2241343 100644
--- a/include/libmtd.h
+++ b/include/libmtd.h
 <at>  <at>  -149,6 +149,32  <at>  <at>  int mtd_get_dev_info1(libmtd_t desc, int mtd_num, struct mtd_dev_info *mtd);
 int mtd_erase(const struct mtd_dev_info *mtd, int fd, int eb);

 /**
+ * mtd_read_oob - read OOB bytes
+ *  <at> fd: MTD device node file descriptor
+ *  <at> start: page-aligned start address
+ *  <at> length: number of OOB bytes to read
+ *  <at> data: read buffer
+ *
+ * This function reads  <at> length OOB bytes starting from address  <at> start on
+ * MTD device described by  <at> fd. Returns %0 in case of success and %-1 in
+ * case of failure.
+ */
(Continue reading)

Permalink | Reply | 2 comments |

Gmane