<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - * glob works wrongly in 60-keyboard.hwdb" href="https://bugs.freedesktop.org/show_bug.cgi?id=88410#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - * glob works wrongly in 60-keyboard.hwdb" href="https://bugs.freedesktop.org/show_bug.cgi?id=88410">bug 88410</a> from <a class="email" href="mailto:maxtram95@gmail.com" title="maxtram95@gmail.com">maxtram95@gmail.com</a> <pre>(In reply to Zbigniew Jedrzejewski-Szmek from <a href="show_bug.cgi?id=88410#c1">comment #1</a>) > It's a question of ordering. Since both the generic MICRO-STAR and the more > specific U100/U90/etc patterns match, which ever gets assigned last wins. I > guess that this is by design, since the documentation does not say anything > about the order. Let's see what Kay thinks. > > @Kay: ^^^ Indeed, I tried to remove that lines from generic rule: KEYBOARD_KEY_f7=brightnessdown # Fn+F4 KEYBOARD_KEY_f8=brightnessup # Fn+F5 And udevadm info /dev/input/event5 shows f7 and f8 as reserved, so *U100* rule works. So asterisk is not a bug. MSI rules rely on order of applying, but it is unspecified. I think the order in which rules are applied has to be specified. Old 95-keymap.rules were applied from top to bottom in order. New 60-keyboard.hwdb is simply generated from 95-keymap.rules. But the ordering is broken now. Maybe, MSI is not the only case where it is important.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>