forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'x86/urgent' into x86/pat
- Loading branch information
Showing
143 changed files
with
1,733 additions
and
994 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,46 @@ | ||
What: /sys/bus/pci/drivers/.../bind | ||
Date: December 2003 | ||
Contact: [email protected] | ||
Description: | ||
Writing a device location to this file will cause | ||
the driver to attempt to bind to the device found at | ||
this location. This is useful for overriding default | ||
bindings. The format for the location is: DDDD:BB:DD.F. | ||
That is Domain:Bus:Device.Function and is the same as | ||
found in /sys/bus/pci/devices/. For example: | ||
# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/bind | ||
(Note: kernels before 2.6.28 may require echo -n). | ||
|
||
What: /sys/bus/pci/drivers/.../unbind | ||
Date: December 2003 | ||
Contact: [email protected] | ||
Description: | ||
Writing a device location to this file will cause the | ||
driver to attempt to unbind from the device found at | ||
this location. This may be useful when overriding default | ||
bindings. The format for the location is: DDDD:BB:DD.F. | ||
That is Domain:Bus:Device.Function and is the same as | ||
found in /sys/bus/pci/devices/. For example: | ||
# echo 0000:00:19.0 > /sys/bus/pci/drivers/foo/unbind | ||
(Note: kernels before 2.6.28 may require echo -n). | ||
|
||
What: /sys/bus/pci/drivers/.../new_id | ||
Date: December 2003 | ||
Contact: [email protected] | ||
Description: | ||
Writing a device ID to this file will attempt to | ||
dynamically add a new device ID to a PCI device driver. | ||
This may allow the driver to support more hardware than | ||
was included in the driver's static device ID support | ||
table at compile time. The format for the device ID is: | ||
VVVV DDDD SVVV SDDD CCCC MMMM PPPP. That is Vendor ID, | ||
Device ID, Subsystem Vendor ID, Subsystem Device ID, | ||
Class, Class Mask, and Private Driver Data. The Vendor ID | ||
and Device ID fields are required, the rest are optional. | ||
Upon successfully adding an ID, the driver will probe | ||
for the device and attempt to bind to it. For example: | ||
# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id | ||
|
||
What: /sys/bus/pci/devices/.../vpd | ||
Date: February 2008 | ||
Contact: Ben Hutchings <[email protected]> | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
How to set up the Technisat devices | ||
=================================== | ||
How to set up the Technisat/B2C2 Flexcop devices | ||
================================================ | ||
|
||
1) Find out what device you have | ||
================================ | ||
|
@@ -16,54 +16,60 @@ DVB: registering frontend 0 (Conexant CX24123/CX24109)... | |
|
||
If the Technisat is the only TV device in your box get rid of unnecessary modules and check this one: | ||
"Multimedia devices" => "Customise analog and hybrid tuner modules to build" | ||
In this directory uncheck every driver which is activated there. | ||
In this directory uncheck every driver which is activated there (except "Simple tuner support" for case 9 only). | ||
|
||
Then please activate: | ||
2a) Main module part: | ||
|
||
a.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" | ||
b.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC PCI" in case of a PCI card OR | ||
b.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC PCI" in case of a PCI card | ||
OR | ||
c.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC USB" in case of an USB 1.1 adapter | ||
d.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Enable debug for the B2C2 FlexCop drivers" | ||
Notice: d.) is helpful for troubleshooting | ||
|
||
2b) Frontend module part: | ||
|
||
1.) Revision 2.3: | ||
1.) SkyStar DVB-S Revision 2.3: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "Zarlink VP310/MT312/ZL10313 based" | ||
|
||
2.) Revision 2.6: | ||
2.) SkyStar DVB-S Revision 2.6: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "ST STV0299 based" | ||
|
||
3.) Revision 2.7: | ||
3.) SkyStar DVB-S Revision 2.7: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "Samsung S5H1420 based" | ||
c.)"Multimedia devices" => "Customise DVB frontends" => "Integrant ITD1000 Zero IF tuner for DVB-S/DSS" | ||
d.)"Multimedia devices" => "Customise DVB frontends" => "ISL6421 SEC controller" | ||
|
||
4.) Revision 2.8: | ||
4.) SkyStar DVB-S Revision 2.8: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "Conexant CX24113/CX24128 tuner for DVB-S/DSS" | ||
c.)"Multimedia devices" => "Customise DVB frontends" => "Conexant CX24123 based" | ||
d.)"Multimedia devices" => "Customise DVB frontends" => "ISL6421 SEC controller" | ||
|
||
5.) DVB-T card: | ||
5.) AirStar DVB-T card: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "Zarlink MT352 based" | ||
|
||
6.) DVB-C card: | ||
6.) CableStar DVB-C card: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "ST STV0297 based" | ||
|
||
7.) ATSC card 1st generation: | ||
7.) AirStar ATSC card 1st generation: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "Broadcom BCM3510" | ||
|
||
8.) ATSC card 2nd generation: | ||
8.) AirStar ATSC card 2nd generation: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "NxtWave Communications NXT2002/NXT2004 based" | ||
c.)"Multimedia devices" => "Customise DVB frontends" => "LG Electronics LGDT3302/LGDT3303 based" | ||
c.)"Multimedia devices" => "Customise DVB frontends" => "Generic I2C PLL based tuners" | ||
|
||
Author: Uwe Bugla <[email protected]> December 2008 | ||
9.) AirStar ATSC card 3rd generation: | ||
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build" | ||
b.)"Multimedia devices" => "Customise DVB frontends" => "LG Electronics LGDT3302/LGDT3303 based" | ||
c.)"Multimedia devices" => "Customise analog and hybrid tuner modules to build" => "Simple tuner support" | ||
|
||
Author: Uwe Bugla <[email protected]> February 2009 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.