trefin56 wrote:
- Ubuntu Lucid Lynx with kernel version 2.6.32
[...]
I would like to install the latest version (official or not of the driver) but I am not sure how to proceed and I am looking for advices.
The firedtv updates in 2.6.33 and 2.6.34 are not of importance to your setup as far as I can see.
trefin56 wrote:
Should I install an ubuntu compiled 2.6.34 kernel to benefit from driver update reported here
https://ieee1394.wiki.kernel.org/index. ... ease_Notes ?
That would be one comparably easy approach, but there won't be immediate benefits to you.
trefin56 wrote:
Should I just try to get the source code of the firedtv module and replace only the module ?
If I go for module only replacement, do I need to replace all IEE1394 modules ?
The firedtv driver interacts with the ieee1394 subsystem, the dvb subsystem, and more. Since 2.6.33 it also interacts with the firewire subsystem (which is going to replace the ieee1394 subsystem in a not too distant future). While the in-kernel APIs of the ieee1394 and dvb subsystems don't change often, it is nevertheless not recommendable or not even easily possible to copy driver sources from a certain kernel release to an even only sightly older kernel.
The v4l/dvb project provides sources though that are relatively current
and backwards compatible to older kernels:
http://linuxtv.org/repo/Another possibility is to patch a kernel source tree with a matching patchkit from my own ieee1394 + firewire + firedtv patch collections at
http://user.in-berlin.de/~s5r6/linux1394/updates/. These patchkits bring the three mentioned subsystem at the current state, in a manner that is compatible to the kernel versions for which I generated these patchkits.
trefin56 wrote:
Have the patch described
http://firedtv.kurelid.se/ being included in some later kernel version?
0001-firedtv-correct-version-number-and-current-next-in.patch has been merged into Linux 2.6.35-rc1. It is also present in the linuxtv hg repository if you want to try linuxtv driver sources for an "older" kernel, and it is present in my patchkits.
0002-firedtv-add-parameter-to-fake-ca_system_ids-in-CA_I.patch has not been merged yet and probably won't be. It has been said that this issue appears to be one that should be addressed in application programs rather than by addition of a driver module parameter. I don't know if this is correct; I am not familiar with DVB application programming nor with CAM issues.
trefin56 wrote:
How to apply these patches file to downloaded driver sources ?
Both patches are probably applicable to any 2.6.32...2.6.34 kernel sources.
There is probably some general guidance somewhere on the web on how to run a kernel that was built from patched sources specifically on Ubuntu.