Messages in this thread | | | Subject | Re: [PATCH] serio.c: dynamically control serio ports bindings via procfs (Was: [RFC/RFT] Raw access to serio ports) | From | Sau Dan Lee <> | Date | 03 Jun 2004 09:47:19 +0200 |
| |
>>>>> "Dmitry" == Dmitry Torokhov <dtor_core@ameritech.net> writes:
>> The info are binary (shown in 0x???? notation). Each reflects >> directly the binary value of the corresponding 'attribute'. >> >> 1) None of these are arrays. But in the input system, each >> device can be attached to _multiple_ handlers, and each handler >> can handle _multiple_ devices. That's an n-to-n relation.
Dmitry> And when they join together they form a new entity, a new Dmitry> device. And that's input system, not serio.
No. The AT keyboard is still ONE device (cat /proc/bus/input/devices) after loading 'evbug'. It is just connected to two handlers: kbd and evbug. No new device is created just because the AT keyboard device is joined to the evbug handler.
>> 2) I can't find out how to dynamically change the driver of a >> PCI device.
Dmitry> No need really. PCI devices are easily identifiable.
Suppose there are 2 "competing" drivers for one device. I want to switch the device to driver 2 at 23:00, and switch it back to driver 1 at 08:00. How to do that?
>> 3) PCI device<-->handler is a many-to-one relation. The input >> system is many-to-many. >> >> 4) How to display/parse a device<-->handler connection? You >> want to show and accept a pointer value?
Dmitry> Strings are perfectly valid:
Of course. What can't be represented as bit-strings?
Dmitry> $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver Dmitry> acpi-cpufreq Dmitry> $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors Dmitry> powersave userspace performance
Dmitry> It just depends on implementation.
Then, go ahead an implement it. I have no interest in sysfs.
-- Sau Dan LEE 李守敦(Big5) ~{@nJX6X~}(HZ)
E-mail: danlee@informatik.uni-freiburg.de Home page: http://www.informatik.uni-freiburg.de/~danlee
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |