Hi, On Sat, Oct 10, 2009 at 1:29 AM, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote: > Hi Joonyoung, > > On Thu, Oct 08, 2009 at 11:11:23AM +0900, Joonyoung Shim wrote: >> Currently, the input device number is decided by order of driver probe. >> But we need the specified input device number regardless of order of >> driver probe because the platform or the middleware tends to access >> using fixed device node of the input devices. >> >> This patch supports to use the specified input device number when the >> input device is registered. If the input device number bigger than zero >> is registered before by other input device, returns error. >> > > No, I don't think this is a good solution. You can have persistent > device nodes without hadrcoding it into the driver. See how UDEV creates > 'by-id' and 'by-path' links. > Please let me know how to use udev at input device. At our system, input0: h/w keypad input1: gpio key input2: touchscreen input3: jack or others but in previous system, we always set the touchscreen as input1. Right we can modify it but it's not easy. With this patch we always set touchscreen as input1. How can we do this? FYI: when launch the X, we set the tsdevice as input1 and keyboard as input0. Thank you, Kyungmin Park -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
