Elgato Eye TV Deluxe V2 supported?

Elgato Eye TV Deluxe V2 supported?

[Another Sillyname]

I have an Elgato Eye TV V2 USB device  USB ID 0fd9:002c which reading here....

https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h

Looks like it should be supported (it looks like Devin wrote some of
the code?)......it gets recognised in dmesg and indeed lsusb sees it,
but no firmware is loaded (I have the required as102 files in
/lib/firmware) and in effect it never 'initialises'.

Has something broken since kernel 2.6 (I'm currently running 3.13.10)
or did it never work?

Googling around pops up a load of contradictory information whether it
works or not.

lsusb gives me this...

lsusb -v -d 0fd9:002c

Bus 002 Device 004: ID 0fd9:002c Elgato Systems GmbH EyeTV DTT Deluxe v2
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           0x0fd9 Elgato Systems GmbH
  idProduct          0x002c EyeTV DTT Deluxe v2
  bcdDevice            1.00
  iManufacturer           1 Elgato
  iProduct                2 EyeTV DTT Dlx
  iSerial                 3 0000xxxxxxxxxxxx
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              300mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
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:     0x0000
  (Bus Powered)



lsusb ends



Any ideas?

Thanks in advance.

Tony

Re: Elgato Eye TV Deluxe V2 supported?

[Devin Heitmueller]

On Fri, Apr 25, 2014 at 2:31 PM, Another Sillyname
<anothersname@googlemail.com> wrote:
> I have an Elgato Eye TV V2 USB device  USB ID 0fd9:002c which reading here....
>
> https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h
>
> Looks like it should be supported (it looks like Devin wrote some of
> the code?)......it gets recognised in dmesg and indeed lsusb sees it,
> but no firmware is loaded (I have the required as102 files in
> /lib/firmware) and in effect it never 'initialises'.

Hi Tony,

Sorry, I saw your email yesterday but forgot to reply.  The issue is
that the as102 is still in "staging", so it won't appear in mainline
kernels by default.  You would need to install the media_build tree,
run "make menuconfig", enable "staging drivers" and then enable the
"as102" bridge.

The messages you are seeing in dmesg and lsusb are just the kernel
finding the hardware at a USB level - these messages will appear
whether there is a driver or not for the actual device.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Elgato Eye TV Deluxe V2 supported?

[Another Sillyname]

Thanks Devin

Is the as102 tree ever likely to go mainline?

Regards

Tony

On 25 April 2014 19:40, Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
> On Fri, Apr 25, 2014 at 2:31 PM, Another Sillyname
> <anothersname@googlemail.com> wrote:
>> I have an Elgato Eye TV V2 USB device  USB ID 0fd9:002c which reading here....
>>
>> https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h
>>
>> Looks like it should be supported (it looks like Devin wrote some of
>> the code?)......it gets recognised in dmesg and indeed lsusb sees it,
>> but no firmware is loaded (I have the required as102 files in
>> /lib/firmware) and in effect it never 'initialises'.
>
> Hi Tony,
>
> Sorry, I saw your email yesterday but forgot to reply.  The issue is
> that the as102 is still in "staging", so it won't appear in mainline
> kernels by default.  You would need to install the media_build tree,
> run "make menuconfig", enable "staging drivers" and then enable the
> "as102" bridge.
>
> The messages you are seeing in dmesg and lsusb are just the kernel
> finding the hardware at a USB level - these messages will appear
> whether there is a driver or not for the actual device.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com

Re: Elgato Eye TV Deluxe V2 supported?

[Devin Heitmueller]

> Is the as102 tree ever likely to go mainline?

The only reason it's in staging is because it doesn't meet the coding
standards (i.e. whitespace, variable naming, etc).  Somebody needs to
come along and expend the energy to satisfy the whitespace gods.

Seems like a fantastically stupid reason to keep a working driver out
of the mainline, but that's just my opinion.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Elgato Eye TV Deluxe V2 supported?

[Another Sillyname]

OK, I'm not a coder these days but I'll look and see if I can work it out.

Regards and have a good weekend.

Tony

On 25 April 2014 19:54, Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
>> Is the as102 tree ever likely to go mainline?
>
> The only reason it's in staging is because it doesn't meet the coding
> standards (i.e. whitespace, variable naming, etc).  Somebody needs to
> come along and expend the energy to satisfy the whitespace gods.
>
> Seems like a fantastically stupid reason to keep a working driver out
> of the mainline, but that's just my opinion.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com

Re: Elgato Eye TV Deluxe V2 supported?

[Another Sillyname]

OK, I realise I should be able to work this out....but I'm stuck and
no matter how much I read I've developed a mental block (think of it
as the computing version of writers block).

I use Fedora as my primary OS, currently Fedora 20 latest kernel 3.13

I need to keep using this kernel as I use SELinux for a couple of
things on my server and compiling a vanilla kernel and patching
SELinux in is just way too messy........

As the V4L-DVB Media_Tree is NOT included in the kernel-devel version
of the Fedora kernel it requires a complete kernel compile to download
the required media tree, however I can't then get the V4L-DVB media
tree from git to patch against the Fedora (uncompiled) kernel prior to
compilation, I've installed all the tools required (I have built a few
kernels before when I needed to) but I've just hit a mental wall......

Help!!



On 25 April 2014 20:06, Another Sillyname <anothersname@googlemail.com> wrote:
> OK, I'm not a coder these days but I'll look and see if I can work it out.
>
> Regards and have a good weekend.
>
> Tony
>
> On 25 April 2014 19:54, Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
>>> Is the as102 tree ever likely to go mainline?
>>
>> The only reason it's in staging is because it doesn't meet the coding
>> standards (i.e. whitespace, variable naming, etc).  Somebody needs to
>> come along and expend the energy to satisfy the whitespace gods.
>>
>> Seems like a fantastically stupid reason to keep a working driver out
>> of the mainline, but that's just my opinion.
>>
>> Devin
>>
>> --
>> Devin J. Heitmueller - Kernel Labs
>> http://www.kernellabs.com

Re: Elgato Eye TV Deluxe V2 supported?

[Another Sillyname]

I realise this is from over a year ago but I ended up putting it to
one side till the kernel 'caught up' as it were.

Looking at github/torvalds/linux/tree/master/drivers/media/dvb-frontends
it looks like the as102 support is now in mainline and indeed looking
at staging there's no reference at all to any as102 devices.

I've just installed FC22 Kernel 4-1-10-200 x86_64 onto a box and
installed the required firmware files into /lib/firmware in the hope
the device would now work....unfortunately plugging it in gives me
exactly the same as early last year.....no firmware load even though
dmesg sees the device installed.

Am I still stuck with potentially having to compile a custom kernel to
support this device under Fedora (which isn't an option due to SELinux
issues it would present elsewhere).

Thanks in advance.

On 2 May 2014 at 14:52, Another Sillyname <anothersname@googlemail.com> wrote:
> OK, I realise I should be able to work this out....but I'm stuck and
> no matter how much I read I've developed a mental block (think of it
> as the computing version of writers block).
>
> I use Fedora as my primary OS, currently Fedora 20 latest kernel 3.13
>
> I need to keep using this kernel as I use SELinux for a couple of
> things on my server and compiling a vanilla kernel and patching
> SELinux in is just way too messy........
>
> As the V4L-DVB Media_Tree is NOT included in the kernel-devel version
> of the Fedora kernel it requires a complete kernel compile to download
> the required media tree, however I can't then get the V4L-DVB media
> tree from git to patch against the Fedora (uncompiled) kernel prior to
> compilation, I've installed all the tools required (I have built a few
> kernels before when I needed to) but I've just hit a mental wall......
>
> Help!!
>
>
>
> On 25 April 2014 20:06, Another Sillyname <anothersname@googlemail.com> wrote:
>> OK, I'm not a coder these days but I'll look and see if I can work it out.
>>
>> Regards and have a good weekend.
>>
>> Tony
>>
>> On 25 April 2014 19:54, Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
>>>> Is the as102 tree ever likely to go mainline?
>>>
>>> The only reason it's in staging is because it doesn't meet the coding
>>> standards (i.e. whitespace, variable naming, etc).  Somebody needs to
>>> come along and expend the energy to satisfy the whitespace gods.
>>>
>>> Seems like a fantastically stupid reason to keep a working driver out
>>> of the mainline, but that's just my opinion.
>>>
>>> Devin
>>>
>>> --
>>> Devin J. Heitmueller - Kernel Labs
>>> http://www.kernellabs.com