Difference between revisions of "Template:Firmware:dvb-usb-dib0700"

From LinuxTVWiki
Jump to: navigation, search
m
(Changes made to IR functions November 16 crash the card with i2c errors)
Line 12: Line 12:
 
'''August 29,2008 - Issues with Firmware 1.20'''.  Some issues have been found with the latest version of the firmware.  Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.
 
'''August 29,2008 - Issues with Firmware 1.20'''.  Some issues have been found with the latest version of the firmware.  Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.
  
'''November 19,2008 - Issues with Firmware 1.20'''.   
+
'''November 15,2008 - Issues with Firmware 1.20'''.   
 
* The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
 
* The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
 
* [http://www.wi-bw.tfh-wildau.de/~pboettch/home/files/dvb-usb-dib0700-1.20.fw <tt>dvb-usb-dib0700-1.20.fw</tt> firmware file] is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed.  The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
 
* [http://www.wi-bw.tfh-wildau.de/~pboettch/home/files/dvb-usb-dib0700-1.20.fw <tt>dvb-usb-dib0700-1.20.fw</tt> firmware file] is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed.  The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
Line 18: Line 18:
 
* To avoid spurious remote control signals with 1.20 firmware, you need to edit <tt>/etc/modprobe.d/options</tt> and add:
 
* To avoid spurious remote control signals with 1.20 firmware, you need to edit <tt>/etc/modprobe.d/options</tt> and add:
 
  options dvb_usb disable-rc-polling=1
 
  options dvb_usb disable-rc-polling=1
 +
 +
'''November 28,2008 - i2c errors'''. 
 +
Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem.  These are currently causing i2c read and write errors which crash the card.  The card is still generally stable for dual tuner reception with Firmware 1.20 as long as remote control polling is disabled.

Revision as of 01:44, 1 December 2008

Firmware

August 21, 2008 - New firmware file fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting.

You will need the dvb-usb-dib0700-1.20.fw firmware file in /lib/firmware or the relevant place for your distribution.

You may need to change the name of the file to dvb-usb-dib0700-1.10.fw or create a link until the driver code reflects that change.

For archival purposes: dvb-usb-dib0700-1.10.fw firmware file

August 29,2008 - Issues with Firmware 1.20. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.

November 15,2008 - Issues with Firmware 1.20.

  • The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
  • dvb-usb-dib0700-1.20.fw firmware file is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
  • The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to dvb-usb-dib0700-1.20.fw or provide a link of that name.
  • To avoid spurious remote control signals with 1.20 firmware, you need to edit /etc/modprobe.d/options and add:
options dvb_usb disable-rc-polling=1

November 28,2008 - i2c errors. Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem. These are currently causing i2c read and write errors which crash the card. The card is still generally stable for dual tuner reception with Firmware 1.20 as long as remote control polling is disabled.