Skip to contentSkip to conversation

How to add DVB-S2 support to firedtv?

DISCUSSION Stefan Richter 3 participants 3 messages Feb 14, 2010 – Feb 26, 2010 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

Hi all,

what steps need to be taken to get DVB-S2 support into the firedtv driver? (The status is, as far as I understood: FireDTV S2 and Floppy DTV S2 devices recognize HD channels during channel scan but cannot tune to them. FireDTV C/CI DVB-C boxes however tune and play back HD channels just fine.)

I suppose the frontend needs to be extended for s2api. Was there a respective conversion in another DVB driver that can serve as a good coding example?

Is documentation from Digital Everywhere required regarding the vendor-specific AV/C requests (LNB_CONTROL? TUNE_QPSK2?) or is the current driver code enough to connect the dots?

Is the transport stream different from DVB-C HD streams so that changes to the isochronous I/O part would be required?

Signature · 3 lines
Stefan Richter
-=====-==-=- --=- -===-
http://arcgraph.de/sr/
#1 lore raw

Hi,

Regarding the documentation and code:

Quoted 1 line

From a quick glance, the LNB/QPSK2 code follows the documentation fairly good.

I guess it could do with a deeper check (I could see that at least the FEC switch case does seems to have some invalid values) but I would prefer that this is done by someone that actually has a DVB-S(2) card.

Regards,
Henrik

Quoted 23 lines

Hi all,

what steps need to be taken to get DVB-S2 support into the firedtv driver? (The status is, as far as I understood: FireDTV S2 and Floppy DTV S2 devices recognize HD channels during channel scan but cannot tune to them. FireDTV C/CI DVB-C boxes however tune and play back HD channels just fine.)

I suppose the frontend needs to be extended for s2api. Was there a respective conversion in another DVB driver that can serve as a good coding example?

Is documentation from Digital Everywhere required regarding the vendor-specific AV/C requests (LNB_CONTROL? TUNE_QPSK2?) or is the current driver code enough to connect the dots?

Is the transport stream different from DVB-C HD streams so that changes to the isochronous I/O part would be required?
--
Stefan Richter
-=====-==-=- --=- -===-
http://arcgraph.de/sr/

#2 lore raw

Hi there

I own a FireDTV S2 and I'm willing to invest some time. I poked around in the driver code previously and I might do some coding given that I have access to the required technical information.

As far as I know Digital Everywhere is out of business - does this mean that the NDAs are no longer in effect and that someone could give me the technical documentation required?

Cheerio

Beat

Quoted 34 lines · Henrik Kurelid

Hi,

Regarding the documentation and code:
From a quick glance, the LNB/QPSK2 code follows the documentation fairly good.
I guess it could do with a deeper check (I could see that at least the FEC switch case does seems to have some invalid values) but I would prefer that this is done by someone that actually has a DVB-S(2) card.

Regards,
Henrik

Quoted 23 lines

Hi all,

what steps need to be taken to get DVB-S2 support into the firedtv driver? (The status is, as far as I understood: FireDTV S2 and Floppy DTV S2 devices recognize HD channels during channel scan but cannot tune to them. FireDTV C/CI DVB-C boxes however tune and play back HD channels just fine.)

I suppose the frontend needs to be extended for s2api. Was there a respective conversion in another DVB driver that can serve as a good coding example?

Is documentation from Digital Everywhere required regarding the vendor-specific AV/C requests (LNB_CONTROL? TUNE_QPSK2?) or is the current driver code enough to connect the dots?

Is the transport stream different from DVB-C HD streams so that changes to the isochronous I/O part would be required?
--
Stefan Richter
-=====-==-=- --=- -===-
http://arcgraph.de/sr/