)]}' { "log": [ { "commit": "f1a28c02843efcfcc41982149880bac3ac180234", "tree": "b15ca1a140e463ef3cde6b9a8591e7be172ee1f1", "parents": [ "9a1fcdfd4bee27c418424cac47abf7c049541297" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 30 00:37:34 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 30 00:37:34 2006 +0200" }, "message": "[MTD] NAND Expose the new raw mode function and status info to userspace\n\nThe raw read/write access to NAND (without ECC) has been changed in the\nNAND rework. Expose the new way - setting the file mode via ioctl - to\nuserspace. Also allow to read out the ecc statistics information so userspace\ntools can see that bitflips happened and whether errors where correctable\nor not. Also expose the number of bad blocks for the partition, so nandwrite\ncan check if the data fits into the parition before writing to it.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "8593fbc68b0df1168995de76d1af38eb62fd6b62", "tree": "dd244def53d2be4f1fbff9f74eac404fab8e240f", "parents": [ "f4a43cfcecfcaeeaa40a9dbc1d1378298c22446e" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Mon May 29 03:26:58 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Mon May 29 15:06:51 2006 +0200" }, "message": "[MTD] Rework the out of band handling completely\n\nHopefully the last iteration on this!\n\nThe handling of out of band data on NAND was accompanied by tons of fruitless\ndiscussions and halfarsed patches to make it work for a particular\nproblem. Sufficiently annoyed by I all those \"I know it better\" mails and the\nresonable amount of discarded \"it solves my problem\" patches, I finally decided\nto go for the big rework. After removing the _ecc variants of mtd read/write\nfunctions the solution to satisfy the various requirements was to refactor the\nread/write _oob functions in mtd.\n\nThe major change is that read/write_oob now takes a pointer to an operation\ndescriptor structure \"struct mtd_oob_ops\".instead of having a function with at\nleast seven arguments.\n\nread/write_oob which should probably renamed to a more descriptive name, can do\nthe following tasks:\n\n- read/write out of band data\n- read/write data content and out of band data\n- read/write raw data content and out of band data (ecc disabled)\n\nstruct mtd_oob_ops has a mode field, which determines the oob handling mode.\n\nAside of the MTD_OOB_RAW mode, which is intended to be especially for\ndiagnostic purposes and some internal functions e.g. bad block table creation,\nthe other two modes are for mtd clients:\n\nMTD_OOB_PLACE puts/gets the given oob data exactly to/from the place which is\ndescribed by the ooboffs and ooblen fields of the mtd_oob_ops strcuture. It\u0027s\nup to the caller to make sure that the byte positions are not used by the ECC\nplacement algorithms.\n\nMTD_OOB_AUTO puts/gets the given oob data automaticaly to/from the places in\nthe out of band area which are described by the oobfree tuples in the ecclayout\ndata structre which is associated to the devicee.\n\nThe decision whether data plus oob or oob only handling is done depends on the\nsetting of the datbuf member of the data structure. When datbuf \u003d\u003d NULL then\nthe internal read/write_oob functions are selected, otherwise the read/write\ndata routines are invoked.\n\nTested on a few platforms with all variants. Please be aware of possible\nregressions for your particular device / application scenario\n\nDisclaimer: Any whining will be ignored from those who just contributed \"hot\nair blurb\" and never sat down to tackle the underlying problem of the mess in\nthe NAND driver grown over time and the big chunk of work to fix up the\nexisting users. The problem was not the holiness of the existing MTD\ninterfaces. The problems was the lack of time to go for the big overhaul. It\u0027s\neasy to add more mess to the existing one, but it takes alot of effort to go\nfor a real solution.\n\nImprovements and bugfixes are welcome!\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "5bd34c091a044d130601370c370f84b1c59f1627", "tree": "8b08012a9a30186a8805d506f8438e2944f5f31b", "parents": [ "ff268fb8791cf18df536113355d7184007c269d9" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Sat May 27 22:16:10 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Mon May 29 15:06:50 2006 +0200" }, "message": "[MTD] NAND Replace oobinfo by ecclayout\n\nThe nand_oobinfo structure is not fitting the newer error correction\ndemands anymore. Replace it by struct nand_ecclayout and fixup the users\nall over the place. Keep the nand_oobinfo based ioctl for user space\ncompability reasons.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "ff268fb8791cf18df536113355d7184007c269d9", "tree": "3a7d9fc72b28f5a0f11a2f8b08174b1bee6ea20d", "parents": [ "8be834f76291fdcc0614cb84926c6910b9f2ecbc" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Sat May 27 20:36:12 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Mon May 29 15:06:49 2006 +0200" }, "message": "[MTD] NAND Consolidate oobinfo handling\n\nThe info structure for out of band data was copied into\nthe mtd structure. Make it a pointer and remove the ability\nto set it from userspace. The position of ecc bytes is\ndefined by the hardware and should not be changed by software.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "9223a456da8ed357bf7e0b128c853e2c8bd54614", "tree": "50cb225c4ba9c610ae4cb67231b319e78e935ac4", "parents": [ "2528e8cdf376d7da24647c442ec1e88c360d76ca" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 23 17:21:03 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 23 17:21:03 2006 +0200" }, "message": "[MTD] Remove read/write _ecc variants\n\nMTD clients are agnostic of FLASH which needs ECC suppport.\nRemove the functions and fixup the callers.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "2528e8cdf376d7da24647c442ec1e88c360d76ca", "tree": "09df5f524085f4d12117fc81791bca10fa8a5f0e", "parents": [ "9d8522df37f91621a70c5c0dbbf5bf2220b16798" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 23 16:10:00 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 23 16:10:00 2006 +0200" }, "message": "[MTD] Remove readv/readv_ecc\n\nThese functions were never implemented and added only bloat to\npartition and concat code.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "9d8522df37f91621a70c5c0dbbf5bf2220b16798", "tree": "30f51aaccb18b1d4a97b7a5c8a64c63633a2fb7b", "parents": [ "0cddd6c258b2ed3798d12619c28ed0d2b5a669bc" ], "author": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 23 16:06:03 2006 +0200" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@cruncher.tec.linutronix.de", "time": "Tue May 23 16:06:03 2006 +0200" }, "message": "[MTD] Remove nand writev support\n\nNAND writev(_ecc) support is not longer necessary. Remove it.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "28318776a80bc3261f9af91ef79e6e38bb9f5bec", "tree": "36ef9144accf19db9d51019aa479807e80aeb8fd", "parents": [ "8ca9ed5db3aea8d27989c239e8a2f79b839f1e99" ], "author": { "name": "Joern Engel", "email": "joern@wh.fh-wedel.de", "time": "Mon May 22 23:18:05 2006 +0200" }, "committer": { "name": "Joern Engel", "email": "joern@wh.fh-wedel.de", "time": "Mon May 22 23:18:05 2006 +0200" }, "message": "[MTD] Introduce writesize\n\nAt least two flashes exists that have the concept of a minimum write unit,\nsimilar to NAND pages, but no other NAND characteristics. Therefore, rename\nthe minimum write unit to \"writesize\" for all flashes, including NAND.\n\nSigned-off-by: Joern Engel \u003cjoern@wh.fh-wedel.de\u003e\n" }, { "commit": "ae282d497d5631ce31539717131c760e3872c539", "tree": "a3067a25401d0fa0d8cf409827d4d7031523095f", "parents": [ "599fb3298b70d75c12dbdc4dd30f52c5cf04ea2f" ], "author": { "name": "Vitaly Wool", "email": "vwool@ru.mvista.com", "time": "Wed May 17 12:34:27 2006 +0100" }, "committer": { "name": "David Woodhouse", "email": "dwmw2@infradead.org", "time": "Wed May 17 12:34:27 2006 +0100" }, "message": "[MTD] generic: propagate oobavail to MTD partitions\n\n\u0027oobavail\u0027 parameter of mtd_info structure is now propagated to the MTD\npartitions\n\nSigned-off-by: Vitaly Wool \u003cvwool@ru.mvista.com\u003e\nSigned-off-by: David Woodhouse \u003cdwmw2@infradead.org\u003e\n" }, { "commit": "97894cda5773e59bd13e87b72077751099419a9f", "tree": "9a039ab8c122ae9a4f64d285e2da0efd1356789e", "parents": [ "b95f9609c761a14d1e7be1a89f2a66399b5ae343" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Mon Nov 07 11:15:26 2005 +0000" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@mtd.linutronix.de", "time": "Mon Nov 07 13:37:38 2005 +0100" }, "message": "[MTD] core: Clean up trailing white spaces\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "5cea5dadfebdede8045fca118328860058129eb2", "tree": "341645da538e4606a139d7b3cbce23e0901a9ca2", "parents": [ "daba5cc4bcd025a9b4fd02a9117c71bfd400d811" ], "author": { "name": "Artem B. Bityutskiy", "email": "dedekind@infradead.org", "time": "Fri Sep 30 15:49:12 2005 +0100" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@mtd.linutronix.de", "time": "Sun Nov 06 23:04:14 2005 +0100" }, "message": "[MTD] mtdpart.c: Allow eraseblock size !\u003d power of 2\n\nDon\u0027t assume eraseblock size is power of 2.\nDataflash can have aligned eraseblock size.\n\nFrom: Peter Menzebach \u003cpm-mtd@mw-itcon.de\u003e\nAcked-by: Artem B. Bityutskiy \u003cdedekind@infradead.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "f77814dd5728edaf1239d19755d2aa0d8c33d861", "tree": "5cf7f73aa367bf152e5fbd16b5173e18bb787dd5", "parents": [ "67d9e95c393d23c229836e28b262dc73d71da784" ], "author": { "name": "Nicolas Pitre", "email": "nico@cam.org", "time": "Tue Feb 08 17:11:19 2005 +0000" }, "committer": { "name": "Thomas Gleixner", "email": "tglx@mtd.linutronix.de", "time": "Mon May 23 12:25:23 2005 +0200" }, "message": "[MTD] Support for protection register support on Intel FLASH chips\n\nThis enables support for reading, writing and locking so called\n\"Protection Registers\" present on some flash chips.\nA subset of them are pre-programmed at the factory with a\nunique set of values. The rest is user-programmable.\n\nSigned-off-by: Nicolas Pitre \u003cnico@cam.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }