![]() | |||||||||||||
Messages in this thread |
On Mon, 2006-09-18 at 10:12 +0200, Haavard Skinnemoen wrote: > On Fri, 15 Sep 2006 16:32:26 +0100 > David Woodhouse <dwmw2@infradead.org> wrote: > > > On Fri, 2006-09-15 at 16:37 +0200, Haavard Skinnemoen wrote: > > > If a cfi_cmdset_0002 fixup installs an unlock() operation, use it > > > to unlock the whole flash after the erase regions have been set up. > > > > There are cmdset_0001 chips which have this affliction too. I was > > thinking of having a flag MTD_STUPID_LOCK which you set when you > > determine that it's one of these chips, then add_mtd_device() can do > > the unlocking... or add_mtd_partitions() can do it but _only_ for > > writable partitions. > > Ok, so how about something like this? Which other chips should be marked? Looks good; thanks. There's some Intel chips which need to be so marked but I'll let the Intel folks deal with that. I'll apply it to my git tree, but only _after_ Linus has pulled from it as requested a couple of days ago -- I think this should wait for 2.6.19 rather than being slipped in at the last moment. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-09-18 10:17 [from the cache] ©2003-2008 | |||||||||||||