0.25.2-81 and atiusb

[jangi]

Not to beat a dead horse... but does anyone have any idea what changed between 81b3 and 81b4 regarding atiusb? See this thread with Pablo:
viewtopic.php?f=1&t=3083

It's been a long time since I've had build system setup but I'm willing to do it again if someone can point me in the right direction.

Thanks,
James

[jangi]

Just want to confirm this is still broken with 0.25.3-82.

[Pablo]

Could you post the difference in remote related messages between 81b3 and 81b4?

In addition, could you post the remote related messaged from 82?

[jangi]

Pablo,

Welcome back! I don't have 81b4 anymore so I'll be comparing 81b3 and 82:

Working in 81b3:

Code: Select all

root@myth1:~ # ls /dev/lirc*
/dev/lirc0

root@myth1:~ # lsmod |grep ati
lirc_atiusb            10088  0
lirc_dev                6559  4 lirc_atiusb

root@myth1:~ # dmesg | grep lirc
lirc_dev: IR Remote Control driver registered, major 252
lirc_atiusb: USB remote driver for LIRC $Revision: 1.88 $
lirc_atiusb: Paul Miller <pmiller9@users.sourceforge.net>
lirc_atiusb 3-1:1.0: lirc_dev: driver lirc_atiusb  registered at minor = 0
lirc_atiusb[2]: X10 Wireless Technology Inc USB Transceiver on usb3:2
usbcore: registered new interface driver lirc_atiusb
input: lircd as /devices/virtual/input/input2
root@myth1:~ #

Broken in 82:

Code: Select all

root@myth1:~ # ls /dev/lirc*
(no files)

root@myth1:~ # dmesg |grep lirc
input: eventlircd as /devices/virtual/input/input4

root@myth1:~ # tail -f /var/log/messages
Dec  7 19:13:02 (none) user.warn kernel: usb 3-1: Weird data, len=5 20 ee 11 d3 2c 00 ...
Dec  7 19:13:02 (none) user.warn kernel: usb 3-1: Weird data, len=5 20 ee 11 d3 2c 00 ...

root@myth1:~ # lsusb -v -s 3:2

Bus 003 Device 002: ID 0bc7:0002 X10 Wireless Technology, Inc. Firecracker Interface (ACPI-compliant)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0bc7 X10 Wireless Technology, Inc.
  idProduct          0x0002 Firecracker Interface (ACPI-compliant)
  bcdDevice            1.00
  iManufacturer           1 X10 Wireless Technology Inc
  iProduct                2 USB Transceiver
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      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
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
Device Status:     0x0000
  (Bus Powered)

root@myth1:~ # lsmod |grep ati
rc_ati_x10               916  0
ati_remote              6050  0
rc_core                 9270  3 rc_ati_x10,ati_remote

The "weird data" messages happen every time a button on the remote is pressed.

Let me know if you need anything else.
Thanks,
James

[Pablo]

Thank you. Looking at these outputs, the most obvious difference is that 81b2 is using the ati_remote driver provided by the kernel whereas 81b3 is using the lirc_atiusb provided by LIRC. 82 has lirc_atiusb.

[jangi]

I noticed that, but I'm seeing ati_remote in version 82, so I'm still stuck on 81b3.

[Pablo]

Oops. While 82 contains lirc_atiusb, it still contains ati_remote. I will remove ati_remote from the next build.