Miss. Angela Koffi | 1 Oct 11:39 2011

Negotiating for Investment Partners


In good faith,

I have a substantial capital honorably inherited from my late father amounting 
to the $12, 500.000.00 (USD) which I have decided to invest in any lucrative 
business in your country while I continue my education there.

Should this be of any interest to you, kindly respond because I will be left 
with no choice in seeking elsewhere if I did not hear from you this week.

Your urgent response needed.

Miss. Angela Koffi

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Artem Bityutskiy | 1 Oct 13:39 2011
Picon

Re: [PATCH] jffs2/security.c: local functions should be static

On Fri, 2011-09-23 at 15:56 -0700, H Hartley Sweeten wrote:
> Quiets the sparse noise:
> 
> warning: symbol 'jffs2_initxattrs' was not declared. Should it be static?
> 
> Signed-off-by: H Hartley Sweeten <hsweeten <at> visionengravers.com>
> Cc: David Woodhouse <dwmw2 <at> infradead.org>

Against which tree is this patch? My l2-mtd-2.6 tree does not have this
function, and it is based on Linux 3.1-rc2.

--

-- 
Best Regards,
Artem Bityutskiy

Bityutskiy, Artem | 1 Oct 13:39 2011
Picon

Re: [PATCH v2] mtd: r852: make r852_pm_ops static

On Mon, 2011-09-26 at 10:13 +0800, Axel Lin wrote:
> It is not used outside this driver so no need to make the symbol global.
> Also make r852_suspend and r852_resume static.
> 
> Signed-off-by: Axel Lin <axel.lin <at> gmail.com>
> ---
> v2: Also make r852_suspend and r852_resume static

Pushed to l2-mtd-2.6.git, thanks!

-- 
Best Regards,
Artem Bityutskiy
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Robert Jarzmik | 1 Oct 14:19 2011
Picon

Re: [PATCH V4] mtd: Add DiskOnChip G3 support

Arnd Bergmann <arnd <at> arndb.de> writes:

> I generally recommend removing debug messages like this entirely from
> production code. If you need them on production systems, that is an indication
> that the code quality is not good enough.
Perhaps.
But when you create a driver without any specification, and you release it to
the communauty, there will be unmet behaviours. So, when someone will ask me
"why in my board XXX my docg3 can't read data ?" how can I improve the driver
without any traces ?

> Enabling the debug output like
> this also creates a lot of almost identical strings, which you don't need
> if you turn it into an extern function that does
>
> 	static const char docseq[] = {
> 		[DOC_SEQ_RESET]		 = "reset",
> 		[DOC_SEQ_PAGE_SIZE_532]	 = "page_size_532",
> 	};
> 	dev_dbg(dev, "doc_flashSequence: %02x %s\n", docseq[seq]);
> with exactly the same output.
That doesn't look very good, as the sequence numbers are sparse numbers, and we
can finish with an array with values (0, 3, 8, 0xff) filled, and all the
remaining are null pointers (as these sequence numbers don't exist).

> Or you could turn the entire tracing into trace events and do the parsing
> in user space, which seems appropriate if you frequently need to trace
> these.
This looks much much better. I'll have a peek into that, as only (io_address,
read/write, width, value) could be dumped, and userland application could
(Continue reading)

Artem Bityutskiy | 1 Oct 16:08 2011
Picon

Re: [PATCHv9] UBI: new module ubiblk: block layer on top of UBI

On Mon, 2011-09-26 at 16:40 +0200, David Wagner wrote:
> ubiblk is a read-only block layer on top of UBI.  It presents UBI volumes as
> read-only block devices (named ubiblkX_Y, where X is the UBI device number
> and Y the Volume ID).
> 
> It is used by putting a block filesystem image on a UBI volume, creating the
> corresponding ubiblk device and then mounting it.
> 
> It uses the UBI API to register to UBI notifications and to read from the
> volumes.  It also creates a ubiblk_ctrl device node that simply receives ioctl
> from a userspace tool for creating/removing ubiblk devices.
> 
> Some code is taken from mtd_blkdevs and gluebi.  Some code for the ioctl part is
> also inspired from ubi's core.
> 
> Advantages of ubiblk over gluebi+mtdblock_ro:

I do not have enough time to nicely answer with comments, so here is
just some patch with my cosmetic changes plus I added "TODO:" items here
and there. Please, apply it and resolve the TODO items, if you can, ok?

diff --git a/drivers/mtd/ubi/ubiblk.c b/drivers/mtd/ubi/ubiblk.c
index ccb22de..2da46fe 100644
--- a/drivers/mtd/ubi/ubiblk.c
+++ b/drivers/mtd/ubi/ubiblk.c
 <at>  <at>  -40,7 +40,7  <at>  <at> 
 #define BLK_SIZE 512

 /**
- * struct ubiblk_dev - represents a ubiblk device, proxying a UBI volume
(Continue reading)

-= KuK =- | 1 Oct 16:55 2011
Picon

Problem with JFFS2 mount

Hi,

I have problem with creating image file from mounted jffs2 file system.

I have 1:1 dump from 1GB NAND which is UBI format.
But it contains JFFS part also.
This part can be downloaded from my server.
www.pouchx.com/PRV/HDS/K9G8G08U0M_Samsung_1GB_NAND_Config.ini_block_JFFS.rar

Archive contains two files. One is original JFFS copy, second is same 
file but I deleted ECC blocks.

I mount jffs image (noECC) with this script:

$ sudo apt-get install mtd-tools
$ sudo modprobe -v mtd
$ sudo modprobe -v jffs2
$ sudo modprobe -v mtdram total_size=8192 erase_size=256
$ sudo modprobe -v mtdchar
$ sudo modprobe -v mtdblock
$ sudo dd if=/HDS/Config.img of=/dev/mtd0
$ sudo mount -t jffs2 /dev/mtdblock0 /HDS/JFFS

After that I can see all 3 files that are in jffs image:
can_unique_id
Config.ini
MAC

I make no changes to these files.

(Continue reading)

Arnd Bergmann | 1 Oct 17:02 2011
Picon

Re: [PATCH V4] mtd: Add DiskOnChip G3 support

On Saturday 01 October 2011 14:19:08 Robert Jarzmik wrote:
> Arnd Bergmann <arnd <at> arndb.de> writes:
> 
> > I generally recommend removing debug messages like this entirely from
> > production code. If you need them on production systems, that is an indication
> > that the code quality is not good enough.
> Perhaps.
> But when you create a driver without any specification, and you release it to
> the communauty, there will be unmet behaviours. So, when someone will ask me
> "why in my board XXX my docg3 can't read data ?" how can I improve the driver
> without any traces ?

In my experience, the kind of debugging data you need for analysing a problem
on someone else's system is not just a trace of the commands you send to
a device but more complicated to get, so you are dependent on a clueful
bug reporter anyway.

If you have successfully debugged a remote problem just by looking at a dump,
then you should certainly leave the code in there.

> > Or you could turn the entire tracing into trace events and do the parsing
> > in user space, which seems appropriate if you frequently need to trace
> > these.
> This looks much much better. I'll have a peek into that, as only (io_address,
> read/write, width, value) could be dumped, and userland application could
> translate it into sequence/nop/flashcontrol ... etc ...

Right, that was the idea.

	Arnd
(Continue reading)

Saarinen Johanna | 2 Oct 15:33 2011
Picon
Picon

Final Notice


YAHOO/REDIFFMAIL/GMAIL/AOL/MSN.
Top of the day to you.

For being a regular Web-User,Your email ID has won 750,000 GBP and 
a cheque has been submitted to INTER CARGO COURIER. Contact the courier 
company with your full info for claims 

Email: intercourier02 <at> hotmail.co.uk
Telephone Number:+447024012706              
Fax Number: +448573339013

Please use this as a subject of contact : PARCEL/NUM/1090.
Congratulations!!!
Bar.Reena Parkson
CUSTOMER CARE OFFICER
YAHOO/REDIFFMAIL/GMAIL/AOL/MSN.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Hitz, Christian | 3 Oct 08:57 2011

[PATCH] mtd: nand: restore useage of ONFI reported bus width

This patch changes the nand_flash_detect_onfi() function to pass
the NAND bus width it discovered via ONFI back to the caller.

Signed-off-by: Christian Hitz <christian.hitz <at> aizo.com>
---
 drivers/mtd/nand/nand_base.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
index a46e9bb..6dae9a0 100644
--- a/drivers/mtd/nand/nand_base.c
+++ b/drivers/mtd/nand/nand_base.c
 <at>  <at>  -2829,7 +2829,7  <at>  <at>  static u16 onfi_crc16(u16 crc, u8 const *p, size_t len)
  * Check if the NAND chip is ONFI compliant, returns 1 if it is, 0 otherwise
  */
 static int nand_flash_detect_onfi(struct mtd_info *mtd, struct nand_chip *chip,
-					int busw)
+					int *busw)
 {
 	struct nand_onfi_params *p = &chip->onfi_params;
 	int i;
 <at>  <at>  -2884,9 +2884,9  <at>  <at>  static int nand_flash_detect_onfi(struct mtd_info *mtd, struct nand_chip *chip,
 	mtd->erasesize = le32_to_cpu(p->pages_per_block) * mtd->writesize;
 	mtd->oobsize = le16_to_cpu(p->spare_bytes_per_page);
 	chip->chipsize = (uint64_t)le32_to_cpu(p->blocks_per_lun) * mtd->erasesize;
-	busw = 0;
+	*busw = 0;
 	if (le16_to_cpu(p->features) & 1)
-		busw = NAND_BUSWIDTH_16;
+		*busw = NAND_BUSWIDTH_16;
(Continue reading)

angelo | 3 Oct 10:52 2011
Picon

erase block < 8KiB

Hi all,

i read several mail about this limitation.

http://lists.infradead.org/pipermail/linux-mtd/2011-February/033851.html
http://lists.infradead.org/pipermail/linux-mtd/2011-June/036498.html

I have a 4 KiB erase-size, common of some SST nor flash'es like mine 
(SST 39VF3201B).

 From all the posts i read here in the list, there seems not to be any 
solution guaranteed.

The tricky change to mkfs.jffs2 don't work for me. It seems to work for 
small files, but i still get error messages copying a 600KB file in the 
partition.
If it's true that the minimal jffs2 block is 4KB + some bytes, of course 
the patch to mkfs.jffs2 can't work.

Some one suggested the "virtual erase block" solution. I would like to 
try to implement it, if i have the time.

In any case, for the common users, is there maybe another flash file 
system that can work with 4KiB erase size ?

Many thanks,
Regards

Angelo Dureghello

(Continue reading)


Gmane