Magellan Linux

Annotation of /trunk/udev/udev-keyboard-force-release.rules.magellan

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1088 - (hide annotations) (download)
Wed Aug 18 02:24:13 2010 UTC (14 years, 2 months ago) by niro
File size: 3342 byte(s)
-updated rules to match udev-161

1 niro 1016 # /etc/udev/rules/95-keyboard-force-release.rules: device naming rules for udev
2 niro 1088 # $Header: /root/magellan-cvs/src/udev/udev-keyboard-force-release.rules.magellan,v 1.2 2010-08-18 02:24:12 niro Exp $
3 niro 1016 #
4     # There are a number of modifiers that are allowed to be used in some
5     # of the different fields. They provide the following subsitutions:
6     # %n - the "kernel number" of the device.
7     # For example, 'sda3' has a "kernel number" of '3'
8     # %k - the kernel name for the device.
9     # %M - the kernel major number for the device
10     # %m - the kernel minor number for the device
11     # %b - the bus id for the device
12     # %c - the string returned by the PROGRAM. (Note, this doesn't work within
13     # the PROGRAM field for the obvious reason.)
14     # %s{filename} - the content of a sysfs attribute.
15     # %% - the '%' char itself.
16     #
17     # Try not to modify this file, if you wish to change things, create a new rule
18     # file that can be run before this one.
19     #
20    
21     # Set model specific atkbd force_release quirk
22     #
23     # Several laptops have hotkeys which don't generate release events,
24     # which can cause problems with software key repeat.
25     # The atkbd driver has a quirk handler for generating synthetic
26     # release events, which can be configured via sysfs since 2.6.32.
27     # Simply add a file with a list of scancodes for your laptop model
28     # in /lib/udev/keymaps, and add a rule here.
29     # If the hotkeys also need a keymap assignment you can copy the
30     # scancodes from the keymap file, otherwise you can run
31     # /lib/udev/keymap -i /dev/input/eventX
32     # on a Linux vt to find out.
33    
34 niro 1088 ACTION=="remove", GOTO="force_release_end"
35 niro 1016 SUBSYSTEM!="serio", GOTO="force_release_end"
36     KERNEL!="serio*", GOTO="force_release_end"
37     DRIVER!="atkbd", GOTO="force_release_end"
38    
39     ENV{DMI_VENDOR}="$attr{[dmi/id]sys_vendor}"
40    
41    
42 niro 1088 ENV{DMI_VENDOR}=="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}=="*E252*|*N120*|*N128*|*N130*|*N140*|*N148/N208*|*N150*|*N150/N210/N220*|*N220*|*N308*|*N310*|*N510*|*NB30*|*NC10/N110*|*ND10*|*Q210/P210*|*R410P*|*R425/R525*|*R428/P428*|*R460*|*R463*|*R468/R418*|*R480/R431/R481*|*R509*|*R518*|*R519/R719*|*R520/R522/R620*|*R528/R728*|*R530/R730*|*R530/R730/P590*|*R560*|*R580*|*R580/R590*|*R59/R60/R61*|*R59P/R60P/R61P*|*R710*|*R720*|*R780/R778*|*SR58P*|*SR700*|*SR70S/SR71S*|*SX22S*|*X118*|*X120*|*X460*", RUN+="keyboard-force-release.sh $devpath samsung-other"
43 niro 1016
44 niro 1088 ENV{DMI_VENDOR}=="Dell Inc.", ATTR{[dmi/id]product_name}=="Studio 1557|Studio 1558", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
45    
46     ENV{DMI_VENDOR}=="FUJITSU SIEMENS", ATTR{[dmi/id]product_name}=="AMILO Si 1848+u", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
47    
48     ENV{DMI_VENDOR}=="FOXCONN", ATTR{[dmi/id]product_name}=="QBOOK", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
49    
50     ENV{DMI_VENDOR}=="MTC", ATTR{[dmi/id]product_version}=="A0", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
51    
52     ENV{DMI_VENDOR}=="PEGATRON CORP.", ATTR{[dmi/id]product_name}=="Spring Peak", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
53    
54     ENV{DMI_VENDOR}=="TOSHIBA", ATTR{[dmi/id]product_name}=="Satellite U300|Satellite Pro U300|Satellite U305", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
55    
56     ENV{DMI_VENDOR}=="Viooo Corporation", ATTR{[dmi/id]product_name}=="PT17", RUN+="keyboard-force-release.sh $devpath common-volume-keys"
57    
58 niro 1016 LABEL="force_release_end"