Code: Select all
$ lsusb -v -d 045e:028f
Bus 003 Device 090: ID 045e:028f Microsoft Corp. Xbox360 Wireless Controller
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0         8
  idVendor           0x045e Microsoft Corp.
  idProduct          0x028f Xbox360 Wireless Controller
  bcdDevice            3.62
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           18
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     93 
      bInterfaceProtocol    255 
      iInterface              0 
Note I also had no problems – that I couldn't solve on my own – pairing my DS4/PS4 and adding mouse and keyboard to a custom config.
Edit:
http://answers.microsoft.com/en-us/wind ... be28d58d13PnC kit only sends power to the battery and the battery level to be able to stop the power transfer. it does not do anything more than that.
"Play & Charge" – Who ever came up with this wording and deliberately leaving out USB connectivity for the controller is harming Microsofts customers. m(