> * What is the current status of the driver?
Just a correction if using 2.4. bttv snapshot bttv9-20031009.tar.gz
has a problem, but bttv9-20031006.tar.gz worked OK for me.
brad had the following fix:
diff -urN bttv-0.9.12/bttv-if.c bttv-0.9.12.new/bttv-if.c
--- bttv-0.9.12/bttv-if.c 2003-
> > You apply the files in my tarball into the dvb-kernel stuff
> > you check out, until it is checked into CVS. We really are very close
> > to checking in.
Now checked in. You can get the driver if you get dvb-kernel from
CVS.
> * What is the current status of the driver?
Well, it works for me
Quoting Jamie Honan <[EMAIL PROTECTED]>:
> In general, the dvb-kernel CVS is the latest bleeding edge.
> It's not quite obvious where it is, but
> http://linuxtv.org/cgi-bin/cvsweb.cgi/
> shows how the check it out. I use the dvb-kernel tree.
>
> There are a bunch of apps in the DVB tree, for com
On Sunday 12 October 2003 16:30, Holger Waechtler wrote:
> Oliver Endriss wrote:
> > On Sunday 12 October 2003 10:35, Holger Waechtler wrote:
> >
> >>Oliver Endriss wrote:
> >>
> >>>The current implementation has a number of restrictions:
> >>>- Permissions of /proc/av7110_ir cannot be changed wit
> Can you give a bit more info on the Twinhan driver?
> What's the current status and where do I get the latest
> sources? Do you have the documentation on the I2C format?
>
> I'm pretty new to all this DVB stuff and I'm basically
> looking for a good starting point.
Holger mentions where I am
Juergen Sauer wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Sonntag, 12. Oktober 2003 12:23 schrieb Klaus Schmidinger:
>
> > > If I add a timer using the vdr menue the vdr destroys
> > > it's own timers.conf file, so that vdr crashes/quits,
>
> > Please keep very clearly apa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 12. Oktober 2003 12:23 schrieb Klaus Schmidinger:
> > If I add a timer using the vdr menue the vdr destroys
> > it's own timers.conf file, so that vdr crashes/quits,
> Please keep very clearly apart whether it _crashes_ or
> _quits_ - th
John Knottenbelt wrote:
Seppo,
Check in the kernel configuration menu:
"Code maturity level options"
and make sure that
"Select only drivers that don't need compile-time external firmware"
is NOT checked.
This should enable the tda1004x frontend module option in the DVB drivers
menu.
Thank
Wolfgang Fritz wrote:
Holger Waechtler wrote:
Oliver Endriss wrote:
[cut]
Additionally, I'd like to implement multiple keymaps per device.
A user might want to use different remote control units, which use the
same protocol but different device addresses. In this case we need
a keymap per devic
Holger Waechtler wrote:
> Oliver Endriss wrote:
>
[cut]
>
>>Additionally, I'd like to implement multiple keymaps per device.
>>A user might want to use different remote control units, which use the
>>same protocol but different device addresses. In this case we need
>>a keymap per device address
Seppo,
Check in the kernel configuration menu:
"Code maturity level options"
and make sure that
"Select only drivers that don't need compile-time external firmware"
is NOT checked.
This should enable the tda1004x frontend module option in the DVB drivers
menu.
On Sunday 12 October 2003 1
oh-ough, I should write my mails slower: s/\/here/g,
s/\/allocate/g. Hope that was all. sorry.
Holger Waechtler wrote:
Michael Hunold wrote:
In theory, you can write to user space memory from device drivers
easily. In practise, most hardware has some sort of DMA limitations
(for example 16k al
one more remark that came to my mind:
Holger Waechtler wrote:
Michael Hunold wrote:
But before thinking about this, someone should really investigate if
these memcpy()s are *really* a problem for system performance. Sure,
there is a lot of copying going on, but I guess that most of the
*real*
Michael Hunold wrote:
In theory, you can write to user space memory from device drivers
easily. In practise, most hardware has some sort of DMA limitations (for
example 16k aligned memory), so this is not an option unfortunately,
because you cannot control memory allocation for userspace.
even i
Ralph Metzler wrote:
Holger Waechtler writes:
> If we want to remove even more ambinguities we should distinguish in the
> demux API between general purpose filter banks and decoder-attached
> filter banks.
>
> Maybe this would even simplify using the API since the routing might get
> m
Hello Ralph,
> I like the idea of a source based routing in Michael's approach (we've
> been discussing this issue before in another thread some months ago),
> the idea not to specify input and output device of the demux but instead
> specify a stream source in the decoder. This removes som
Michael Hunold wrote:
Hello Holger,
I like the idea of a source based routing in Michael's approach (we've
been discussing this issue before in another thread some months ago),
the idea not to specify input and output device of the demux but
instead specify a stream source in the decoder. This
Michael Hunold wrote:
Please refer to the fundamental difference I desribed in my mail to Ralph:
Different demux devices with included filter capabilities suggest to the
user that there's hardware behind it. This is currently not the case for
any hardware out there.
It is. Whenever we implemente
Oliver Endriss wrote:
On Sunday 12 October 2003 10:35, Holger Waechtler wrote:
Oliver Endriss wrote:
The current implementation has a number of restrictions:
- Permissions of /proc/av7110_ir cannot be changed without recompiling
the driver, i.e. chown/chmod do not work.
- Only one keymap can be
On Sunday 12 October 2003 10:35, Holger Waechtler wrote:
> Oliver Endriss wrote:
> >
> > The current implementation has a number of restrictions:
> > - Permissions of /proc/av7110_ir cannot be changed without recompiling
> > the driver, i.e. chown/chmod do not work.
> > - Only one keymap can be
Hello Holger,
I like the idea of a source based routing in Michael's approach (we've
been discussing this issue before in another thread some months ago),
the idea not to specify input and output device of the demux but instead
specify a stream source in the decoder. This removes some ambingiut
"Flo G." wrote:
>
> Hi,
>
> I'm new to this list and subscribed, because i had the same error
> messages. The scan utility creates channel files with lines like these:
> ProSieben:12480:v:S19.2E:27500:255:256;257:32:0:898:1:0:0
> in the channels.conf delivered with vdr, i have:
> Pro-7:12480:v:S1
Hi,
I'm new to this list and subscribed, because i had the same error
messages. The scan utility creates channel files with lines like these:
ProSieben:12480:v:S19.2E:27500:255:256;257:32:0:898:1:0:0
in the channels.conf delivered with vdr, i have:
Pro-7:12480:v:S19.2E:27500:255:256;257:32:0:898
Hello Johannes,
> Ralph wrote:
Again, this depends on the hardware.
The current API V4 proposition basically treats each filter as if it
is a streaming device. For software filters this is no problem except
that DMA is probably out of the question. Some hardware only has two
recording devices whi
Hello Ralph,
> - specialized APID/VPID/PCR filters for each mpeg decoder (so they
> technically belong to the mpeg demux/decoder, not to the other demux
> devices)
But they do (I guess you are talking about NEC hardware?!).
Might be. ;-)
They have to be assigned to one of the demuxes and th
Hi,
if you tune to the "MPEG2 HD" service on ASTRA 19.2E, the arm will
crash immediately. :-(
Channel settings:
MPEG2 HD:12168:v:S19.2E:27500:308+8190:256,257:0:0:21100:0:0:0
I would not expect that the firmware can decode HDTV properly, but it
should not crash imho. Can this be fixed?
Oliver
Hi Dmitri,
Dmitri Katchalov wrote:
Hi Brad,
Can you give a bit more info on the Twinhan driver?
What's the current status and where do I get the latest
sources? Do you have the documentation on the I2C format?
I've got Twinhan VisionPlus DVB-T (terrestrial) card and
I'd like to make it work un
Quoting Brad Campbell <[EMAIL PROTECTED]>:
> Manu Abraham wrote:
> > Hi,
> >Could anyone tell me whether i require a dvb kernel for kernel
> > 2.6.0-test6/7 for a Visionplus(VP-1020) card from Twinhan to run ? If so
> > how can i use the card ?
> >
> > Regards,
> > Manu
>
> There is a dr
My TT Budget2-S seem to work with built-in DVB support in 2.6.0-test7.
However I can't enable build of tda1004x frontend module from "make
menuconfig". Is it a bug?
BR,
Seppo
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Juergen Sauer wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Moin,
> My vdr installation tends to crash by itself.
> I got my channels from the scan util (scan -o vdr) and
> pasted it to channels.conf.
>
> If I add a timer using the vdr menue the vdr destroys
> it's own timers.co
Oliver Endriss wrote:
The current implementation has a number of restrictions:
- Permissions of /proc/av7110_ir cannot be changed without recompiling
the driver, i.e. chown/chmod do not work.
- Only one keymap can be loaded for all devices.
What about loading keymaps using the ioctl interface of
31 matches
Mail list logo
