Can someone explain what's happening here with linux 2.6.7 and the
latest bttv driver from bytesex.org and my avermedia DVB-T card? It's
working but not well enough to set and forget.
Basically it's working, but it isn't reliable. Sometimes (eventually)
it will just stop tuning until the bttv
Kenneth Aafløy writes:
On Wednesday 21 July 2004 00:34, Ralph Metzler wrote:
[snip]
Alternative: get the i2c_adapter pointer via sub_device,
lock it, (in case of linuxtv driver, change i2c adapter name),
scan it for already present clients, init them,
How the
Gerd Knorr writes:
Alternative: get the i2c_adapter pointer via sub_device,
lock it, (in case of linuxtv driver, change i2c adapter name),
scan it for already present clients, init them,
How the initialization is done?
Via i2c client command calls. FE_REGISTER
Hi,
We've got a WinTV-NOVA-CI with a matrix reloaded cam card, the cam didn't work
at first. After some digging (adjust timeouts and stuff like that), i noticed
that the card was never reset during the initialisation. Adding a reset
made the card work :). Patch for this is attached.
Hello,
I have just booted under 2.6.8-rc2 which has some DVB/v4l change since
2.6.8-rc1 and I don't get audio/video anymore. The OSD works, I can zap
to any channel and receive the EPG. Also I can't play recordings made
earlyer...
My config for this kernel is to be found under :
[EMAIL PROTECTED] wrote:
I have just booted under 2.6.8-rc2 which has some DVB/v4l change since
2.6.8-rc1 and I don't get audio/video anymore. The OSD works, I can
zap to any channel and receive the EPG. Also I can't play recordings
made earlyer...
I have the same problem but only after
Kenneth Aafløy wrote:
On Wednesday 21 July 2004 01:25, Johannes Stezenbach wrote:
Kenneth Aafløy wrote:
On Tuesday 20 July 2004 21:08, Holger Waechtler wrote:
wouldn't it be better to replace the from-scratch list-and-device
handling in dvb_i2c.[hc] by the driver/bus infrastructure in 2.6 that
On Wed, Jul 21, 2004 at 10:20:54AM +0200, Ralph Metzler wrote:
Gerd Knorr writes:
So this part should be easy as the i2c_clients_command() helper function
(see i2c-core.c) does everything you need for that I think.
This does not solve the problem with the timing of registration and
Kenneth Aafløy wrote:
On Tuesday 20 July 2004 21:08, Holger Waechtler wrote:
well -- I still can't see the deep reason for this, the recent patches
usually added ~20-100 lines of code complexity to each file, so where is
the point of getting rid of something?
There wasn't that much complexity
On Wednesday 21 July 2004 14:18, Holger Waechtler wrote:
I have to admit that I didn't felt the urge to use this yet, but at a
first glance over the API everything looks good, pretty cleanly
implemented and provides all the power management and hotplug features
the current dvb_i2c and the
On Wed, Jul 21, 2004 at 01:34:28PM +0200, hgm.bg wrote:
I see no frontend. Are you sure you modprobe all frontends ?
See my .config :
CONFIG_DVB=y
CONFIG_DVB_CORE=y
CONFIG_DVB_VES1X93=y
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregoire Favre wrote:
| Hello,
|
| I have just booted under 2.6.8-rc2 which has some DVB/v4l change since
| 2.6.8-rc1 and I don't get audio/video anymore. The OSD works, I can zap
what v4l change?
maybe relevant:
[EMAIL PROTECTED]
[PATCH]
On Wed, Jul 21, 2004 at 06:18:44PM +0200, Thomas Schorpp wrote:
what v4l change?
From the patch :
patching file drivers/media/video/bttv-cards.c
patching file drivers/media/video/bttv-driver.c
patching file drivers/media/video/bw-qcam.c
patching file drivers/media/video/c-qcam.c
patching file
Hello,
I'm trying to get some facts about the infamous video data stream
broken error in VDR.
The following modified code from VDR-1.3.10/dvbdevice.c cDvbTuner::Action
active = true;
while (active) {
if (tunerStatus == tsTuned) {
fe_status_t status =
On Wed, Jul 21, 2004 at 07:31:36PM +0200, Wolfgang Fritz wrote:
Hello,
I'm trying to get some facts about the infamous video data stream
broken error in VDR.
The following modified code from VDR-1.3.10/dvbdevice.c cDvbTuner::Action
active = true;
while (active) {
On Wed, Jul 21, 2004 at 07:31:36PM +0200, Wolfgang Fritz wrote:
Hello,
I'm trying to get some facts about the infamous video data stream
broken error in VDR.
The following modified code from VDR-1.3.10/dvbdevice.c
cDvbTuner::Action
active = true;
while (active) {
Kenneth Aafløy wrote:
On Wednesday 21 July 2004 14:18, Holger Waechtler wrote:
I have to admit that I didn't felt the urge to use this yet, but at a
first glance over the API everything looks good, pretty cleanly
implemented and provides all the power management and hotplug features
the current
Wolfgang Fritz wrote:
Hello,
I'm trying to get some facts about the infamous video data stream
broken error in VDR.
The following modified code from VDR-1.3.10/dvbdevice.c cDvbTuner::Action
active = true;
while (active) {
if (tunerStatus == tsTuned) {
Kenneth Aafløy wrote:
On Wednesday 21 July 2004 14:18, Holger Waechtler wrote:
I have to admit that I didn't felt the urge to use this yet, but at a
first glance over the API everything looks good, pretty cleanly
implemented and provides all the power management and hotplug features
the current
On Wednesday 21 July 2004 21:36, Holger Waechtler wrote:
Kenneth Aafløy wrote:
Power management is provided through the dvb driver, and do you really
need to hotplug a frontend?
All current USB DVB drivers can get forced to oops the kernel if you
unplug the device in the wrong moment.
Holger Waechtler wrote:
one more point came to my mind: the 2.6 driver API provides a clean way
to upload demod firmware files, no need for dirty hacks and workarounds
and direct access of internal dvb_adapter or i2c_adapter struct members.
That's the whole point why we want to use
Hi all,
I have attached a patch to address a limitation of the OSD API.
Currently, the OSD API does not provide the ability to create many of
the window types supported by the av7110 OSD. I have implemented a
change in the OSD_Open command that will allow the creation of any
type of OSD window
22 matches
Mail list logo
