<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - Improve Surface Pro Type Cover 2 support"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=99079">bug 99079</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">CC</td>
           <td>
                
           </td>
           <td>benjamin.tissoires@gmail.com
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - Improve Surface Pro Type Cover 2 support"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=99079#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - Improve Surface Pro Type Cover 2 support"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=99079">bug 99079</a>
              from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
        <pre>(In reply to defree from <a href="show_bug.cgi?id=99079#c3">comment #3</a>)
<span class="quote">> So this device need some hack for proper support?
> Either a custom initialization procedure or just filtering some packets.
> (Is it reasonable to expect that kind of hack into the kernel? Given the
> huge number of clunky usb devices, it seems one would need a dedicated
> database for handling that).</span >

yes. CC-ing benjamin, he's done work on the type covers before and knows the
current state.

as for tap-to-click and scrolling: the device just looks like a normal mouse
with a scroll wheel. tapping is implemented in the firmware, we don't have
access to it. here too we'd need the kernel to support this properly and expose
it as a touchpad device.

We can put a quickfix in for the F23 though. In libinput's
evdev_pre_configure_model_quirks() put in a call to 

   libevdev_disable_event_code(device->evdev, EV_KEY, KEY_F23);

and see if that has any side-effects. as you noticed, F23 is used for touchpad
disabling, so let's see what happens if we just completely filter this out.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>