Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73132 - ivtv firmware version not recommended one
Summary: ivtv firmware version not recommended one
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Brian Jackson (RETIRED)
URL:
Whiteboard:
Keywords:
: 101785 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-12-02 06:34 UTC by Rutger Hendriks
Modified: 2005-08-08 13:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rutger Hendriks 2004-12-02 06:34:11 UTC
There have been several discussions on the ivtv-devel mailinglist about which firmware version to use. The person who is releasing the ivtv-driver (Chris Kennedy) keeps recommending one specific firmware version. This is not the version that is used in the gentoo ivtv ebuilds up to now.
Is there a specific reason for that? 
If so, it would be nice to have it mentioned here for reference.
If not, it might be a good idea to change the firmware to the one mentioned by Chris, which can be found here:

ftp://ftp.shspvr.com/download/wintv-pvr_250-350/win9x-2k-xp_mpeg_wdm_drv/pvr48wdm_1.8.22037.exe

Please tell me what you think about it.
Thanks
Comment 1 Brian Jackson (RETIRED) gentoo-dev 2004-12-02 09:05:00 UTC
The version that was used in versions prior to 0.2.0_rc3 was just what was the latest at the time, and noone ever complained. The version that is used in 0.2.0_rc3 is the version that's listed as recommended on the ivtv wiki. I'm not all that tempted to change it unless there are actual problems with it. Personally I think the wraning in the drivers is a little too restrictive. It's based on what works for 1 person on his specific computer.
Comment 2 Brian Jackson (RETIRED) gentoo-dev 2005-08-08 13:35:28 UTC
*** Bug 101785 has been marked as a duplicate of this bug. ***