Johannes Stezenbach wrote:
Holger Waechtler wrote:
struct dvb_atsc_parameters {
fe_modulation_t modulation;
/* anything more? maybe 8VSB or 16VSB? */
};
struct dvb_frontend_parameters {
__u32 frequency;
fe_spectral_inversion_t inversion;
union
I applied your proposed changes to the dvb-kernel CVS frontend.h file.
You probably also need to add a struct dvb_atsc_parameters atsc to
struct dvb_frontend_parameters parameter union, right?
It would then look like this:
struct dvb_atsc_parameters {
fe_modulation_t modulation;
Kenneth Aafløy wrote:
Hi!
I've sent this to Michael, but never got a reply (that's happened before), is
it just insane?
What really annoys me is that when I want to do a simple demuxing task, such
as harvesting all the PMT's, I have to set up a chain of fd's and do rotating
and stuff, to avoid
Roberto Ragusa wrote:
(BTW, typedefs are deprecated for kernel code (only allowed
for explicitly opaque data types)).
Until now, I've been contested:
1) "&buf" instead of "buf"
2) "//" comments
3) use of typedef
the funny part is that
1) I copied&pasted existing code
2) "//" comments are everywhe
Mac Michaels wrote:
I am the owner of a FunsionHDTV 3 Gold card. I have the
analog TV and audio working with my modificatons to the
CX88 driver. I am working on the Digital TV (HDTV ATSC) and
want to integrate it into DVB as I seems to be a good fit.
The FusionHDTV card produces a transport str
Johannes Stezenbach wrote:
Roberto Ragusa wrote:
OK, so I propose this:
- you use FE_SET_FRONTEND as usual
- then, you call FE_SET_AUTO_SEARCH passing something as
struct dvb_autosearch {
fe_autosearch_t parameter;
__u32 lower limit;
__u32 higher limit;
}
Gregoire Favre wrote:
On Tue, Aug 03, 2004 at 03:48:48PM +0200, Steffen Barszus wrote:
I would like to test the new dvb-kernel, but I also don't want to be
forced to have a different kernel source for each kernel as I can't
patch if with for example patch-2.6.8-rc1-rc2.bz2.
So my question : does so
Johannes Stezenbach wrote:
Roberto Ragusa wrote:
Holger Waechtler <[EMAIL PROTECTED]> wrote:
struct dvb_fe_scan_spec {
unsigned freq_start;
unsigned freq_end;
unsigned srate_start;
unsigned srate_end;
}
A similiar approach works for the mt352 DVB-T demod, the
Roberto Ragusa wrote:
On Mon, 02 Aug 2004 18:11:54 +0200
Holger Waechtler <[EMAIL PROTECTED]> wrote:
sounds hard to use. I would prefer the approach similiar to thy Zarlink
Evalsoftware: pass the frequency and symbol rate ranges to the driver
and then get interrupted/notified as soon som
Roberto Ragusa wrote:
Third idea: create our own hw independent ranges and define the
meaning of the bits (we could use 16 bit, for example).
Better, let decide that bit 31 means auto-sr and use 16 or 24
or 30 bits for ranges.That is:
if (bit31==0) (bit29-bit0)=symbol rate in baud
if (bit31==1)
Michael Hunold wrote:
Hi,
On 07/27/04 19:39, Oliver Endriss wrote:
On Tuesday 27 July 2004 19:20, Johannes Stezenbach wrote:
The new offical major number is 212. I've changed the sources
for dvb-kernel (dvbdev.h and MAKEDEV-DVB.sh). People who
don't use devfs will have to recreate their devices.
Johannes Stezenbach wrote:
Holger Waechtler wrote:
Oliver Endriss wrote:
On Tuesday 27 July 2004 19:20, Johannes Stezenbach wrote:
Hi,
I was just informed that LANANA has assigned an official
major number for DVB, so we don't have to use the "unoffical /
experimental use only" num
John Dalgliesh wrote:
On Tue, 27 Jul 2004, Holger Waechtler wrote:
Mac Michaels wrote:
I own a DViCO FusionHDTV 3 Gold card and am writing a
driver for it. I have modified the cx88 V4L2 driver to
almost work for NTSC-M. All video and tuner functions work,
no sound yet.
I want to write a driver
Stefan Grotehans wrote:
Holger Waechtler <[EMAIL PROTECTED]> schrieb am 27.07.04 21:16:05:
>
> John Dalgliesh wrote:
> > On Mon, 26 Jul 2004, Stefan Grotehans wrote:
> >>
> >>1) I implemented a new tuner type in stv0299.c. Since the new box
ver 2.2 has
John Dalgliesh wrote:
On Mon, 26 Jul 2004, Stefan Grotehans wrote:
1) I implemented a new tuner type in stv0299.c. Since the new box ver 2.2 has a
ALPS BSBE1
tuner. This tuner model has only two small differences to the BSRU tuner. However I
will need
Holgers's help to distinguesh between the ol
Martin Hammermüller wrote:
HI!
at firs: sorry my english is very (very,very...) bad! ;)
i have a terratec cinergy 1200 dvb-s card. with a saa7146. but it don't
work!
i've try it with:
- 2.4.20 kernel, linuxtv-dvb-1.1.1 and cvs version.
- 2.6.7 kernel with linuxtv-dvb-1.1.1
Please use a recent CVS
Roberto Ragusa wrote:
Hi,
frontends can currently return some information, such as BER,
STRENGTH, SNR. Every one of this values is assigned an ioctl
command.
I'm experimenting with getting more detailed info from one of
the frontends, by reading specific registers. Assuming I find
something interes
Oliver Endriss wrote:
On Tuesday 27 July 2004 19:20, Johannes Stezenbach wrote:
Hi,
I was just informed that LANANA has assigned an official
major number for DVB, so we don't have to use the "unoffical /
experimental use only" number 250 anymore.
Apparently the number was assigned months ago, just
Mac Michaels wrote:
I own a DViCO FusionHDTV 3 Gold card and am writing a
driver for it. I have modified the cx88 V4L2 driver to
almost work for NTSC-M. All video and tuner functions work,
no sound yet.
I want to write a driver for the ATSC transport stream. Is
DVB or V4L2 the best place to i
Hi Kenneth,
Kenneth Aafløy wrote:
On Friday 23 July 2004 20:06, you wrote:
that probably depends on the general plans regarding the current CVS
tree and the schedule for the v4 API.
If v4 is to be pushed to the public soonish then any work in the old
tree despite bugfixes and minor cosmetic changes
Petr Nejedly wrote:
Problem summary:
When running dvb-ttusb-budget driver on a mipsel platform with ohci, the
isochronous
USB buffers come back from the hcd driver untouched although the period
and size is probably OK.
Details:
I have Hauppage USB DVB-T. It works for me correctly on a PC (x86
n
Stefan Grotehans wrote:
Folks,
Holger's remarks are right!
Here is the status of my efforts:
1) I implemented a new tuner type in stv0299.c. Since the new box ver
2.2 has a ALPS BSBE1 tuner. This tuner model has only two small
differences to the BSRU tuner. However I will need Holgers's help to
Kenneth Aafløy wrote:
On Friday 23 July 2004 17:48, Holger Waechtler wrote:
Johannes Stezenbach wrote:
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
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 cu
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) {
fe_status
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 cu
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
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
John Dalgliesh wrote:
On Tue, 20 Jul 2004 [EMAIL PROTECTED] wrote:
I have bought a DVB-s of Technotrend USB, and have tried to install linuxtv.org
driver, but it does not work, dmesg give me:
...
ttusb_init_controller: unknown STC version V 2.2, please report!
...
No signal is found them from scan
Kenneth Aafløy wrote:
On Sun, Jul 18, 2004 at 01:04:02AM +0200, Kenneth Aafløy wrote:
On Sunday 18 July 2004 00:09, Ralph Metzler wrote:
No, I also considered this before implementing the FE_(UN)REGISTER
stuff but adapters with more than one I2C bus/frontend will not work
like this. It also makes t
Johannes Stezenbach wrote:
Holger Waechtler wrote:
Wolfram Joost wrote:
- .flags = I2C_M_NOSTART,
+ .flags = 0,
If I understand the MT352 spec right i2c read transfers from the MT352
have to get executed without STOP condition (this scenario is called
Michael Hunold wrote:
Hello Irek,
On 06/25/04 08:56, Irek Defee wrote:
It is strange that this issue has been downgraded comparing to kernel
2.4. For me it’s a huge factor not to upgrade to 2.6:).
The "problem" is that devfs in 2.4 has the "feature" that a device node
is not tightly coupled to a
Wolfram Joost wrote:
Hi,
it works on boards with hardware i2c enabled. Changing the I2C_M_NOSTART
to 0, as you did, is the right thing to do here.
Ahh, OK.
Please fix the i2c host driver to handle RESTART conditions properly
instead of introducing dirty hacks in the device drivers, these will
Wolfram Joost wrote:
Hi,
I updated the version on http://www.frokaschwei.net/avtv771/avermedia.html. I
changed Christopher Pascoe's patch because I don't want to disable the
recovery.
Wolfram
--- mt352.c.cvs 2004-06-28 20:
Aurelian Pop wrote:
On Wednesday 30 June 2004 16:25, Aurelian Pop wrote:
Hello,
First of all, let me apologize if I'm a little off-topic.
I would like to know with who should I talk about the details of including
the dvb-drivers into a rpm package having other commercial software too.
If (for any r
Wolfram Joost wrote:
Hi,
if i add:
r = mt352_read_register (i2c, 0x7f);
before:
r = mt352_read_register (i2c, 0x00);
the read of register 0x00 returns the same as the read of register 0x7f!
And it appears that the "snr" values from above are actually the value of
re
Jolse Maginnis wrote:
Hi,
I've purchased an AverMedia DVB-T 771, and I live in Tasmania,
Australia, but I can't seem to get it to tune anything in linux. It
works in winxp (I can tune nearly all the channels with my crap
aerial), so it's got to be the driver.
I'm using the patches from
http://www.f
Wolfram Joost wrote:
Hi,
btw: does anybody of you has an idea how we might make use of the
automatic channel scan functionality of the MT352 under Linux, how we
might need to extend the LinuxDVB API?
I would add two ioctls:
- FE_START_SCAN with the lowest and highest frequency to scan as paramter
Nathan Hand wrote:
Would have helped if I'd attached the patch.
manually applied to CVS. Can't test it though -- don't have a 2.6 kernel
installed here...
thanks for tracking this down; due to the well-working TPS autoprobing
we never had this problem here.
btw: does anybody of you has an idea
Johannes Stezenbach wrote:
Peter Urbanec wrote:
I wanted to check if there is any work being done by anyone on
supporting the Samsung/Zarlink MT-352 tuner/demodulator as used by a
number of recently released cards.
The Kworld V-Stream, DVico FusionHDTV and Avermedia A771 cards all seem
to be ba
Michael Hunold wrote:
Hello Hilmar,
On 03/31/04 11:11, Hilmar Linder wrote:
[...]
diff -ru linuxtv-dvb-apps-1.1.0/include/linux/dvb/net.h
linuxtv-dvb-apps-1.1.0-ULE/include/linux/dvb/net.h
--- linuxtv-dvb-apps-1.1.0/include/linux/dvb/net.h2004-01-17
17:59:46.0 +0100
+++ linuxtv-dvb-
On Sunday 21 March 2004 14:20, Rainer.scherg wrote:
> Hi,
>
> I have some questions to the frontend-info structure in the current
> dvb-api3:
>
> How are the following frequency-variables defined?
>
> --- snip ---
> 2.1.3 frontend information
>
> struct dvb_frontend_info {
> char name[128];
> f
On Monday 15 March 2004 00:27, Andrew de Quincey wrote:
>
> So there must still be a change in the av7110 code, which does the DISEQC
> on your card. As far as I can see none of the other changes to ves1x83
> should break anything. Just that there were _two_ driver issues here
> complicated the mat
On Monday 15 March 2004 00:10, Klaus Schmidinger wrote:
> Holger Waechtler wrote:
> > On Sunday 14 March 2004 23:55, Andrew de Quincey wrote:
> > > The problem with 1.1.0 is VDR isn't doing the full DISEQC init
> > > sequence, and so no voltage was ever being
On Monday 15 March 2004 00:13, Klaus Schmidinger wrote:
> Holger Waechtler wrote:
> >
> > The DiSEqC spec requires you to set the appropriate bus voltage before a
> > DiSEqC command is sent. It also requires that the old-style SEC and
> > DiSEqC commands are sent c
On Sunday 14 March 2004 23:55, Andrew de Quincey wrote:
>
> The problem with 1.1.0 is VDR isn't doing the full DISEQC init sequence,
> and so no voltage was ever being sent to the LNB.
that's definitely illegal.
Holger
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscrib
On Sunday 14 March 2004 23:45, Klaus Schmidinger wrote:
> Holger Waechtler wrote:
> >
> > As soon you submit the polarisation selection command (VOLTAGE_13V or
> > VOLTAGE_18V) you already powered up the LNB. The only important thing is
> > to maintain the delay time
On Sunday 14 March 2004 23:46, Andrew de Quincey wrote:
> On Sunday 14 March 2004 22:36, Holger Waechtler wrote:
> >
> > As soon you submit the polarisation selection command (VOLTAGE_13V or
> > VOLTAGE_18V) you already powered up the LNB. The only important thing is
>
On Sunday 14 March 2004 23:38, Klaus Schmidinger wrote:
>
> When I compiled the latest VDR developer version with the dvb-kernel
> header files, everything compiled just fine - so I would assume that there
> was no change in the API (besides, it has always been emphasized that the
> API did not cha
On Sunday 14 March 2004 23:35, Andrew de Quincey wrote:
> >
> > If you specify a bus voltage of 13 or 18V you definitely don't mean
> > VOLTAGE_OFF but expect the LNBP working, everything else is a bug.
>
> Yeah, it seemed to have changed from being set to VOLTAGE_13 in the
> initialisation tables
On Sunday 14 March 2004 23:22, Johannes Stezenbach wrote:
> Klaus Schmidinger wrote:
> > Johannes Stezenbach wrote:
> > > It doesn't make much sense to remove the power from the LNB
> > > while sending the DiSEqC sequence, but luckily vdr doesn't
> > > seem to do that ;-) So, I guess that 'v' is a
On Sunday 14 March 2004 13:11, Oliver Endriss wrote:
> On Sunday 14 March 2004 10:27, Robert Schlabbach wrote:
> > From: "Heino Goldenstein" <[EMAIL PROTECTED]>
> >
> > > Helmut Auer wrote:
> > > > These settings are not working for me, but the long version
> > > > from Oliver will:
> > > >
> > > >
On Sunday 14 March 2004 14:45, Andrew de Quincey wrote:
> On Sunday 14 March 2004 13:35, you wrote:
> > Andrew de Quincey wrote:
> > > > The two combinations below are working with the _unmodified_ ves1x93
> > > > code and also with my alps_bsvr2 mod.
> > > >
> > > > S13E11700 V 9750 v [E0 10
On Sunday 14 March 2004 23:02, Klaus Schmidinger wrote:
>
> > There are some mandatory delays before and after sending
> > the DiSEqC sequence. The Nokia API rolled all that in a simple
> > and convenient ioctl which would allow the driver to do
> > all the timing (so that applications cannot fuck
Oliver Endriss wrote:
On Monday 08 March 2004 21:34, Holger Waechtler wrote:
Ralph Metzler wrote:
Oliver Endriss writes:
And, unless there is a hardware or firmware CSA descrambler on the card, you
will never be able to decrypt pay-tv in a legal way.
IANAL, but I don't think
Ralph Metzler wrote:
Oliver Endriss writes:
> > Also: are there any
> > budget cards already that have drivers that support CAMs? I have to admit that
> > I don't know that.
>
> AFAIK there is _no_ budget card driver with CI support under linux.
No public and GPLed ones.
There are drivers for KN
Andrew de Quincey wrote:
I have done some more tests arount crl_bit() in ves1x93 with my Rev 1.3
DVB-S (ves1893). Realy only one "soft reset" is needed for this demod
(and
i think for the ves1993 too) to aquire lock. But the ves1893 needs some
short delay (according to the ves1893 appnote), up to
alve wrote:
moin,
is there any way to get a document describing the structure of mpeg
streams (especially ps) in detail (for example length of headers,
meaning of each bit in the headers) without paying 220 SFR to ISO? (or
can anyone send me the ISO documents for free...?)
The MPEG preview dra
Klaus Schmidinger wrote:
Holger Waechtler wrote:
Klaus Schmidinger wrote:
Holger Waechtler wrote:
...
calling the PES unpacking process a 'remuxing' is kind of flattered,
not? Forcing everybody to misuse the lowlevel-API instead of highlevel
access just because the av711x driver
Klaus Schmidinger wrote:
Holger Waechtler wrote:
Johannes Stezenbach wrote:
[EMAIL PROTECTED] wrote:
i am playing around with the DVR device for playing back a TS which
was recorded from the DVR device.
...
The kernel is configured a an SMP Kernel and Preemptible feature.
That's a r
Johannes Stezenbach wrote:
[EMAIL PROTECTED] wrote:
> i am playing around with the DVR device for playing back a TS which
> was recorded from the DVR device.
...
> The kernel is configured a an SMP Kernel and Preemptible feature.
That's a recipe for disaster -- the dvr playback code in the a
Johannes Stezenbach wrote:
Andrew de Quincey wrote:
On Wednesday 03 March 2004 17:06, Kelvin Woods wrote:
I'm sure I've read (on this list I believe) that after you tune your DVB
card with szap the card will lose the frequency after a few seconds.
This indeed is easily observable. If you d
Kieran Fulke wrote:
hi folks,
thought some of you might be interested to hear i have a wintv nova-t
pci card running inside a cobalt qube2. (mips cpu, UK dvb-t)
works nicely, and no problems at all. so i guess you can add
MIPS to the list of working targets.
wow, cool! do you use that thin
Andreas Share wrote:
Andrew de Quincey wrote:
Actually, the update_delay() is fine; its just that the TIMEOUT doesn't
take
into account how long it takes to write to the frontend itself... I put
in
some instrumentation, and its taking 25 jiffies to call
FE_SET_FRONTEND...
I've checked the front
[EMAIL PROTECTED] wrote:
Hi
I've got kernel 2.6.2 up and running with the drivers install and xine installed and
working ok, but apparently I need some device nodes for my card. I tried mknod -
m 0660 /dev/dvb/adapter0/video0c 250 but this didn't seem to work. Is there
anything else I have t
Andrew de Quincey wrote:
Hi, the first version of the new frontend stuff is coming along nicely. I have
a couple of remaining questions:
Why is there an FE_RESET ioctl immediately after the FE_SET_FRONTEND in
dvb_frontend_recover.. surely the frontend code itself should take care of
performing
Johannes Stezenbach wrote:
Andrew de Quincey wrote:
Well, the DVB API as specified by Nokia says that FE_SET_FRONTEND
should start tuning, and the result (failure or success) is relayed
to the application by means of an event with FE_GET_EVENT.
I.e. one FE_SET_FRONTEND -> one FE_GET_EVENT. But it'
Johannes Stezenbach wrote:
Holger Waechtler wrote:
Andrew de Quincey wrote:
If there _isn't_ a problem with breaking the Nokia API, I would be glad to
have a look.
If there is, all I have to do to fix my stuff is ignore the FE_TIMEDOUT
bit.
;) just remove it, it's bogus anyway
Bernd Bartmann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Stezenbach schrieb:
| Bernd Bartmann wrote:
|
|>Johannes Stezenbach schrieb:
|>| The home-grown firmware loader code in the various frontend drivers
|>| is problematic and should be replaced by request_firmware(). This
|>|
Guido Fiala wrote:
Am Sonntag, 15. Februar 2004 11:59 schrieb Robert Schlabbach:
From: "Scott White" <[EMAIL PROTECTED]>
I got spammed today to an Email address I have only had for 4 days
and only used on this list by a [EMAIL PROTECTED]
Just wanted to warn you to be careful as this list is obvio
Mattias Ernelli wrote:
I have problems installing the drivers for A Technotrend WinDVB-T 1300 card.
http://www.usa-x.org/1shop/images/t1300.jpg
I have tried several combinations of kernels and linuxtv-dvb driver
releases. The one that built properly on my system was linuxtv-dvb-1.1.0.
After resol
Johannes Stezenbach wrote:
Guido Draheim wrote:
Johannes Stezenbach wrote:
See README.bt8xx.
Hmmm, it still does not say how to go about it as a packager. As far as
I understand it one should not use dvb-bt8xx on a kernel without the
absolute latest fashion, so in 2.4.21 one should `rm dvb-bt8xx.
Johannes Stezenbach wrote:
Guido Draheim wrote:
here is a patch that will make `dvbscan` to list the series of
initial-data-files being installed in the system. It works on
all of /etc/dvb/dvb-?/* /usr/share/dvb/dvb-?/* and of course
that /usr/share/doc/packages/dvb/dvb-?/* ... it may help user
to
Johannes Stezenbach wrote:
Niklas Peinecke wrote:
Hernan A. Perez Masci wrote:
I've found a problem with skystar2 / mt312 modules (DVB version 1.1.0)
with the kernel 2.4.24.
Let's first insert the skystar2 module:
skynet:~# modprobe skystar2
skynet:~# lsmod
Module Size Used b
Pasi Kärkkäinen wrote:
Hello!
Attached is the initial-tuning-datafile for DVB-T Finland / Kuopio.
applied to CVS, module dvb-apps. Many thanks!
Holger
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Dave Chapman wrote:
After about two years of only working with the sourceforge CVS, I
thought I would make some official releases of dvbtune and dvbstream.
They available as part of the Sourceforge "dvbtools" project. The
download page is:
http://sourceforge.net/project/showfiles.php?group_id=
Johannes Stezenbach wrote:
Holger Waechtler wrote:
Johannes Stezenbach wrote:
Maybe Holger can comment on this?
Hmm, I did not followed the discussion, but your suggestions sound
plausible. Does anybody remembers why the offset has been changed?
Well, if *you* don't remember why *you* ch
Andrew G. Wilson wrote:
Any chance we could do a quick patch release with this change,
as I'm sure this will quickly become a FAQ otherwise.
you mean a dvbstream release?
Holger
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Niklas Peinecke wrote:
Hi,
attached is a small patch for cards.txt, wherein I added some details
about recently supported cards & frontends.
thanks, applied. Can you please send unified diffs next time
(cvs -q diff -pu)?
Holger
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "uns
Torbjörn Jansson wrote:
I have been trying to figure out why the windows software gets better signal
quality than the linux drivers on some channels.
There is a few things in ves1820.c, function tuner_set_tv_freq that I don't
understand.
The ifreq variable, is that the reference crystal on the sp56
Oliver Endriss wrote:
On Monday 09 February 2004 22:36, Max Nickel wrote:
On Mon, 2004-02-09 at 22:13, Johannes Stezenbach wrote:
On Mon, Feb 09, 2004 at 09:25:29PM +0100, Max Nickel wrote:
Hi,
it's me again. I still can't get the card to work properly. First of all
i have to say i had it workin
Pete Martin wrote:
Has anyone had experience of using the tda10045 based boards on some of the
higher frequency UHF channels? We are seing some problems and I was
wondering if this common, or if I should consider upgrading my drivers.
We have observed in Spain, where the upper channel is 66 which c
Norbert Schechner wrote:
Am Montag, 26. Januar 2004 15:11 schrieb Holger Waechtler:
Johannes Stezenbach wrote:
Holger Waechtler wrote:
we're preparing the 1.1.0 release in the CVS repository. In order to
avoid too many bugfix-releases I'd like to invite you to test the
release code be
Jussi Alanärä wrote:
On Mon, 2 Feb 2004, Torbjörn Jansson wrote:
In the syslog I get a line like: "DVB: VES1820(0): pwm=0x40"
I'll have to try changing it.
If this works, maybe a few lines in some readme file coud be
added to the
dvb drivers so that others that run into the same problem
atleast k
Torbjörn Jansson wrote:
Do you have one of the cards where the PWM value stored in
the card's
EEPROM needs to be overridden? I don't remember exactly for
which cards
this was required or improved things, maybe you want to check
the mail
archives or just try to override it using the 'pwm='
Torbjörn Jansson wrote:
I have tried again and move the dvb card to my windows machine and it works
much better, no bad reception and no channel tuning problems.
But I want it to work on linux and not windows.
Do you have one of the cards where the PWM value stored in the card's
EEPROM needs to be
Rob Shortt wrote:
Wolfgang Rohdewald wrote:
Hi,
Hi!
I want to use the Hauppauge remote connected to the Hauppage card. Is
this possible at all?
It sure is. I have done tonnes of searching, reading, hacking, and have
spend the last several hours getting my Hauppauge romote working with my
Rolf Fiedler wrote:
On Tuesday 27 January 2004 19:13, Andrew de Quincey wrote:
Hi, I've just committed the new tda1004x driver. This version supports the
TDA10046H as well now. Firmware file is the same as that for tda10045h BTW.
I've managed to get video streaming off my Nova-USB-t v2.1, but it s
Prakash K. Cheemplavam wrote:
Hi,
I just installed udev onto my gentoo distri. It seems the dvb (compiled
into kernel) devices in linux 2.6.2-rc2 don't appear in /sys as the
nodes don't appear in /dev. I just create them manually rigth now every
start up with the code ripped from makenapi or wh
[EMAIL PROTECTED] wrote:
No I hadn't recompiled the driver. I was hoping not to have to
(whenever I try to compile drivers it never seems to work properly,
almost certainly my fault though).
Under some circumstances (e.g. a 2.4 kernel without the ability to load
the firmware on request) the firmwa
[EMAIL PROTECTED] wrote:
Holger Waechtler <[EMAIL PROTECTED]> wrote :
[EMAIL PROTECTED]
wrote:
Koivisto Kimmo &lang=en">[EMAIL PROTECTED]>
wrote :
Hi
I've been reading various things about how to get a DVB card working,
and am know quite confused as to what is actua
[EMAIL PROTECTED] wrote:
Koivisto Kimmo <[EMAIL PROTECTED]> wrote :
Hi
I've been reading various things about how to get a DVB card working,
and am know quite confused as to what is actually required. I would like
to avoid having to compile a driver if at all possible (from reading
around
it se
Andreas Oberritter wrote:
Hi,
as we are living with this losless(?) section demux v1.4 since two
months now without having a solution for the broken memcopy and crc32
acceleration hooks, I propose to remove the possibility to use these
hooks completely to avoid confusion and do crc32 entirely in s
Mark Edwards wrote:
Thanks Gavin...
babyurl's installed, tested, and working...
I commited this version to CVS, file is now
dvb-kernel/linux/Documentation/dvb/avermedia.txt. Please let us know if
this was the wrong one...
Holger
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "
Juri Haberland wrote:
Juri Haberland wrote:
Holger Waechtler wrote:
Has somebody a card with ALPS TDLB7 and/or a USB box with TDMB7 handy
and can test these patches?
Will do so later this day (TDLB7).
Sorry, cannot test today, but as Jürgen already tested it, I think it's
not really nece
Arne Gellhaus wrote:
Holger Waechtler wrote:
we're preparing the 1.1.0 release in the CVS repository. In order to
avoid too many bugfix-releases I'd like to invite you to test the
release code before we'll put it on the website. To do so please do this:
does this driver work
Ralph Metzler wrote:
Johannes Stezenbach writes:
> > But the latter is probably the better interpretation of the API
> > intention and on the long term the only way I see to cleanly load
> > firmwares into MPEG decoders or DSPs in STBs without PCI or USB or i2c
> > bus (or any other bus with
Johannes Stezenbach wrote:
Holger Waechtler wrote:
As I read the device.h API it requires you to define a subsystem class -
in our case either 'i2c' or 'dvb'. 'i2c' would add again a dependency to
the kernel-i2c core, defining our own device class 'dvb&
Andrew de Quincey wrote:
On Wednesday 28 January 2004 16:21, Holger Waechtler wrote:
Andrew de Quincey wrote:
Hi, this patch is an example of how the changes to support
request_firmware might be done. I've only made the neccessary changes to
certain example devices. It probably won'
Holger Waechtler wrote:
Andrew de Quincey wrote:
I just spent a while trying to figure out how I would go about using
the 2.6 request_firmware() calls for the tda1004x driver. As far as I
can see, its impossible right now.
The problem is you have to pass a struct device* into
request_firmware
1 - 100 of 1213 matches
Mail list logo
