On Sat, Dec 20, 2003 at 08:12:37PM +0100, Michael Hunold wrote:
Hello Michael ;-)
> Did you successfully load the firmware, ie. is the card fully operational?
The two cards are perfectly working with VDR, so the answer should be
yes ;-)
> If so, and if you used the hotplug firmware scripts, the
Le 12/20/2003 08:04 PM, Michael Hunold a joliment écrit :
The vanilla 2.6.0 kernel does not contain the latest bunch of patches I
was speaking of. They will be part of 2.6.1.
You need to apply the 12 patches from "dvb-kernel/patches-2.6" -- these
contain the recent additions and the new documen
Hello Gregoire,
last problem solved in changing the order of the rmmod ;-)
I have still to learn why I don't see my cards in /sys/class/firmware/
Did you successfully load the firmware, ie. is the card fully operational?
If so, and if you used the hotplug firmware scripts, then the entry for
yo
Hello Nicolas,
All this is described in the new "Documentation/dvb" directory, please
read it.
I just download the kernel sources, but I don't find such a directory.
Did I miss something ?
The vanilla 2.6.0 kernel does not contain the latest bunch of patches I
was speaking of. They will be par
Le 12/20/2003 07:09 PM, Michael Hunold a joliment écrit :
All this is described in the new
"Documentation/dvb" directory, please read it.
I just download the kernel sources, but I don't find such a directory.
Did I miss something ?
Thanks. Nicolas.
--
Powered .~.
by Linux
Hello all,
I think all of you have noticed already that the official 2.6 Linux
kernel is out. It's the first kernel that officially contains the
LinuxTV.org DVB subsystem plus a variety of drivers for different DVB cards.
Thanks to everyone who contributed!
Because of the recent feature freeze
> The memcpy() issue should not be too hard to resolve, just never copy
> more than a complete section and reset the crc seed appropriatly. The
> performance impact should be negligible.
Alright, that's simple if it helps, I can just limit the memcpy range
to each one complete section with crc
Emard wrote:
Crc check can't be done there because the crc engine cannot access
system ram but only demux ram. memcopy wasn't used to always copy a
complete section before, but it didn't copy more than one section. A
quick grep shows me, that our driver is the only one available that uses
the hardw
> Any similar conditionals (i.e. they are checking for more than 3 bytes to
> calculate section length) also do not directly reject any data.
Hmmm... looking at the code I wasn't able to certainly tell so;
I was thinking it rejects some data and made an attempt to fix
that what I saw as rejection
Hello,
last problem solved in changing the order of the rmmod ;-)
I have still to learn why I don't see my cards in /sys/class/firmware/
Thank you very much,
Grégoire
http://magma.epfl.ch/greg ICQ:16624071 mailto:[
Michal Dobrzynski writes:
> I haven't been able to really do anything butt try and read about it
> (because my rev1.5 card has not arrived yet) but I really care about
> WSS support via the RGB out (or SVideo for that matter) of the card.
>
> It seems that this would have to be done by sett
Hello again,
my VDR has quit and my scrits should normally remove the driver and
reload then, but it doesn't seems to do it...
I have in syslog:
Dec 20 14:17:56 greg kernel: saa7146: unregister extension 'dvb'.
And if I try a lsmod it only show:
Module Size Used by
and don't goe
Hello,
I have patched my 2.6.0 with the 12 patches from
CVS/dvb-kernel/patches-2.6 and I have the
/usr/lib/hotplug/firmware/dvb-ttpci-01.fw
Everything seems to works, BUT:
ls /sys/class/firmware/ has only timeout in, nothing about my
2 Hauppauge DVB-s rev 1.3, why ?
Is that because of hotplug or
Emard writes:
> > > The old code is broken in boundary conditions, dropping some sections
> > > that should have been otherwise correctly received.
> >
> > Details?
>
> If e.g. one byte of new section starts at the last byte of TS packet,
> this section will not be received because the old
> Crc check can't be done there because the crc engine cannot access
> system ram but only demux ram. memcopy wasn't used to always copy a
> complete section before, but it didn't copy more than one section. A
> quick grep shows me, that our driver is the only one available that uses
> the hardware
Andreas Oberritter writes:
> [1 ]
> On Sat, 2003-12-20 at 01:06, Marcus Metzler wrote:
> > > I'd like to add this patch to dvb-kernel's linux/dvb/video.h, so
> > > userspace programs can adjust video system settings (PAL/NTSC) depending
> > > on the frame rate and video size. I think it wo
16 matches
Mail list logo
