Re: [Line6linux-devel] line6 out of staging

[L. A. G. <agi...@sy...>]

On Wed, Nov 28, 2012 at 08:34:52AM +0100, Stefan Hajnoczi wrote:
> 
> Has the HD 500 ever worked with the driver?  AFAIK support for HD 500
> is incomplete.

I don't know, it's the first time I try it out in Linux. I have the hardware and it
would be awesome to help to add support for HD500 for Linux :)

 
> Please post the output of "lsusb -d 0e41:414d -v" while the device is
> attached.  This will provide the USB capabilities of the device so we
> can try to find the correct interface, altsetting, and endpoints.

# lsusb -d 0e41:414d -v

Bus 001 Device 010: ID 0e41:414d Line6, Inc. 
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        64
  idVendor           0x0e41 Line6, Inc.
  idProduct          0x414d 
  bcdDevice            0.00
  iManufacturer           1 Line 6
  iProduct                2 POD HD500
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           18
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x40
      (Missing must-be-set bit!)
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              4 User
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

> 
> If you want to play with this yourself, try editing the switch
> statements in driver.c:line6_probe() to use the interface, altsetting,
> and endpoint information from the lsusb output.  This is just
> guesswork, if you want to be sure then you need to capture USB traffic
> from the Line6 Edit software to see how the Windows driver talks to
> the device.

Well, yes, I want to play :) But I have a very limited knowledge of USB kernel (and
ALSA) development. I need to read some kernel documents and try to understand the
code!

So, whare do you recommend me to begin with?

On the other hand, I can begin to submit checkpatch fixes so I get comfortable with
the code.

In the kernel configuration, I didn't activate the debug options because i read in
the list that they were to be obsoleted for general-purpose facilities (usbmon, etc).
Would you recommend to activate those options anyway?


Best regards,
-- 
L. Alberto Giménez
JabberID agi...@ja...
GnuPG key ID 0x3BAABDE1