linux-toradex.git/include/linux/mtd/flashchip.h, branch v2.6.18-rc7 Linux kernel for Apalis and Colibri modules [MTD] includes: Clean up trailing white spaces 2005-11-07T13:32:58+00:00 Thomas Gleixner tglx@linutronix.de 2005-11-07T11:15:31+00:00 61ecfa8777d0bc8e33dc0e5c2cca9b3247da2d37 Signed-off-by: Thomas Gleixner <tglx@linutronix.de> 
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
[MTD] Fixed signed 1bit bitfield 2005-05-23T10:51:30+00:00 Ben Dooks ben@simtec.co.uk 2005-03-14T18:27:18+00:00 0514cd938009de1d6b3239d98c3cf2a67b620103 Signed-off-by: Ben Dooks <ben@simtec.co.uk> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> 
Signed-off-by: Ben Dooks <ben@simtec.co.uk>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
[MTD] Support for protection register support on Intel FLASH chips 2005-05-23T10:25:23+00:00 Nicolas Pitre nico@cam.org 2005-02-08T17:11:19+00:00 f77814dd5728edaf1239d19755d2aa0d8c33d861 This enables support for reading, writing and locking so called "Protection Registers" present on some flash chips. A subset of them are pre-programmed at the factory with a unique set of values. The rest is user-programmable. Signed-off-by: Nicolas Pitre <nico@cam.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> 
This enables support for reading, writing and locking so called
"Protection Registers" present on some flash chips.
A subset of them are pre-programmed at the factory with a
unique set of values. The rest is user-programmable.

Signed-off-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Linux-2.6.12-rc2 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!