Extensa 5220

Thu Nov 29 00:42:55 PST 2007

Am Mittwoch, den 28.11.2007, 17:40 +0000 schrieb Carlos Corbacho:
> On Tuesday 11 September 2007 16:14:57 Thomas Ilnseher wrote:
> > I got this new laptop, with a lot of extra buttons on it.
> > I tried to write the fdi file according to the info on: 
> > http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-report.html
> > 
> > but it doesn't work. Any help is appreciated.
> 
> Can you elaborate a bit further on "doesn't work"?
I patched the file on my notebook, fiddled in hal-0.5.10rc-something,
rebooted, pressed these keys, and looked at dmesg. Still, those 'use
setkeycode' messages appeared. Also, by doing 'lshal | grep key', I
wasn't able to see any input.keymap.data values.

A lot of other things ceased working also, so I decided to go back to
hal-0.5.9 from my distro. It might be the case that I did something
wrong when installing hal-0.5.10, though.

I recently noticed hal-0.5.10 appearing in portage, albeit with a hard
mask. once this hard mask disappears, I'll give it a try.
> 
> On Wednesday 28 November 2007 15:59:43 Danny Kukawka wrote:
> > @Carlos: Could you verify this patch? You are more familiar with the Acer 
> > machines.
> 
> Here goes.
> 
> On Tuesday 11 September 2007 16:14:57 Thomas Ilnseher wrote:
> > diff --git a/fdi/information/10freedesktop/30-keymap-acer.fdi b/fdi/information/10freedesktop/30-keymap-acer.fdi
> > index bcce56d..c59bc8e 100644
> > --- a/fdi/information/10freedesktop/30-keymap-acer.fdi
> > +++ b/fdi/information/10freedesktop/30-keymap-acer.fdi
> > @@ -7,6 +7,29 @@
> >      <match key="@input.originating_device:info.linux.driver" string="atkbd">
> >  
> >        <match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" prefix="Acer">
> > +        <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" prefix="Extensa">
> 
> This is wrong - there is now an Extensa section in 30-keymap-acer.fdi
> (between 'Aspire' and 'Ferrari' - the list is alphabetically ordered);
> please add your 5220 entry to that section.
will do
> 
> > +	  <!-- Extensa 5220; possibly also 5210, 5620 -->
> 
> Add them (and the 5610) - all these laptops will have the same base unit,
> keyboard controller, etc.
Ok. I know that the 5210 has a different chipset than the 5220 (i915GM
derivative vs. GL960 = GM965 derivative). I'm more sure about that 5620.
> 
> > +	  <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" contains="5220">
> 
> s/contains/contains_outof/
> 
> > +	    <append key="input.keymap.data" type="strlist">e055:wlan</append> <!-- Wifi Switch, first press -->
> > +            <append key="input.keymap.data" type="strlist">e056:wlan</append> <!-- Wifi Switch, second press -->
> > +            <append key="input.keymap.data" type="strlist">e054:bluetooth</append> <!-- bluetooth Switch, second press -->
> 
> This is odd - I would usually expect bluetooth to be e057 & e058 - can you
> confirm this is really not the case?
Yes. Bluetooth is e054. Also note that I don't have a bluetooth module.
When I "press" that bluetooth switch, only e054 appears in dmesg, which
is a different behavior than the wlan "button" has. 
> 
> (Even if your laptop doesn't have bluetooth, others fitted with it would also
> produce a second scancode for going from bluetooth on to off, so you would
> need to add another entry for that - if the bluetooth really is e054, then
> I expect this other scancode to be e053).
> 
> > +            <append key="input.keymap.data" type="strlist">e074:prog1</append> <!-- e key, upper left side -->
> 
> This scancode is fine - however, please just copy and paste the relevant
> comment from the other entries to keep the Acer keymaps consistent, rather
> than rewriting them yourself (that way we can try and maintain consistency
> across the various laptop entries).
> 
> > +            <append key="input.keymap.data" type="strlist">e06e:screenlock</append> <!-- screenlock key, second press -->
> > +            <append key="input.keymap.data" type="strlist">e075:camera</append> <!-- camaera key, second press -->
> > +            <append key="input.keymap.data" type="strlist">e079:refresh</append> <!-- Possibly reload key ??? -->
> 
> These three keycodes I don't recognise, but your laptop does appear to have
> new keys.
> 
> The manual though:
> ftp://ftp.work.acer-euro.com/notebook/extensa_5220/manual/EX_5620_5610_5220_5210_User_Guide_Eng.pdf
wow, there's a manual now! back when I wrote that patch, i couldn't find
a manual. (Yes, i looked in that directory on exactly that ftp server.)
> 
> lists these new keys as
> 
> Lock = Windows Lock function
> Presentation = Minimise all windows
> Sync = Launch NTI shadow (some sort of backup application?)
> 
> I presume the 'lock' key maps to e06e?
> 
> And what happens with these keys on the 'first press'? Do they already
> generate a keycode (and which one), or do they produce a different
> scancode?
> 
> > +            <append key="input.keymap.data" type="strlist">e073:prog2</append> <!-- "P" key ??? -->
> 
> This scancode is fine - however, please just copy and paste the relevant
> comment from the other entries to keep the Acer keymaps consistent, rather
> than rewriting them yourself (that way we can try and maintain consistency
> across the various laptop entries).
yes will do. to explain the problem: i made this fdi, without looking in
that acer.fdi file first. than i merged it, and wanted to keep it
consistent with keycodes from the other acer entries.
> 
> > +            <append key="input.keymap.data" type="strlist">e033:f15</append> <!-- FIXME !!This is a dedicated "euro" key -->
> > +            <append key="input.keymap.data" type="strlist">e034:f14</append> <!-- FIXME !!This is a dedicated "$" key -->
> 
> There are proper Dollar and Euro keycodes - please use them.
> 
> > +            <append key="input.keymap.data" type="strlist">e078:fn</append> <!-- fn key -->
> > +            <append key="input.keymap.data" type="strlist">e025:help</append> <!-- fn+f1 key -->
> > +            <append key="input.keymap.data" type="strlist">e026:setup</append> <!-- fn+f2 key -->
> > +            <append key="input.keymap.data" type="strlist">e027:battery</append> <!-- fn+f3 key -->
> > +            <append key="input.keymap.data" type="strlist">e029:switchvideomode</append> <!-- fn+f5 key -->
> > +            <append key="input.keymap.data" type="strlist">e071:f22</append> <!-- fn+f7 key, first press -->
> > +            <append key="input.keymap.data" type="strlist">e072:f22</append> <!-- fn+f7 key, 2nd press -->
> 
> These 7 scancodes are fine - however, please just copy and paste the relevant
> comments from the other entries to keep the Acer keymaps consistent, rather
> than rewriting them yourself (that way we can try and maintain consistency
> across the various laptop entries).
> 
> Also, please reorder _all_ these entries - they should be sorted by scancode.
> 
> And check to see if any of your brightness keys produce scancodes (some do,
> some don't).
> 
> > +            <append key="info.capabilities" type="strlist">input.keymap</append>
> > +	  </match>
> > +	</match>
> >          <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" prefix="Aspire">
> >            <!-- Aspire 1360 and Aspire 1520 are identical -->
> >            <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" contains_outof="1360;1520">
> 
> -Carlos
-- 
Thomas Ilnseher <ilnseher at eit.uni-kl.de>