On Wed, Aug 17, 2011 at 12:39 AM, Artem Bityutskiy <dedeki...@gmail.com> wrote: > I think the OOB mode should not be a global MTD device state. Each > ioctl invocation should just specify the mode.
I agree. This brings up some questions, though. See below. > Brian's idea of having a completely new ioctl or a set of new ioctls for > OOB which would copletely deprecate the old ones is a good idea. Let's > wait for his patch. I sent a patch series (RFC) to the MTD mailing list. You can see the cover description, which describes my proposed changes and asks some questions, at the following link, but for some reason the patches are being held up by the mailing list software - for now, you'll only receive them if you were CC'd directly: http://lists.infradead.org/pipermail/linux-mtd/2011-August/037522.html Follow that thread for more information. > May be we should even start physically removing depricated ioctls by > first adding a printk with a warning and then removing completely. But > first mtdutils should be updated to not use them. Yes, this sounds fine, although I'm not too familiar with the MTD_OOB_AUTO stuff, so I'm not sure how well it will replace all the uses of MEMGETOOBSEL. I don't actually see any users of ECCGETLAYOUT; I think I've asked about this ioctl before, but I can't seem to find any response...perhaps it can be killed with no work? Brian _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
