Hello,
On 07/01/04 23:10, Nishanth Aravamudan wrote:
[Not subscribed to linux-dvb, so please CC back if replying from that list]
I'm working on one of the KernelJanitor/TODO items, specifically
converting appropriate calls to schedule_timeout() to msleep() calls
(Addendum by Greg KH to original
Michael Hunold wrote:
I don't think it's ever necessary to be interruptible for us, so
mdelay() is suitable.
^^
msleep()
Johannes
Hi,
I'm working on an DVB-output extension for the SDL-library, so you can use
SDL-ported apps on your TV-screen:
http://www.vdrportal.de/board/thread.php?threadid=19229sid=
(sorry in german!)
Currently Audio and Video works separately well. But if I send audio and
video
packets to the device,
Hello Luke,
On 07/01/04 23:37, Luke Anderson wrote:
as you may be aware, the firmware for tda1004x is stored
in /usr/lib/hotplug/firmware/tda1004x.bin. However a problem arises whenever
a new firmware is released because the offsets are different within that
file.
May I suggest that tda1004x.c
Just to clear up some confusion I was having,
I incorrectly assumed that the different versions numbers for the drivers
available from the technotrend.de site, were indicative of different firmware
versions.
I now know this not to be the case.
But it appears that although the firmware version
From: Michael Hunold [EMAIL PROTECTED]
1. Rename the default firmware from tda1004x.bin to
dvb-fe-tda1004x-2.15a.fw. Add a comment that users should
extract and rename their firmware appropriately.
Hmm, how about a really flexible solution:
Instead of reading a firmware file directly, read a
What is the current status, if I were to switch my full-feature
Hauppauge card over to a new Fedora Core 2 machine which uses
kernel-2.6.6-1.435.2.1, what patches do I need to apply or should
a current release work immediately?
--
/* * * Otto J. Makela [EMAIL PROTECTED] * * * * * * * * * * *
On Fri, 2004-07-02 at 12:32, Michael Hunold wrote:
1. Rename the default firmware from tda1004x.bin to
dvb-fe-tda1004x-2.15a.fw.
That's the Technotrend Windows driver version, not the DSP firmware
version.
Add a comment that users should extract and
rename their firmware appropriately.
Andreas Oberritter wrote:
On Fri, 2004-07-02 at 12:32, Michael Hunold wrote:
1. Rename the default firmware from tda1004x.bin to
dvb-fe-tda1004x-2.15a.fw.
That's the Technotrend Windows driver version, not the DSP firmware
version.
What's important is that the driver and the firmware
From: Luke Anderson [EMAIL PROTECTED]
However I have tried, and failed to hack the sources to accomodate
the DLL from this new driver version:
static struct fwinfo tda10045h_fwinfo[] = { {.file_size =
286720,.fw_offset
= 0x34cc5,.fw_size = 30555}, {.file_size =
Hi Andreas,
On Fri, Jul 02, 2004 at 02:00:28PM +0200, Andreas Oberritter wrote:
[...]
the (hardcoded) firmware version in tda1004x_check_upload_ok is quite
useless IMHO.
I agree with you that a hardcoded comparison is not a good solution.
However, especially in case of problems with the driver
I managed to do some testing of Christopher Pascoe's driver this
evening with interesting results.
I used the CVS version of linuxtv DVB along with Christopher's mt352
front end (the current one in the CVS didn't get nearly as far as
Christopher's mt352.c from
[EMAIL PROTECTED] wrote:
What is the current status, if I were to switch my full-feature
Hauppauge card over to a new Fedora Core 2 machine which uses
kernel-2.6.6-1.435.2.1, what patches do I need to apply or should
a current release work immediately?
There is (was?) a problem with the osd
Hi,
i and some other people from vdrportal.de have some trouble using budget
cards, because the card died after some time.
In my case there are Skystar2 rev 2.6c and Nova budged (like budget-ci)
cards and a fullfeatured rev. 1.5 card (all of them use the stv0299
friontend, but other reported
Hello dvb-users,
I proudly announce that I have completed a first alpha-driver for
the mentioned device. (aka VP7041)
If you own such a device I would like to encourage you to test the driver
and please, please report if you had problems or not. Also, if you do not
own such a device, it would be
On Fri, Jul 02, 2004 at 04:41:37PM +0200, Andreas Share wrote:
In this case there are no more handled IRQ´s to see in /proc/interrupts for
the card. I have tried to debug this on a second computer with a rev 1.3 as
primary and a second skystar2 as secondary card. The only i have seen is
that i
On Fri, Jul 02, 2004 at 04:41:37PM +0200, Andreas Share wrote:
In this case there are no more handled IRQ´s to see in /proc/interrupts
for
the card. I have tried to debug this on a second computer with a rev 1.3
as
primary and a second skystar2 as secondary card. The only i have seen is
Hi,
I have a problem, I don't get my Pinnacle PCTV Sat to work on Linux kernel
2.6. In my desperation I tried to load nearly every module I found in the dvb
folder. After loading every module I tried whether the DVB-card works, but it
did never. So the loaded dvb modules are right now:
The following code does a few loops and then kills my card:
(or is there something wrong with the program??)
#include stdio.h
#include stdlib.h
#include unistd.h
#include linux/dvb/frontend.h
#include linux/dvb/dmx.h
#include errno.h
#include string.h
#include sys/ioctl.h
#include fcntl.h
void
[EMAIL PROTECTED] wrote:
I wrote my own application to get epg. I call the usual SetFiltSection()
in a loop to get the package for the currently tuned channel. After too many
calls (30-40??) the card (nova) hangs, too. Module reloading doesn't fix
the problem. Since I don't have to wait a
Roland Praml wrote:
I'm working on an DVB-output extension for the SDL-library, so you can use
SDL-ported apps on your TV-screen:
http://www.vdrportal.de/board/thread.php?threadid=19229sid=
(sorry in german!)
Currently Audio and Video works separately well. But if I send audio and
Your description of what you do is rather vague. Assuming you
write audio to /dev/dvb/adapterX/audioY and video to
/dev/dvb/adapterX/videoY, why don't you use nonblocking I/O?
Yes thats right, I open the devices with O_NONBLOCK and I poll
each device to see if i can write new data. But it
I already mailed about this on the vdr list, but got no responses and I think
this is probably a driver problem anyway.
I have two Hauppauge DVB-C 2.1 cards with CI and Conax CAM on the first card.
I'm using the first card's video out. I'm currently using linuxtv-dvb-1.1.1
and vdr 1.3.11,
Hello!
I bought a Technotrend DVB-C PCI budget card on eBay
(http://cgi.ebay.de/ws/ebayISAPI.dll?ViewItemitem=5100217074) and have now
tried for more than two weeks to make it work with linux. I have really tried
many different things, two different computers, many many kernel versions,
Hi Soyeb,
Since the KWorld/V-Stream card uses the same Samsung Tuner as the
AVerMedia AVerTV DVB-T 771, I decided to force the mt352 front end to
treat the V-Stream card as an Avermedia card with interesting results.
It seems that the tuner can now be controlled, but I can't grab the
stream.
I wonder if this info in the kernel logs could be a hint as to why the
DVB isn't working:
--
cx88_register_dvb_module
Linux video capture interface: v1.00
cx2388x v4l2 driver version 0.0.4 loaded
cx8800[0]: found at :01:08.0, rev: 5, irq: 18, latency: 32, mmio: 0xde00
cx8800[0]:
26 matches
Mail list logo
