public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: "Oliver Endriss" <o.endriss@gmx.de>,
	"\"Sébastien RAILLARD (COEXSI)\"" <sr@coexsi.fr>
Subject: Re: [DVB] Octopus driver status
Date: Fri, 24 Jun 2011 08:57:16 -0300	[thread overview]
Message-ID: <4E047B9C.1010308@redhat.com> (raw)
In-Reply-To: <201106241151.34019@orion.escape-edv.de>

Em 24-06-2011 06:51, Oliver Endriss escreveu:
> Hi,
> 
> On Thursday 23 June 2011 23:31:08 Sébastien RAILLARD wrote:
>> Dear all,
>>
>> I'm looking at the Octopus DVB cards system from Digital Devices for a while
>> as their system seems to be very interesting 
>>
>> Here is link with their products:
>> http://shop.digital-devices.de/epages/62357162.sf/en_GB/?ObjectPath=/Shops/6
>> 2357162/Categories
>>
>> The good points I have found:
>>
>> * They support most of the common DVB standards: DVB-C, DVB-T, DVB-S and
>> DVB-S2
>> * They are moderately priced
>> * There is a CAM support with a CI adapter for unscrambling channels
>> * They are using the now de-facto standard PCI-Express bus
>> * The new Octopus system is using a LATTICE PCI-Express bridge that seems to
>> be more future proof than the previous bridge Micronas APB7202A
>> * They seem to be well engineered ("Designed and manufactured in Germany" as
>> they say!)
>>
>> And now the doubts :
>>
>> * The DVB-C/T frontend driver is specific to this system and is very new, so
>> as Devin said one week ago, it's maybe not yet production ready
>> * The way the CAM is supported break all the existing userland DVB
>> applications (gnutv, mumudvb, vlc, etc.)
>> * There isn't so much information about the Digital Devices company and
>> their products roadmap (at least in English)
>>
>> So, my two very simple questions to the developers who worked on the drivers
>> (I think Oliver and Ralph did) and know the product:
>> * How you feel the future about the Octopus driver?
> 
> The drivers work fine. I am not aware of any problems.
> 
> All Digital Devices cards and tuner variants are supported by the driver
> http://linuxtv.org/hg/~endriss/media_build_experimental
> 
> ddbridge (Lattice bridge):
> - Octopus (all variants)
> - cineS2 v6
> - DuoFlex S2 (stv0900 + stv6110 + lnbp21)
> - DuoFlex C/T (Micronas DRXK + NXP TDA18271C2)
> 
> ngene bridge:
> - cineS2 (v4,v5), Satix S2 Dual
> - PCIe bridge, mini PCIe bridge
> - DuoFlex S2 (stv0900 + stv6110 + lnbp21)
> - DuoFlex C/T (Micronas DRXK + NXP TDA18271C2)
> 
> For a German description, see
> http://www.vdr-portal.de/board16-video-disk-recorder/board85-hdtv-dvb-s2/105803-aktuelle-treiber-für-octopus-ddbridge-cines2-ngene-ddbridge-duoflex-s2-duoflex-ct-sowie-tt-s2-6400
> 
> From an operational point of view, the driver is ready for the kernel.
> Unfortunately I did not have the time yet to clean up the coding-style.
> There are thousands of coding-style issues waiting to be fixed...

Hi Oliver,

If it is ok for you, I have here a few devices with DRXK that I'm seeking for
some time to work with. I'll probably have some time this weekend for them,
so I can do the CodingStyle cleanups, if it is ok for you.

Cheers,
Mauro.

  parent reply	other threads:[~2011-06-24 11:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23 21:31 [DVB] Octopus driver status Sébastien RAILLARD (COEXSI)
2011-06-24  9:51 ` Oliver Endriss
2011-06-24 11:18   ` Sébastien RAILLARD (COEXSI)
2011-06-24 11:57   ` Mauro Carvalho Chehab [this message]
2011-06-24 12:46     ` Simon Liddicott
     [not found]     ` <BANLkTinzBGMxwd7AmxPhG3Q1pCx0EsUxvA@mail.gmail.com>
2011-06-24 13:35       ` Mauro Carvalho Chehab
2011-06-25  0:37       ` Oliver Endriss
2011-06-25  0:02     ` Oliver Endriss
2011-07-29 14:52   ` Rune Evjen
2011-07-30 14:25     ` Cine CT V6 (was: Re: [DVB] Octopus driver status) Oliver Endriss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E047B9C.1010308@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=o.endriss@gmx.de \
    --cc=sr@coexsi.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox