Re: wireless keyboard with built in touchpad

From: Brian K. White (brian_at_aljex.com)
Date: 07/06/05

  • Next message: Boris Popov: "Re: cat: stdout: No space left on device"
    To: <freebsd-usb@freebsd.org>, <freebsd-current@freebsd.org>
    Date: Wed, 6 Jul 2005 03:35:29 -0400
    
    

    ----- Original Message -----
    From: "Brian K. White" <brian@aljex.com>
    To: <freebsd-usb@freebsd.org>; <freebsd-current@freebsd.org>
    Sent: Saturday, July 02, 2005 8:33 PM
    Subject: wireless keyboard with built in touchpad

    >I have a VGP-WKB1 Sony Vaio usb, 2.4gz rf wireless, keyboard with built-in
    >touch pad and seperate wireless mouse.
    >
    > Gizmodo article
    > http://www.gizmodo.com/gadgets/peripherals/input/vaio-vgpwkb1-wireless-keyboard-with-touchpad-036744.php
    >
    > Sony product page
    > http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_DisplayProductInformation-Start?ProductSKU=VGPWKB1&CategoryName=hid_pr_p_20_per_ecoupon_all&DCMP=CNET_DF&HQS=NBA_VGPWKB1
    >
    > better pictures on this japanese page:
    > http://www.watch.impress.co.jp/akiba/hotline/20050319/etc_vgpwkb1.html
    >
    [...]
    > Like all the others I tried, the keyboard part of this works fine on
    > 5.4-release (what thinbsd is built on)
    > and the mouse is unrecognized.
    > Ordinary usb mice work fine, including when indirectly connected via hubs.
    > I have one slim wired usb keyoard which has a built in 2 port hub and a
    > usb mouse works fine plugged into it.
    [...]
    > Who can I bribe to get the mouse working ?
    > Can I buy one of these and give it to someone (as in it's yours forever)
    > in return for updating the mouse detection in usbd or in the kernel? or
    > even just figuring out whatever cheap hack would allow it to work like
    > maybe just commenting uhid out of the kernel config like you have to do
    > for apcupsd?
    >
    > dmesg on 5.4-release shows this near the end:
    >
    > ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0
    > uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0
    >
    > I'm also willing to do the usual testing and reporting myself according to
    > someones direction of course but I really want this so I don't mind making
    > it worth someones while.
    > It's a really sweet unit.

    More info:
    It partially works on Linux.
    Xandros Desktop 3 autodetects the mouse (linux 2.6.9 / xorg 6.7.0)
    The pointer works but not the buttons.
    Even xev doesn't show anything at all when I move the pointer into the xev
    window and press the buttons.
    Tapping in the touchpad area doesn't produce a button-press either.
    But the pointer follows your finger just fine.

    dmesg:
    [...]
    uhci_hcd 0000:00:11.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
    Controller
    uhci_hcd 0000:00:11.2: irq 12, io base 0000d400
    uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
    [...]
    usbcore: registered new driver hiddev
    input: USB HID v1.10 Keyboard [Sony RF Receiver] on usb-0000:00:11.2-1
    input,hiddev0: USB HID v1.10 Mouse [Sony RF Receiver] on usb-0000:00:11.2-1
    usbcore: registered new driver hiddev
    drivers/usb/input/hid-core.c: v2.0:USB HID core driver

    /var/log/Xorg.0.log:
    [...]
    (**) Option "Protocol" "IMPS/2"
    (**) mouse.usb: Device: "/dev/input/mice"
    (**) mouse.usb: Protocol: "IMPS/2"
    (**) Option "CorePointer"
    (**) mouse.usb: Core Pointer
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Emulate3Buttons" "YES"
    (**) mouse.usb: Emulate3Buttons, Emulate3Timeout: 50
    (**) Option "ZAxisMapping" "4 5"
    (**) mouse.usb: ZAxisMapping: buttons 4 and 5
    (**) mouse.usb: Buttons: 5
    (II) XINPUT: Adding extended input device "mouse.usb" (type: MOUSE)
    (II) mouse.usb: ps2EnableDataReporting: succeeded
    [...]

    In windows it works immediately without any special drivers too.

    The linux & windows experience suggests no special driver needs to be
    written, merely get an existing driver attached to the device.

    How do I go about that?

    When linux is running and working, what can I look at in order to find
    details that freebsd needs? and then where do I use them on freebsd?
    Something from /proc? translated into a patch somewhere in the freebsd
    kernel?

    I'll try a newer linux and newer xorg than above presently.

    The offer still stands, no one has claimed their $150 wireless keyboard.
    Thanks

    Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
    +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
    filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Boris Popov: "Re: cat: stdout: No space left on device"