On 4/18/05, Louie Ilievski <[EMAIL PROTECTED]> wrote: > Hi again. I've been having trouble getting my 350 and 150 working > together. I posted a thread on this just a couple days ago, and > thanks to the help of James Sager I'm getting much closer. The cards > initialize properly with the exception that the 150 audio firmware > does not get loaded from version 0.3.2r and on. I was previously > using 0.3.2h, and then decided tonight to randomly try 0.3.2p, and > after that loaded the firmware, I wanted to get closer to the problem, > so I tried every version until I hit 0.3.2r, which is where it stopped > working. I've included the dmesg output from q and r so you can see > what is different. It seems to me that with 0.3.2r, the saa7127 > module does not skip the 150 card, even though I tell it to in the > module configuration. I've also included that for reference. > > Thanks for any help! > > ~Lou
I gave 0.3.3a a shot just now, hoping it would fix my problem since it had some audio firmware patches, but it acted no differently than the others. So, I decided to investigate the situation a little more. Since I was pretty confident that the saa7127 module was the culprit, I did a diff on them, and noticed a small i2c related change. I patched 0.3.3a with the differences between 0.3.2q and 0.3.3a, and reloaded the driver. Everything loaded perfectly. The saa7127 skipped the 150 card as it should have, and the audio firmware loaded fine. Attached is the patch in case anyone wants to try it. I suppose as an alternative you could simply copy over saa7127.c from version 0.3.2q, but this might make things easier. ~Lou
saa7127.patch
Description: Binary data
