On Thursday 21 December 2006 23:10, Bjorn Helgaas wrote: > On Thursday 21 December 2006 20:12, Zhang Rui wrote: > > Then I have an idea about the other ones. We can also convert the PNPids > > reserved in the spec to such kind of strings. > > E.g. "PNP0C0D,PNP0C0C,PNP0C0E" "button" > > "ACPI0003" "ac_adapter" > > "PNP0C0A" "battery" > > I hesitate to hide the PNP IDs altogether. They seem analogous > to PCI vendor/device IDs. We expose the PCI IDs directly and > let user-space map them into human-readable strings. In fact, > the mostly-forgotten lspnp package already has a pnp.ids file > with these mappings. So I vote for keeping the mapping there. I agree with Bjorn that it is a slippery slope for the kernel to try to be human friendly, and that the kernel should just give the raw names and let an application translate them. I think my original point was somewhat mis-interpreted. My point is that when the kernel has _no_ PNPid to use to describe the device node and we have to manufacture a string anyway, that we might as well manufacture a string that a human can read. thanks, -Len - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
