Jump to content

userus1

Members
  • Posts

    9
  • Joined

  • Last visited

userus1's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. probably not, at leat with the flirch rev. i own
  2. @Nobuddy0816 can you post "lsusb -v" output of your flirc. maybe there are different revisions
  3. i tried it several times on my zbox ad 02 and another pc with flirc keyboard profile without success :-(
  4. Here the lsusb -v output of a in BIOS and Bootloader useable remote (HAMA MCE): lsusb -s 002:002 -v --- Bus 002 Device 002: ID 05a4:9881 Ortek Technology, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x05a4 Ortek Technology, Inc. idProduct 0x9881 bcdDevice 1.10 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 63 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 208 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0005 1x 5 bytes bInterval 10 Device Status: 0x0000 (Bus Powered)
  5. do you have HID's "boot protocol" implemented? Do not have flirc device here to check HID "Sub Class" and "Protocol" parameters. from wiki (http://en.wikipedia.org/wiki/Human_interface_device) "... HID also defines "boot protocol". In boot protocol, only specific devices are supported with only specific features because fixed data packet formats are used. The HID descriptor is not used in this mode so innovation is limited. However, the benefit is that minimal functionality is still possible on hosts that otherwise would be unable to support HID. The only devices supported in boot protocol are Keyboard — Any of the first 256 key codes ("Usages") defined in the HID Usage Tables, Usage Page 7 can be reported by a keyboard using the boot protocol, but most systems only handle a subset of these keys. Most systems support all 104 keys on the IBM AT-101layout, plus the three extra keys designed for Microsoft Windows 95. Many systems also support additional keys on basic western European 105-, Korean 106-, Brazilian ABNT 107- and Japanese DOS/V 109-key layouts. Buttons, knobs and keys that are not reported on Usage Page 7 are not available. For example, a particular US keyboard's QWERTY keys will function but the Calculator and Logoff keys will not because they are defined on Usage Page 12 and cannot be reported in boot protocol. Mouse — Only the X-axis, Y-axis, and the first 3 buttons will be available. Any additional features on the mouse will not function. One common usage of boot mode is during the first moments of a computer's boot up sequence. Directly configuring a computer's BIOS is often done using only boot mode. Sometimes a message will appear informing the user that the device has installed the correct driver and is now usable." http://www.usb.org/developers/devclass_docs/HID1_11.pdf Page 75 F.5 Keyboard: Using the Keyboard Boot Protocol Edit: Device descriptor of working keyboard bios mode: bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard Device descriptor of flirc non working bios mode: bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 1 Keyboard
  6. can some of devs take a look at this. please!
  7. yes e.g. grub is working with usb keyboards. i'm still looking for working harmony ir keyboard profile.
  8. hi, i'm using grub to choose between Windows and Openelec. If needed to switch it is always neccessary to use a keyboard. Isn't it possible to get flirc working already at this stage with some ir kb profile so the selection can be made using remote.
×
×
  • Create New...