bt8xx.txt 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109
  1. How to get the Nebula, PCTV and Twinhan DST cards working
  2. =========================================================
  3. This class of cards has a bt878a as the PCI interface, and
  4. require the bttv driver.
  5. Please pay close attention to the warning about the bttv module
  6. options below for the DST card.
  7. 1) General informations
  8. =======================
  9. These drivers require the bttv driver to provide the means to access
  10. the i2c bus and the gpio pins of the bt8xx chipset.
  11. Because of this, you need to enable
  12. "Device drivers" => "Multimedia devices"
  13. => "Video For Linux" => "BT848 Video For Linux"
  14. Furthermore you need to enable
  15. "Device drivers" => "Multimedia devices" => "Digital Video Broadcasting Devices"
  16. => "DVB for Linux" "DVB Core Support" "BT8xx based PCI cards"
  17. 2) Loading Modules
  18. ==================
  19. In general you need to load the bttv driver, which will handle the gpio and
  20. i2c communication for us, plus the common dvb-bt8xx device driver.
  21. The frontends for Nebula (nxt6000), Pinnacle PCTV (cx24110) and
  22. TwinHan (dst) are loaded automatically by the dvb-bt8xx device driver.
  23. 3a) Nebula / Pinnacle PCTV
  24. --------------------------
  25. $ modprobe bttv (normally bttv is being loaded automatically by kmod)
  26. $ modprobe dvb-bt8xx
  27. (or just place dvb-bt8xx in /etc/modules for automatic loading)
  28. 3b) TwinHan and Clones
  29. --------------------------
  30. $ modprobe bttv card=0x71
  31. $ modprobe dvb-bt8xx
  32. $ modprobe dst
  33. The value 0x71 will override the PCI type detection for dvb-bt8xx,
  34. which is necessary for TwinHan cards. Omission of this parameter might result
  35. in a system lockup.
  36. If you're having an older card (blue color PCB) and card=0x71 locks up
  37. your machine, try using 0x68, too. If that does not work, ask on the
  38. mailing list.
  39. The DST module takes a couple of useful parameters.
  40. verbose takes values 0 to 4. These values control the verbosity level,
  41. and can be used to debug also.
  42. verbose=0 means complete disabling of messages
  43. 1 only error messages are displayed
  44. 2 notifications are also displayed
  45. 3 informational messages are also displayed
  46. 4 debug setting
  47. dst_addons takes values 0 and 0x20. A value of 0 means it is a FTA card.
  48. 0x20 means it has a Conditional Access slot.
  49. The autodected values are determined bythe cards 'response
  50. string' which you can see in your logs e.g.
  51. dst_get_device_id: Recognise [DSTMCI]
  52. If you need to sent in bug reports on the dst, please do send in a complete
  53. log with the verbose=4 module parameter. For general usage, the default setting
  54. of verbose=1 is ideal.
  55. 4) Multiple cards
  56. --------------------------
  57. If you happen to be running multiple cards, it would be advisable to load
  58. the bttv module with the card id. This would help to solve any module loading
  59. problems that you might face.
  60. for example, if you happen to have a Twinhan and clones alongwith a FusionHDTV5
  61. card
  62. $ modprobe bttv card=0x71 card=0x87
  63. Here the order of the card id is important and should be the same as that of the
  64. physical order of the cards. Here card=0x71 represents the Twinhan and clones
  65. and card=0x87 represents Fusion HDTV5.
  66. Some examples of card-id's
  67. Pinnacle Sat 0x5e
  68. Nebula Digi TV 0x68
  69. PC HDTV 0x70
  70. Twinhan 0x71
  71. Fusion HDTV5 0x87
  72. For a full list of card-id's, you can see the exported card-id's from
  73. bttv-cards.c in linux-2.6.x/drivers/media/video/bttv.h
  74. If you have problems with this please do ask on the mailing list.
  75. --
  76. Authors: Richard Walker, Jamie Honan, Michael Hunold, Manu Abraham