We’ve reached the end of a major milestone. SAA7164 is ready to be merged into the master LinuxTV repositories at linuxtv.org. For cleanup and ease of merging I’ve extracted all of the patches from saa7164-stable and created saa7164-merge. I’ve asked Mauro to review and merge at his earliest conveinience.
I want to take this opportunity to thank everyone involved in the SAA7164 project. If you’ve donated, tested, written to me, complained, given me words of encouragement or simply reported bugs… thank you!
What’s next for the SAA7164 project? Once the merge is complete we’ll rebuild saa7164-stable and saa7164-dev trees so they reflect the very latest source form LinuxTV.org, meaning you’ll have the very latest patches for your all of your other TV tuner cards along with support for the SAA7164 based products. We’ll continue to maintain the SAA7164 driver here at www.kernellabs.com so keep coming back for the latest news and updates.
Hmm. And after that? What about the Analog Encoder support? Stay tuned, keep reading the KernelLabs blog, the wheels of industry are beginning to turn. We hope to make an important announcement shortly.
Update: The tree was merged into linuxtv.org today, Sep 17th 2009.
Merging the saa7164 driver into the master branch on linuxtv.org is exciting news! …but. you said “I’ve asked Mauro to review and merge at his earliest convenience.” I don’t see this review & pull request on the mailing lists. Can you post a mailarchive link of that email here?
Thunderbird address book lookup failure, I didn’t notice. Email was forwarded again today.
edit: I’ve updated the original post a link to the actual email.
Steve is there any chance I could convince you to work on saa7162?!
Manu seems to be struggling, mostly i guess because of the poor doco he was left with by Phillips. I’d make it worth your while ;-P
These were some of the issues they were struggling with when nxp released the driver..
Not sure you had same start with 7164…
“In essence, the pre-release driver from NXP require rewriting from scratch.
It’s simply not production quality.”
The problem as I see the current code is as follows:
1. It appears to be C++ code basically from their Windows BDA driver,
horribly wedged into the Linux V4L/DVB infrastructure. It’s a poor fit.
2. It doesn’t compile with anything other than kernel 2.6.14 (we’re well
past this version now)
3. It doesn’t support SMP (most systems these days are SMP)
4. It doesn’t support 64 bit
5. It has other bugs/issues too
@Jed, the 7162 driver belongs to Manu and you need to negotiate with him initially for bug fixes, that is how the community operates. If you want to discuss a commercial agreement with KernelLabs in order to have 7162 bugs fixed, or the driver completely re-written, then feel free to contact me privately, we can certainly help. KernelLabs charges commercial hourly rates. (Contact details on the site).
Great news Steve! Well done on all the hard work you’ve put in
Congrats on this milestone.
Sad to report that I’m having problems again. After a recent unrelated reboot the saa7164 driver didn’t load. Tried reloading the driver and got nowhere. Found this in my logs:
[ 1478.161049] saa7164: disagrees about version of symbol dvb_dmxdev_init
[ 1478.161056] saa7164: Unknown symbol dvb_dmxdev_init
[ 1478.161244] saa7164: disagrees about version of symbol dvb_register_adapter
[ 1478.161247] saa7164: Unknown symbol dvb_register_adapter
[ 1478.161795] saa7164: disagrees about version of symbol dvb_net_init
[ 1478.161795] saa7164: Unknown symbol dvb_net_init
[ 1478.161795] saa7164: disagrees about version of symbol dvb_dmxdev_release
[ 1478.161795] saa7164: Unknown symbol dvb_dmxdev_release
[ 1478.161795] saa7164: disagrees about version of symbol dvb_frontend_detach
[ 1478.161795] saa7164: Unknown symbol dvb_frontend_detach
[ 1478.161795] saa7164: disagrees about version of symbol dvb_net_release
[ 1478.161795] saa7164: Unknown symbol dvb_net_release
[ 1478.161795] saa7164: disagrees about version of symbol dvb_unregister_frontend
[ 1478.161795] saa7164: Unknown symbol dvb_unregister_frontend
[ 1478.161795] saa7164: disagrees about version of symbol dvb_register_frontend
[ 1478.161795] saa7164: Unknown symbol dvb_register_frontend
[ 1478.161840] saa7164: disagrees about version of symbol tveeprom_hauppauge_analog
[ 1478.161842] saa7164: Unknown symbol tveeprom_hauppauge_analog
[ 1478.161881] saa7164: disagrees about version of symbol dvb_unregister_adapter
[ 1478.161884] saa7164: Unknown symbol dvb_unregister_adapter
I’d appreciate any help as usual.
@Matt, you probably got a kernel update and need to rebuild your saa7164 driver. First, from inside the saa7164 tree, do “make distclean” , then make && sudo make install all over again. The driver should load up properly on the next reboot. If you run into build problems, try using the ~mkrufky/saa7164 tree instead.
Steven, thanks a lot for your great work. I no longer have any problems with digital recording on my 2250. I can even channel surf with no lockups using the stable branch. I am looking forward to further progress and would be willing to help a bit for analog support.
Thanks Patrick.
@Michael
Haven’t updated my kernel lately but I was messing with a lot of stuff late at night trying to get mythgame to work so I can’t really guarantee anything.
Rebuilt with a “make clean;make;make install” but still failed after cold boot.
Suspected (grasping at straws) thermal issues so I left the box off for a couple hours. Now it seems to be working again. I’ll keep a closer eye on the temps from now on.
thanks for the suggestion.
I installed the latest development source into an OpenSUSE 11.1 Athlon X2 4000+ MythTV system and have made about 20 QAM256 recordings at 480i, 720p, and 1080i resolutions without issues under MythTV 0.21. Two of the programs record concurrently at 270p and 1080i resolutions. This is wonderful, and gets me ready for Comcast dropping transmission of several favorite analog channel transmissions!
Are there plans to add Remote control support to the driver for Linux? I’d like to get rid of the keyboard and mouse for programming, skip features, etc. If I can offer driver programming help in this area, please let me know. I might need a little help knowing how to attach to Linux IR support infrastructure for this remote control effort (so far looks like serial /dev/ttyS[0-N] work). A list of my past development experience is on my web site.
@Steve, Congratulations on today’s merge to the linuxtv.org master branch!
@Michael, thanks
@Craig, I’ve just responded to your linuxtv email. Sadly, due to circumstances beyond my control I’m unable to release the materials you’d need in order to work on IR, although thank you for your offer of help. Other than that, glad to hear the driver is working well for you!
Does this driver support the saa7163 as well? According to the NXP document I have read it is the single stream version of the saa7164. NewEgg has a card which is $50 AMIR. Thanks!
@Brandon, not that I’m aware of. Highly unlikely.
Could someone explain the implications of this to a noob? For example, does this change the install instructions found here:
http://ubuntu-virginia.ubuntuforums.org/showthread.php?p=7344302
Specifically, I’m wondering if the URL of the mercurial repository needs to change from:
http://kernellabs.com/hg/saa7164-stable
to something else at linuxtv.org.
Sorry if my question’s naive, I haven’t really grokked how all these different parts fit together.
Thanks.
Hello Dan,
Yes, generally speaking once the code is merged upstream you should use the main v4l-dvb mercurial URL: http://linuxtv.org/hg/v4l-dvb
Cheers,
Devin
Thanks for the response. Are there any other changes that come into effect with releasing into linuxtv.org? It looks like linuxtv has a sort of architecture that drivers fit into. Does that mean I need to install that architecture and its libraries also, or do I still grab the saa7164-stable from some portion of their repository tree and compile/install just as before?
I’ve been trying to get the driver to work on my machine for a while and am having problems. I know this probably isn’t the best place to look for technical help. Could someone point me to a mailing list or forum for users of the driver? Sorry for cluttering up the comments here.
Thanks,
dan
Dan,
I would suggest sending email to the linux-media mailing list:
http://linuxtv.org/lists.php
Cheers,
Devin
Hi
I have an ASUS My Cinema-EHD2-100/PT/FM/AV/RC tuner card with the saa7164 chip.
I tried the stable version, but the card wasn’t known to the driver.
What could I do to be this card know to the driver?
What did the console messages say?
[ 8.837874] saa7164 driver loaded
[ 8.838161] saa7164 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 8.838168] saa7164[0]: Your board isn’t known (yet) to the driver.
[ 8.838169] saa7164[0]: Try to pick one of the existing card configs via
[ 8.838170] saa7164[0]: card= insmod option. Updating to the latest
[ 8.838171] saa7164[0]: version might help as well.
[ 8.838175] saa7164[0]: Here are valid choices for the card= insmod option:
[ 8.838177] saa7164[0]: card=0 -> Unknown
[ 8.838179] saa7164[0]: card=1 -> Generic Rev2
[ 8.838181] saa7164[0]: card=2 -> Generic Rev3
[ 8.838183] saa7164[0]: card=3 -> Hauppauge WinTV-HVR2250
[ 8.838184] saa7164[0]: card=4 -> Hauppauge WinTV-HVR2200
[ 8.838186] saa7164[0]: card=5 -> Hauppauge WinTV-HVR2200
[ 8.838188] saa7164[0]: card=6 -> Hauppauge WinTV-HVR2200
[ 8.838191] saa7164[0]: card=7 -> Hauppauge WinTV-HVR2250
[ 8.838193] saa7164[0]: card=8 -> Hauppauge WinTV-HVR2250
[ 8.838343] CORE saa7164[0]: subsystem: 1043:48cb, board: Unknown [card=0,autodetected]
[ 8.838349] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 17, latency: 0, mmio: 0xfb800000
[ 8.838355] saa7164 0000:02:00.0: setting latency timer to 64
[ 8.838359] IRQ 17/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 8.838371] saa7164_initdev() Unsupported board detected, registering without firmware
lspci -vv:
02:00.0 Multimedia controller: Philips Semiconductors Device 7164 (rev 81)
Subsystem: ASUSTeK Computer Inc. Device 48cb
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at fb400000 (64-bit, non-prefetchable) [size=4M]
Capabilities: [40] Message Signalled Interrupts: Mask- 64bit+ Queue=0/4 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [50] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x2, ASPM L0s L1, Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [74] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [7c] Vendor Specific Information
Capabilities: [100] Vendor Specific Information
Capabilities: [160] Virtual Channel
Kernel driver in use: saa7164
Kernel modules: saa7164
[ 8.837874] saa7164 driver loaded
[ 8.838161] saa7164 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 8.838168] saa7164[0]: Your board isn’t known (yet) to the driver.
[ 8.838169] saa7164[0]: Try to pick one of the existing card configs via
[ 8.838170] saa7164[0]: card= insmod option. Updating to the latest
[ 8.838171] saa7164[0]: version might help as well.
[ 8.838175] saa7164[0]: Here are valid choices for the card= insmod option:
[ 8.838177] saa7164[0]: card=0 -> Unknown
[ 8.838179] saa7164[0]: card=1 -> Generic Rev2
[ 8.838181] saa7164[0]: card=2 -> Generic Rev3
[ 8.838183] saa7164[0]: card=3 -> Hauppauge WinTV-HVR2250
[ 8.838184] saa7164[0]: card=4 -> Hauppauge WinTV-HVR2200
[ 8.838186] saa7164[0]: card=5 -> Hauppauge WinTV-HVR2200
[ 8.838188] saa7164[0]: card=6 -> Hauppauge WinTV-HVR2200
[ 8.838191] saa7164[0]: card=7 -> Hauppauge WinTV-HVR2250
[ 8.838193] saa7164[0]: card=8 -> Hauppauge WinTV-HVR2250
[ 8.838343] CORE saa7164[0]: subsystem: 1043:48cb, board: Unknown [card=0,autodetected]
[ 8.838349] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 17, latency: 0, mmio: 0xfb800000
[ 8.838355] saa7164 0000:02:00.0: setting latency timer to 64
[ 8.838359] IRQ 17/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 8.838371] saa7164_initdev() Unsupported board detected, registering without firmware
lspci -vv:
02:00.0 Multimedia controller: Philips Semiconductors Device 7164 (rev 81)
Subsystem: ASUSTeK Computer Inc. Device 48cb
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at fb400000 (64-bit, non-prefetchable) [size=4M]
Capabilities: [40] Message Signalled Interrupts: Mask- 64bit+ Queue=0/4 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [50] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x2, ASPM L0s L1, Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [74] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [7c] Vendor Specific Information
Capabilities: [100] Vendor Specific Information
Capabilities: [160] Virtual Channel
Kernel driver in use: saa7164
Kernel modules: saa7164
Hmm, your right. The SAA7164 driver only supports Hauppauge HVR2200 and HVR2250′s.
Sorry for double post…
What can we do to make it suport this card as well?
How can I help?
Not that I can do the coding, but I can help testing if it is necessary.
hi, i’ve just purchased a HVR2200 with the extension cable, for the encoder HW feature.
under “the other OS” it works more or less. but i would prefer to use linux to script some batch execution
so i kindly ask if there is an extimated ETA for the Analog encoding HW support
regards
I’ve got two 2250s in a Windows SageTV server just waiting for the analog portion of the linux driver to be completed. Just wanted to make sure that you know there are still people interested in analog support…
Hi Steve,
What would it take to get analog support on the HVR2250? I am willing to commit a few hundred USD, I suspect others are willing to contribute cash for your time to add analog support.
Thanks!
Hi Guy / Keith / Andrea,
Thanks for asking. As you can appreciated, I only have a limited amount of spare Linux capacity and that’s currently occupied by the cx23885 Linux driver.
I have a problem with the hvr 2200 on linux 2.6.32-rc7 x86-64.
When I initialize the second tuner with tzap the first
lose the FE_HAS_LOCK, and viceversa. Here is an example:
tzap -a 1 “LA7(MBone)”
using ‘/dev/dvb/adapter1/frontend0′ and ‘/dev/dvb/adapter1/demux0′
reading channels from file ‘/root/.tzap/channels.conf’
tuning to 826000000 Hz
video pid 0×0101, audio pid 0×0102
status 00 | signal d5d5 | snr 0044 | ber 0000ffff | unc 00000000 |
status 1f | signal fdfd | snr 00d7 | ber 00000617 | unc 00000045 | FE_HAS_LOCK
status 1f | signal fcfc | snr 00c6 | ber 0000094e | unc 00000000 | FE_HAS_LOCK
status 1f | signal fafa | snr 00a8 | ber 000009db | unc 00000046 | FE_HAS_LOCK
status 01 | signal 0000 | snr 0005 | ber 0000ffff | unc 00000000 |
status 1f | signal fdfd | snr 00c6 | ber 000007d8 | unc 00000000 | FE_HAS_LOCK
status 1f | signal fcfc | snr 00c6 | ber 00000750 | unc 00000000 | FE_HAS_LOCK
status 1f | signal fcfc | snr 00d7 | ber 0000082c | unc 00000000 | FE_HAS_LOCK
status 1f | signal fcfc | snr 00b9 | ber 00000898 | unc 00000000 | FE_HAS_LOCK
‘status 01′ happened when running ‘tzap MTV’.
I have discovered this behaviour while watching tv with
both vlc and kaffeine: when one of the two application are
opened or closed, the image is garbled for about 1 seconds.
Anyone?
Marco, have you tried windows to see if the same error occurs?
Sorry Steven,
I’m unable to try with windows. I don’t understand how to use
both tuners (I’m runnign winxp_sp3 with winTV7 1.2b).
You should be able to schedule a background recording and watch livetv at the same time. While your background recording is in progress, if you flip between livetv channels in theory it will great minor glitches in the background recording. Subsequent playback of that recording may / may-not should issues.
Thanks Steven, this evening I will try, and I will let you know.
Could it be a linux driver bug?
PS: just for ask: did you receive my message about the updated firmware?
Good morning Steven,
On windows xp, I’m unable to reproduce the problem. I started vlc & WinTV7.
VLC video stream wasn’t garbled.
@Marco, let me look into this over the next few days.
I’m very happy hearing you.
Thanks a lot Steven.
Hi Steven,
did you get any time to look this problem about?
Just for clarification: only the adapter 1 is affected by this problem.
When I initialize the adapter 0 the adapter 1 lose the ‘FE_HAS_LOCK’.
When I initialize the adapter 1 the adapter 0 *does not* lose the ‘FE_HAS_LOCK’.
So only adapter 1 is affected by this problem.
Apologies for misinformation.
Steven, I too would love to get you to start work on the analog support for this card. $$ can be a big motivator and I previously supported the original driver development. Maybe consider putting out the Paypal donation button again and see what that gets you?
I just bought my hvr 2250. I installed, configured the kernel drivers and make some tests. I found almost all my cable channes are scrambled, that leaves me only the use of the RCA inputs with IRblasters and the motorola decoders… are there the RCA inputs ready to use? if yes, how can I select them as the video/audio source?
Thanks!!!
If not, do you think if I made some more donations will help to accelerate the process?
Hi Mario. The analog inputs are not currently supported. I do plan to have analog support on the saa7164 but it’s not in my immediate horizon.
I am also interested in getting the analog support implemented for the 2250 and would consider donating some money if an estimated delivery date were available. Also, so Hauppauge site (here) FAQ page lists Linux support as “work in progress.” Is that this same effort or something else?
Thanks Ryan, let’s see how things work out of the next few weeks before I commit to anything.
Yes, Hauppauge “Work in Progress” is indeed my work.
Just adding another voice to the analog support on the 2250 and would be happy to donate. =)
I’m looking forward to analog support as well. The basic cable from my provider (Charter) is about two thirds analog SD, and one third digital. For me, the HVR-2250 is the perfect card for a mythtv backend, assuming I can use the analog tuners.
One more voice for the analog support for the tuners (HVR-2200 board). All my channels are analog in the cablenet in my house here in Sweden. Looking forward to leave MS win7 to take the full step to the linuxplattform. Thx for your good work so far Steven.
Steven,
I wanted to add another voice for analog and IR remote (IR more so for me). Is there a roadmap for either of these features in the works? Thanks for the good work thus far!
Another vote for analog and IR remote support. The Hauppage 2250 card is the complete package if we can get it fully functioning in Linux. The digital portion is working great for me. Thanks a ton!
I’ve added IR to my todo list for the project.
I’ll be buying two or three when analog support comes along.
One more vote to get analog support. (HVR-2250).
Thanks!
Hi Steven, with regards to the following statement you made last year:
“Hmm. And after that? What about the Analog Encoder support? Stay tuned, keep reading the KernelLabs blog, the wheels of industry are beginning to turn. We hope to make an important announcement shortly”
Have you guys made any announcements with regards to this yet?
I read your post stating that analogue was a no go, was that the announcement?
Thanks
@Mike, analog is on the cards currently mid-year best guess. Nothing else to say at this point.
Now that is some great news !!!! THANKS Steven
Is mid-year still a reasonable target for analog?
It’s not unreasonable.
Oh my. I just gave that exact same response when asked about a code release. So, *that’s* what my petard looks like.
Also another vote for analog support. I’ll donate some money when the delevopment of analog support is in progress.
I’m also waiting for analog support for the HVR-2200. Until then my HTPC build is on hold
Thanks for all of the hard work Steven!
Thanks David.
I just downloaded the firmware and built the development version. After “modprobe saa7164″, I found this in the syslog:
Mar 26 21:12:27 eowyn firmware.sh[27998]: Cannot find firmware file ‘v4l-saa7164-1.0.3-3.fw’
The firmware downloaded from your site had only these versions:
v4l-saa7164-1.0.2.fw
v4l-saa7164-1.0.3.fw
Where should I get the “-3″ firmware?
@Jim, did you look in the sub folders in that web dir? You should find it in http://steventoth.net/linux/hvr22xx/firmwares/4038864/
Thank you very much!
Now to configure Mythtv for the new tuner…
Steven, there seems to be a good deal of interest for the analog support, IR Receiver and Blaster for the hauppage 2250. Is there any way to measure all of our interest, and specifically get an understanding of the $ people would contribute to help you get this done? Just asking, wanting to make sure that we all truly understand the # of people that would $ support your effort. Sorry if this is a dumb question, I’m fairly new to open source and feature requests. I would also understand if your experience tells you that communication donations $ are never enough to reprioritize your own work and that you will get to it when it works for you.
This interest is a compliment to your initial work, as the digital TV works excellent.
http://www.gossamer-threads.com/lists/mythtv/users/430004?page=last
Thanks for all your hard work. Pretty cool being the man.
I agree with this, it would be good to know a ballpark of how much you think it would be to make adding analog support worth your while. I’d probably be willing to kick in at least $50. If 99 others were willing to do the same?
i have a recent hvr 2200 . that is quiet hard to set up but it seems that this topic explain well : http://www.xpmediacentre.com.au/community/linux-tutorials-guides/38864-hauppauge-hvr-2200-tuner-install-guide-4.html
so myyk talk about the fact that the 8940 is not drived yet . will it come soon ?
i tried modprobe saa7164 card=4 but it did not worked . in a future release can you add more comment on the numbers and cards that should use it .
for 8940 there should be card = 9 . if you could make it available with the ubuntu package manager that could be wonderfull
I would just like to add my voice to the many here that would love to see analog implemented. Cox cable still are (annoyingly) mostly analog. I’d be happy to contribute $$$ to get a proper effort started.
Your work on the HVR-2200 is much appreciated, do a huge thanks. I would like to add my voice in support for the development of the analogue component to this card. Having the hardware encoder available under Linux would be fantastic. If you need a tester, I have the resources to do this.
Thanks for all your efforts.
One more voice to analogue support. I hope there will be enough people willing to donate and to help to get this done. I can only speak for myself, but I would really be willing to donate if this would get things going. Maybe I’ve missed it, but reading this page I could not understand how big effort would this be? Is it really so hard to implement, or too time consuming? I know that probably our donations would not cover much, but would it help if we send emails to hauppauge urging them to support your work ? At least tell us if there is any hope for analogue support since it’s already midlle of the year?