#10213 HIGH 1.5-sof: Frame key doesn't work on XO-1.5 HS

Zarro Boogs per Child bugtracker at laptop.org
Wed Jul 14 18:18:03 EDT 2010


#10213: Frame key doesn't work on XO-1.5 HS
------------------------------+---------------------------------------------
           Reporter:  wad     |       Owner:  dsd                               
               Type:  defect  |      Status:  new                               
           Priority:  high    |   Milestone:  1.5-software-update               
          Component:  sugar   |     Version:  Development source as of this date
         Resolution:          |    Keywords:                                    
        Next_action:  code    |    Verified:  0                                 
Deployment_affected:          |   Blockedby:                                    
           Blocking:  10229   |  
------------------------------+---------------------------------------------

Comment(by pgf):

 thanks.

 this fills in a gap in my understanding.  the initial default scancode -->
 keycode mapping we see from "getkeycodes" actually comes from that hal
 file.  (/etc/hal/fdi/information/30-keymap-olpc.fdi)

 so i could dispense with the proposed new xkb lines, and the proposed new
 setkeycodes lines, and simply change 4 of the lines in 30-keymap-olpc.fdi
 from:

 {{{
         <append key="input.keymap.data" type="strlist">e043:fn_f9</append>
         <append key="input.keymap.data"
 type="strlist">e044:fn_f10</append>
         <append key="input.keymap.data"
 type="strlist">e057:fn_f11</append>
         <append key="input.keymap.data"
 type="strlist">e058:fn_f12</append>

 }}}
 to:
 {{{
         <append key="input.keymap.data"
 type="strlist">e043:brightnessdown</append>
         <append key="input.keymap.data"
 type="strlist">e044:brightnessup</append>
         <append key="input.keymap.data"
 type="strlist">e057:volumedown</append>
         <append key="input.keymap.data"
 type="strlist">e058:volumeup</append>

 }}}

 then kbdshim would bind to KEY_BRIGHTNESSUP/DOWN and KEY_VOLUMEUP/DOWN
 instead of KEY_F21-KEYF24.  the remaining Fn-Fkeys would continue to be
 inaccessible from X.  (well, at least as inaccessible as they are today.
 i can't seem to get them through xkb.)

 i agree this is a simpler change.  is this sort of what you had in mind?

-- 
Ticket URL: <http://dev.laptop.org/ticket/10213#comment:14>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list