On Wednesday 04 August 2004 14:50, Andreas Büsching wrote:
Kenneth Aafløy wrote:
[snip]
I'm pretty sure I checked that the bt driver had a call to i2c_clients_command, but now I can find the changes for either the mt352 or dvb-bt in any of my trees, hmm. I've attached a patch which should be what you need, the extra include <moduleparam.h> is some unrelated changes for kernel < 2.6.7.
Thanx for your fast respone. I applied your patch, but I do not get any new results. I added one printk call to the init function to see if it gets called. This messages is printed out. Another printk call in the mt352_command function (the first line of code) is not printed out. So it looks like the function is still not invoked through the dvb-bt8xx module. The mt352_attach_adapter function is definitely called and returns with no errors.
Ok, seems I should have lisened to Gerd Knorr and Ralph Metzler in the first place.
Any new suggestions?
I've tried to port the dvb-bt driver to the new sub device interface. It might or might not work, depending on my luck :) You will need a snapshot of the bttv core from http://cvs.bytesex.org/video4linux.html, at least from 2004-07-22 15:54. I have no idea what other (if any) patches you would need except this one, so please enlighten me.
Okay, this is what I did:
- reverse your old patch from dvb-bt8xx.c - downloaded v4l snapshot from 2004-07-30 - compiled and installed v4l bttv modules - recompiled dvb-kernel modules with the new patch - reboot
After this procedure everything looks worse.
Loading bttv still works
Loading bt878 is also okay
But at this point seems to be a problem. The next step would be to load dvb-bt8xx. When loading the module, I don't get any output (setting option debug=1 does not help). At the moment I've no clue why.
crunchy
