On Fri, Dec 18, 2009 at 09:03:26AM -0800, Shahar Or wrote: > On Fri, Dec 18, 2009 at 5:37 PM, Luis R. Rodriguez > <lrodriguez@xxxxxxxxxxx> wrote: > >> If we have all the IDs from the INF file, then why do we need this in > >> userspace? Is the list growing? > > > > No, but for other newer hardware/drivers it can likely grow, so my > > comment was more of a generic driver approach to this. > > Is this a linux-wireless thing You mean my suggestion? It depends, I personally am not aware of upstream drivers keeping tabs on knobs in userspace currently but I do think things like configs are used to tweak, for example Oracle db stuff. configs can technically also be used to expose knobs for example for non-generic device configuration stuff for example but as far as I can tell no one has really used it yet for this. It does' mean its not possible. The other question is where do we stuff this in userspace and if it really makes sense to start following that practice. For GPIO pin mapping, perhaps given the number of patches I see for it but since its the only thing I see a good use of perhaps its not worth it. The kernel should always use default sensible values but since this is more of database thing it makes sence to start thinking istead of userspace for a better solution. Examples of moving large dbs to userspace could be the preference on USB side to not keep the USB vendor/device IDs names in the kernel, and also the regulatory database stuff. > or do other areas of linux keep some > data in userspace? I gave a few examples, not sure what else the kernel keeps in userspace for data which is generic like that. Moving PCI device vendor/device names might be good example. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
