On Sun, 2010-05-30 at 02:54 +0200, Arnd Bergmann wrote: > The reason we have the driver is so that we're able to use the kernel > internal functions for arch/powerpc/kernel/nvram_64.c on it, which > operated on the well-defined interface for partitions inside of the > nvram memory. > > mtd/phram provides a completely different abstraction, which is normally > used for block- or file system based access. They also both have > the character device, but that's not really the main point. > > The part that is unfortunate is the device_type matching in the driver, > which was a result of clueluess firmware and Linux developers (i.e. me) > at the time.
Right. Which is why I want to change it to be a platform device, so that platforms explicitely instanciate it, which is probably the best thing for now. That way, platforms that don't want the ppc specific nvram stuff don't have to instanciate it, or platforms who want to use the mtd bits, etc... Cheers, Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev