On Wed, Jun 04, 2003 at 05:08:26PM -0700, Doug You wrote:
are these working properly? assuming fine, compiled xawtv-3.88, which
looked ok, but when I executed, got the following erros.
This is xawtv-3.54, running on Linux/i686 (2.4.20)
Are you sure of the version you are using?
I read 3.54,
hi,
I got the following error msg. when i had tried to
install linux-dvb.2003-04-27(make) on the kernel
version 2.4.18-14.
make[3]: Entering directory
`/home/rohini/vdr/DVB/driver'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.18-14/include
-Wall -Wstrict-prototypes -W
no-trigraphs -O2
Hi,
your kernel include files are screwed up. I'd suggest you to get a fresh
kernel source tarball from http://www.kernel.org/, configure and install
this one and then try again to build the driver.
Holger
M Rohini wrote:
hi,
I got the following error msg. when i had tried to
install
Hi all,
I would like to know if there is any limitation on the osd color palette.
I know VDR just can use 16 palette deep colors and I'd like to know if it
is a limitation of the linuxtv driver, an specific DVB card limitation or
it is an specific VDR implementation.
Thanks in advance.
Marc R.
On Thu, Jun 05, 2003 at 11:37:22AM +0200, Marc Rovira Vall wrote:
I would like to know if there is any limitation on the osd color
palette.
In short, yes.
There is a relatively small amount of SDRAM available for use by the
AV7110, which has to be used (amongst other things) for
- firmware
Andreas Oberritter wrote:
James, I don't know the reason for this problem, but to say it again:
You should use DMX_PES_OTHER if you are recording. using
DMX_PES_AUDIO/VIDEO does not work (ok, it works for the av7110, but it
is a bug in the driver). just to make your code portable. ;)
On Thu, 2003-06-05 at 22:15, James Green wrote:
But when I did this fix I found that I still got overflow errors. I
instrumented the code a lot and found that the read routine couldn't keep
up with the write routine. The buffer size was the default, 8192 bytes.
This doesn't seem large
On Thu, 2003-06-05 at 22:52, Dominik Strasser wrote:
Do you see a chance to port the stuff to 2.4. I looked into it and it
the drivers are _really_ different (v4l/v4l2 ?)
dvb-kernel already works quite well with current 2.4 kernels.
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED]
michal wrote:
Yes, this works fine for me. Can somebody competent check it and then
apply attached patches?
applied. thanks for catching this one,
Holger
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
I had a similar problem a while ago, and it turned out be be a DiSEqC
problem. The polarization was sometimes set wrong, and the zig-zag scan
locked on an adjacent transponder.
You could run 'apps/scan/scan -c' to verify that you are tuned to
the right TP.
Johannes
Great guess, thanks:) And what
Tomi Ollila schrieb:
Wednesday Jun 4 12:57:52 +0200 2003 Guido Draheim [EMAIL PROTECTED] wrote:
Well Tomi,
it's actually annoying - of course the /dev/video viewer
...
that is.
This article maybe explains the situation...:
Guido Draheim wrote:
Tomi Ollila schrieb:
Wednesday Jun 4 12:57:52 +0200 2003 Guido Draheim
[EMAIL PROTECTED] wrote:
Well Tomi,
it's actually annoying - of course the /dev/video viewer
...
that is.
This article maybe explains the situation...:
I've been compiling DVB cvs for 2.4.21-0.13mdk (mandrake 9.1 kernel).
Using zapping to overlay the hw-decoded video onto the screen which
uses a v4l device.
This works fine on the primary head (an ati card), but it does not
work on the secondary head (an nvidia card). The motion picture
is visible
Holger Waechtler schrieb:
Guido Draheim wrote:
Theoretically, the v4l/ devices even allow to tune (_FLAG_TUNER),
exposing themselves as the frontend device to the videodev per se.
(well, _frequency is not all there is a dvb stream). Therefore, and
from the same theory, one might say that
I would suggest trying different values when setting PCI burst length and FIFO
threshold via this line from the patch:
saa7146_write(saa-mem, PCI_BT_V1, 0x0007);
If you look in the SAA7146A spec sheet on page 31 you will find a definition
of the register (PCI_BT_V1, at offset 0x48), and
Am Mittwoch, 4. Juni 2003 12:57 schrieb Guido Draheim:
Sadly, some other dvb tools have crashed so far, esp.
the vdr freezes up hard.
I think you should try to fix your problems with vdr. Its a great app and
since you have a premium dvb-s i don't understand why you do not use it. Its
running
I had a RedHat 7.3 system with linuxtv-dvb-1.0.0-pre2.tar.gz
installed. Everything was working great. One day, however,
the system boots up and the linuxDVB module is unable to install.
The missing dependencies are in
/usr/src/linux-2.4.18-3/include/linux/modules/
that is they are
Hi,
I recently bought a Lorenzen SL DVB-T pci card for my computer. It works on Win2k
(though awfully slowly), so I tried to install it on linux.
After some fiddeling I managed to compile the driver (Version 1.0.0-pre3), libdvb
(0.4.0) and some dvbtools (0.4).
For make'ing insmod I had to add
From: Jens Herrmann [EMAIL PROTECTED]
I recently bought a Lorenzen SL DVB-T pci card for my computer.
So have I :-)
What do you think? May I soon watch television instead of working?
The problem is that the register-level documentation on the frontend
chipset (Philips TDM1316L and TDA10045H)
Gregor Lawatscheck wrote:
At 02:40 04/06/2003, you wrote:
I haven't had a single arm crash for weeks. All arm crash problems
disappeared when the OSD was fixed in March.
Do you use transfer mode much? I believe replaying / transfermode
with recordings / programms that require a high video
While I am not a Linux programmer, I'll happily share my knowledge on how
to make this frontend work with anyone who is willing to start a
corresponding Linux module.
Please send this information to me, and I'll implement a frontend for it if
you want.
--
Info:
To unsubscribe send a
On Mon, 2 Jun 2003, Johannes Stezenbach wrote:
[Code fragment removed]
This can't work. You must use select() or poll() to wait for
data to arrive, then read() from the file descriptor which is ready.
I changed my code to use select() and exactly the same happens. I'm
beginning to suspect
On Thu, 2003-06-05 at 00:27, James Green wrote:
What is special about ~9KB?
The least common multiple of 188 and 204 is 9588. ;-)
Tomas
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
On Wednesday 04 June 2003 17:08, Tomas Andersson wrote:
On Thu, 2003-06-05 at 00:27, James Green wrote:
What is special about ~9KB?
The least common multiple of 188 and 204 is 9588. ;-)
Tomas
Perhaps try using a multiple of the packet size as your buffer size?
--
Mike Bourgeous
[EMAIL
The problem is that the register-level documentation on the frontend
chipset (Philips TDM1316L and TDA10045H) appears to be impossible to come
by. I have even dug up two data sheets from a russian website on the
TDA10045 and the VES9600, the two predecessors of the TDA10045H, but none
Hi,
I got recently involved in linux-dvb project,
seemed that everything was fine while compiling and installing
dvb-modules.(kernel 2.4.20 + linuxtv-dvb-driver 1.1.0-pre3)
the following is the output from
#lsmod
Module Size Used by
dvb-ttpci 302272 0 (unused)
26 matches
Mail list logo
