On Fri, 7 Dec 2012 04:54:40 +0000 "Zheng, Lv" <lv.zheng@xxxxxxxxx> wrote: > > > > We just need a set of type names for the sysfs node I think > > > > "bluetooth", "ups", "loconet", "serial", "modem", "cir" etc... > > > > > > Is it a good idea to introduce uart_device driver in the kernel to fill a new > > 'ldisc' member in the uart_device or to load ldisc by default for the > > corresponding tty_port? > > > > No but it can provide information to help user space. In many cases the > > decision isn't about a line discipline but about automatically setting permissions > > or linking ports to the right driver. > > > > The hints need to be generic - they can come from open firmware, from pci > > identifiers, from ACPI and so on. > > Userspace need to know more than a simple type name to match the driver. It's just an enumeration - and unlike numbers names don't usually collide or need hard management > For example, > Atheros BT will send wrapped HCI packets from their HSU BT adapters, so they need to see "ath3000" rather than "bluetooth" to load a kernel hci protocol module for the device. Fine so we could use "bluetooth/atheros" or similar. Easily dealt with Alan -- 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
