B2C2 FlexCop - Revision history

Js: Reverted edits by MergeMac (Talk) to last version by Jimbley

2010-09-28T17:22:05Z

Reverted edits by MergeMac (Talk) to last version by Jimbley

← Older revision		Revision as of 17:22, 28 September 2010
Line 14:		Line 14:
	* [http://www.b2c2.com/ B2C2 Inc.]		* [http://www.b2c2.com/ B2C2 Inc.]
	* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]		* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]
-	* [http://www.mac-how.net mac how to]

	[[Category:Chipsets]]		[[Category:Chipsets]]

MergeMac: /* External Links */

2010-09-28T10:28:14Z

External Links

← Older revision		Revision as of 10:28, 28 September 2010
Line 14:		Line 14:
	* [http://www.b2c2.com/ B2C2 Inc.]		* [http://www.b2c2.com/ B2C2 Inc.]
	* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]		* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]
		+	* [http://www.mac-how.net mac how to]

	[[Category:Chipsets]]		[[Category:Chipsets]]

Jimbley: Added category: Chipsets

2009-05-04T02:14:44Z

Added category: Chipsets

← Older revision		Revision as of 02:14, 4 May 2009
Line 15:		Line 15:
	* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]		* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]

-	[[Category:~~Hardware]]~~	+	[[Category:Chipsets]]
-	~~[[Category:Hardware~~]]	+

CityK: correct category -- its not a decoder, just a bridge

2008-12-06T17:35:05Z

correct category -- its not a decoder, just a bridge

← Older revision		Revision as of 17:35, 6 December 2008
Line 15:		Line 15:
	* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]		* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]

-	[[Category:~~Decoder~~]]	+	[[Category:Hardware]]
	[[Category:Hardware]]		[[Category:Hardware]]

CityK: fixed link

2008-01-06T22:14:44Z

fixed link

← Older revision		Revision as of 22:14, 6 January 2008
Line 1:		Line 1:
-	The FlexCop is a quite interesting and well-designed [[PCI interface chipsets\|PCI interface chipset]] by [[B2C2 Inc.]]. The FlexCop/FlexCop2 family is comprised of the FlexCopII, FlexCopIIb and FlexCopIII variants. It is worthwhile to point out that the FlexCop ASICs have no analog input handling capabilities, but rather are designed strictly for digital receiver applications. These chips contain a flexible [[~~MPEG2~~ Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus.	+	The FlexCop is a quite interesting and well-designed [[PCI interface chipsets\|PCI interface chipset]] by [[B2C2 Inc.]]. The FlexCop/FlexCop2 family is comprised of the FlexCopII, FlexCopIIb and FlexCopIII variants. It is worthwhile to point out that the FlexCop ASICs have no analog input handling capabilities, but rather are designed strictly for digital receiver applications. These chips contain a flexible [[MPEG-2 Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus.

	PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.		PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.

CityK: fixed link

2008-01-05T16:26:43Z

fixed link

← Older revision		Revision as of 16:26, 5 January 2008
Line 3:		Line 3:
	PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.		PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.

-	As far we know the FlexCop chipsets contain a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[~~i2c~~ Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.	+	As far we know the FlexCop chipsets contain a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[I²C Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.

	The Linux driver works quite well and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.		The Linux driver works quite well and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.

CityK: fixed link

2007-12-16T20:35:18Z

fixed link

← Older revision		Revision as of 20:35, 16 December 2007
Line 1:		Line 1:
-	The FlexCop is a quite interesting and well-designed [[PCI interface chipset]] by [[B2C2 Inc.]]. The FlexCop/FlexCop2 family is comprised of the FlexCopII, FlexCopIIb and FlexCopIII variants. It is worthwhile to point out that the FlexCop ASICs have no analog input handling capabilities, but rather are designed strictly for digital receiver applications. These chips contain a flexible [[MPEG2 Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus.	+	The FlexCop is a quite interesting and well-designed [[PCI interface chipsets\|PCI interface chipset]] by [[B2C2 Inc.]]. The FlexCop/FlexCop2 family is comprised of the FlexCopII, FlexCopIIb and FlexCopIII variants. It is worthwhile to point out that the FlexCop ASICs have no analog input handling capabilities, but rather are designed strictly for digital receiver applications. These chips contain a flexible [[MPEG2 Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus.

	PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.		PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.

CityK: correct goodly grammer :P

2007-02-17T18:37:28Z

correct goodly grammer :P

← Older revision		Revision as of 18:37, 17 February 2007
Line 5:		Line 5:
	As far we know the FlexCop chipsets contain a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[i2c Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.		As far we know the FlexCop chipsets contain a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[i2c Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.

-	The Linux driver works quite ~~good~~ and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.	+	The Linux driver works quite well and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.

	The FlexCop family of chips can be found employed in several [[TechniSat]] DVB cards and USB devices.		The FlexCop family of chips can be found employed in several [[TechniSat]] DVB cards and USB devices.

CityK at 18:36, 17 February 2007

2007-02-17T18:36:33Z

← Older revision		Revision as of 18:36, 17 February 2007
Line 3:		Line 3:
	PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.		PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.

-	As far we know the FlexCop chipsets ~~contains~~ a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[i2c Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.	+	As far we know the FlexCop chipsets contain a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[i2c Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.

	The Linux driver works quite good and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.		The Linux driver works quite good and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.

CityK: no analog capablilities, external link

2007-02-17T18:35:13Z

no analog capablilities, external link

← Older revision		Revision as of 18:35, 17 February 2007
Line 1:		Line 1:
-	~~These are~~ quite interesting and well-designed [[PCI interface chipset]] by [[B2C2 Inc.]]. ~~They~~ contain a flexible [[MPEG2 Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus.	+	The FlexCop is a quite interesting and well-designed [[PCI interface chipset]] by [[B2C2 Inc.]]. The FlexCop/FlexCop2 family is comprised of the FlexCopII, FlexCopIIb and FlexCopIII variants. It is worthwhile to point out that the FlexCop ASICs have no analog input handling capabilities, but rather are designed strictly for digital receiver applications. These chips contain a flexible [[MPEG2 Transport Stream]] interface with hardware [[PID]] filters which, if delivery of a complete Transport Stream payload is not desired, allow for the removal of unwanted packets from the stream, and thus reduce the bandwidth utilized when transferred across the host system bus.

	PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.		PID filtering is most useful in scenarios such as when recording one HD program (typically 14-17Mbps) from a 256-QAM stream (having a demodulated payload ~38.8Mbps), or when recording low resolution program streams from any given Transport Stream. In other scenarios, such as when recording an HD stream encoded with 8-VSB (~19.4Mbps), PID filtering is not as impactive in terms of the relative bandwidth savings, since the saved program usually constitutes most of the original Tranport Stream's bandwidth to begin with. The hardware filters impact may also be limited if in the case of collecting EIT data.

-	As far we know the ~~chipset~~ contains a [[Smartcard interface]] and a [[CSA Descrambler]]. As it tends to display some quirks in the [[i2c Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.	+	As far we know the FlexCop chipsets contains a [[Smartcard interface]] and a [[CSA Descrambler]]. As the FlexCop tends to display some quirks in the [[i2c Protocol]] interface, the PCI bridge driver thus needs to know which clients are allowed on the bus in order to avoid lockups.

-	The Linux driver works quite good and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.	+	The Linux driver works quite good and has no known drawbacks. Support for the IC's [[Smartcard Interface]] and [[CSA Descrambler]] features, however, are missing.

-	The FlexCop~~/FlexCop2~~ family ~~is comprised~~ of ~~the FlexCopII, FlexCopIIb~~ and ~~FlexCopIII variants~~.	+	The FlexCop family of chips can be found employed in several [[TechniSat]] DVB cards and USB devices.

-	~~These chips are employed in several [[TechniSat]] DVB cards and USB devices.~~


-	== Links ==	+	== External Links ==
-	* http://www.b2c2.com/docs/flexcop.pdf	+	* [http://www.b2c2.com/ B2C2 Inc.]
		+	* [http://www.b2c2.com/docs/flexcop.pdf FlexCop PDF]

	[[Category:Decoder]]		[[Category:Decoder]]
	[[Category:Hardware]]		[[Category:Hardware]]