> > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > > > This patch should not be merged in its current form. > > Linux kernel driver development shall be against the > current -rc > kernel, and there is no need to reinvent the > "REQUEST_FIRMWARE" > mechanism. > > Furthermore, the changeset introduces more bits of this > "SMS_HOSTLIB_SUBSYS" -- this requires a binary library > present on the > host system. This completely violates the "no > multiple APIs in > kernel" and "no proprietary APIs in kernel" guidelines. > > Uri, what are your plans for this? > > Regards, > > Mike > Mike, Per discussion with other members of the community, backport are welcome at LinuxTV mercurial (true they are not pass through when up-streaming to the kernel git, but that is per current kernel version anyway ...). Regarding the REQUEST_FIRMWARE - with most older kernels, and with some new (I even have such 2.6.27 case), that is the only option available, Please check Motorola (opensource.motorola.com) and Google Android for external examples. Second issue is that when you are using interface like SPI, the hotplug mechanism is degenerated or simply voided. So we can either decide we support only x86 based machines, but if I'm not wrong, I can see lots of TI OMAP (and other ARM) activity lately, so, we may decide to support REQUEST_FIRMWARE... Regarding SMS_HOSTLIB_SUBSYS, since it's not defined its... undefined... The patch replace '#if 0' with '#ifdef SMS_HOSTLIB_SUBSYS' (which is... undefined), so actually no "harm" done, but it make the life of Siano's engineers, and various other who use patches and merges, easier when looking at the code (IMHO strings are better than magic numbers). I simply don't see what's wrong with that. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
