Re: [linux-dvb] Problem about mt2131 tuner
kevin liu wrote: > Yeah, I did this part of code already. > I design mt2131_set_tv_freq(struct i2c_client *cli, unsigned int > freq) function and I compile this part of code into tuner.ko just like > mt20xx code has done, > > static void mt2131_set_tv_freq(struct i2c_client *client, unsigned > int freqency) > If this is your function prototype, then you must be using much older v4l-dvb code. You'll have to use the most recent mercurial tip in order to use the new hybrid features after the recent tuner refactoring. [code snipped] > ++ > For mt2131, I use the same init parameters as in ATSC, and the > same algorithm for frequency parameters setting. > I can see the function correctly called when VIDIOC_S_FREQUENCY. > But my tv card's demod just can't get a valid NTSC IF signal. > So I suspect if mt2131 has different init params or different freq > set algorithm for NTSC. > Looks like you just copied the atsc code. I think you'll probably need to use slightly different settings in order to use NTSC instead of ATSC... Also, you probably have to handle a tda988x IF demod. Try using the latest mercurial tip and add analog support for mt2131 that way -- should be easier. Good Luck, Mike > On Nov 26, 2007 1:11 PM, Michael Krufky <[EMAIL PROTECTED]> wrote: > >> >> kevin liu wrote: >> >>> Dear: >>> In Linux DVB framework, mt2131 works for atsc tv mode. >>> But the problem is that can I use the same module when I want to see any >>> NTSC tv program? >>> >> mt2131 currently does not support analog television. All we need is to fill >> .set_analog_params, and call it from tuner-core.c, and then it can work. >> >> -Mike Krufky >> >> ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem about mt2131 tuner
Yeah, I did this part of code already.
I design mt2131_set_tv_freq(struct i2c_client *cli, unsigned int
freq) function and I compile this part of code into tuner.ko just like
mt20xx code has done,
static void mt2131_set_tv_freq(struct i2c_client *client, unsigned
int freqency)
{
struct tuner *t = i2c_get_clientdata(client);
struct mt2131_priv *priv = t->priv;
int ret, i = 0;
u32 freq;
u8 if_band_center;
u32 f_lo1, f_lo2;
u32 div1, num1, div2, num2;
u8 buf[12];
u8 lockval = 0;
u8 agcrst = 0;
freq = (freqency * 16) / 1000;
f_lo1 = freq + MT2131_IF1;
f_lo1 = (f_lo1 / 250) * 250;
f_lo2 = f_lo1 - freq - MT2131_IF2;
priv->frequency = (f_lo1 - f_lo2 - MT2131_IF2) * 1000;
num1 = f_lo1 * 64 / (MT2131_FREF / 128);
div1 = num1 / 8192;
num1 &= 0x1fff;
num2 = f_lo2 * 64 / (MT2131_FREF / 128);
div2 = num2 / 8192;
num2 &= 0x1fff;
if(freq <= 82500) if_band_center = 0x00; else
if(freq <= 137500) if_band_center = 0x01; else
if(freq <= 192500) if_band_center = 0x02; else
if(freq <= 247500) if_band_center = 0x03; else
if(freq <= 302500) if_band_center = 0x04; else
if(freq <= 357500) if_band_center = 0x05; else
if(freq <= 412500) if_band_center = 0x06; else
if(freq <= 467500) if_band_center = 0x07; else
if(freq <= 522500) if_band_center = 0x08; else
if(freq <= 577500) if_band_center = 0x09; else
if(freq <= 632500) if_band_center = 0x0a; else
if(freq <= 687500) if_band_center = 0x0b; else
if(freq <= 742500) if_band_center = 0x0c; else
if(freq <= 797500) if_band_center = 0x0d; else
if(freq <= 852500) if_band_center = 0x0e; else
if(freq <= 907500) if_band_center = 0x0f; else
if(freq <= 962500) if_band_center = 0x10; else
if(freq <= 1017500) if_band_center = 0x11; else
if(freq <= 1072500) if_band_center = 0x12; else
if_band_center = 0x13;
buf[0] = 0x01;
buf[1] = (num1 >> 5) & 0xff;
buf[2] = 0x02;
buf[3] = num1 & 0x1f;
buf[4] = 0x03;
buf[5] = div1;
buf[6] = 0x04;
buf[7] = (num2 >> 5) & 0xff;
buf[8] = 0x05;
buf[9] = num2 & 0x1f;
buf[10] = 0x06;
buf[11] = div2;
ret = mt2131_regs_write(t, buf, 12);
if(ret < 0){
mt2131_debug("change mt2131 frequency failed!\n");
}
mt2131_reg_write(t, 0x0b, if_band_center | 0xe0);
//reset mt2131 AGC
mt2131_reg_read(t, 0x15, &agcrst);
agcrst |= 0x40;
mt2131_reg_write(t, 0x15, agcrst);
while(i < 10){
mt2131_reg_read(t, 0x08, &lockval);
if((lockval & 0x88) == 0x88)
break;
mdelay(4);
i++;
}
mt2131_debug("tuner lock the signal on the specified frequency!\n");
if(i == 10)
mt2131_debug("Mt2131 tuner can't lock the signal %d\n", freqency);
++
For mt2131, I use the same init parameters as in ATSC, and the
same algorithm for frequency parameters setting.
I can see the function correctly called when VIDIOC_S_FREQUENCY.
But my tv card's demod just can't get a valid NTSC IF signal.
So I suspect if mt2131 has different init params or different freq
set algorithm for NTSC.
On Nov 26, 2007 1:11 PM, Michael Krufky <[EMAIL PROTECTED]> wrote:
>
>
>
> kevin liu wrote:
> > Dear:
> > In Linux DVB framework, mt2131 works for atsc tv mode.
> > But the problem is that can I use the same module when I want to see any
> > NTSC tv program?
>
>
> mt2131 currently does not support analog television. All we need is to fill
> .set_analog_params, and call it from tuner-core.c, and then it can work.
>
> -Mike Krufky
>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem about mt2131 tuner
kevin liu wrote: > Dear: > In Linux DVB framework, mt2131 works for atsc tv mode. > But the problem is that can I use the same module when I want to see any > NTSC tv program? mt2131 currently does not support analog television. All we need is to fill .set_analog_params, and call it from tuner-core.c, and then it can work. -Mike Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] SATELCO EasyWatch PCI DVB-T
Hi,
looks ok.
Please sign your patch ('Signed-off-by: ...')
The developer of a patch should also receive the credits. ;-)
CU
Oliver
Kim Sandberg wrote:
> Hi.
>
> Replying to myself.
>
> Created a simple patch and I got the card working. Seems to work ok
> under vdr with 1h of recording done.
> I got no idea of the names that should be used so just picked something
> similar.
>
> ---
> diff -u -r orig.v4l-dvb/linux/drivers/media/dvb/ttpci/budget-av.c
> v4l-dvb/linux/drivers/media/dvb/ttpci/budget-av.c
> --- orig.v4l-dvb/linux/drivers/media/dvb/ttpci/budget-av.c
> 2007-11-23 22:08:25.0 +0200
> +++ v4l-dvb/linux/drivers/media/dvb/ttpci/budget-av.c 2007-11-23
> 21:59:09.0 +0200
> @@ -913,6 +913,7 @@
> #define SUBID_DVBT_KNC1_PLUS 0x0031
> #define SUBID_DVBT_KNC10x0030
> #define SUBID_DVBT_CINERGY1200 0x1157
> +#define SUBID_DVBT_EASYWATCH 0x003a
>
> static void frontend_init(struct budget_av *budget_av)
> {
> @@ -1021,6 +1022,7 @@
> case SUBID_DVBT_KNC1:
> case SUBID_DVBT_KNC1_PLUS:
> case SUBID_DVBT_CINERGY1200:
> + case SUBID_DVBT_EASYWATCH:
> budget_av->reinitialise_demod = 1;
> fe = dvb_attach(tda10046_attach, &philips_tu1216_config,
> &budget_av->budget.i2c_adap);
> @@ -1248,6 +1250,7 @@
> MAKE_BUDGET_INFO(satewps, "Satelco EasyWatch DVB-S", BUDGET_KNC1S);
> MAKE_BUDGET_INFO(satewplc, "Satelco EasyWatch DVB-C", BUDGET_KNC1CP);
> MAKE_BUDGET_INFO(satewcmk3, "Satelco EasyWatch DVB-C MK3", BUDGET_KNC1C_MK3);
> +MAKE_BUDGET_INFO(satewt, "Satelco EasyWatch DVB-T", BUDGET_KNC1C_MK3);
> MAKE_BUDGET_INFO(knc1sp, "KNC1 DVB-S Plus", BUDGET_KNC1SP);
> MAKE_BUDGET_INFO(knc1cp, "KNC1 DVB-C Plus", BUDGET_KNC1CP);
> MAKE_BUDGET_INFO(knc1cmk3, "KNC1 DVB-C MK3", BUDGET_KNC1C_MK3);
> @@ -1272,6 +1275,7 @@
> MAKE_EXTENSION_PCI(satewps, 0x1894, 0x001b),
> MAKE_EXTENSION_PCI(satewplc, 0x1894, 0x002a),
> MAKE_EXTENSION_PCI(satewcmk3, 0x1894, 0x002c),
> + MAKE_EXTENSION_PCI(satewt, 0x1894, 0x003a),
> MAKE_EXTENSION_PCI(knc1c, 0x1894, 0x0020),
> MAKE_EXTENSION_PCI(knc1cp, 0x1894, 0x0021),
> MAKE_EXTENSION_PCI(knc1cmk3, 0x1894, 0x0022),
>
>
>
>
> > Hi.
> >
> > I bought a Satelco dvb-t card and it doesnt seem to be added to budget
> > drivers.
> >
> > kudzu -p tells me this:
> >
> > class: CAPTURE
> > bus: PCI
> > detached: 0
> > desc: "Philips Semiconductors SAA7146"
> > vendorId: 1131
> > deviceId: 7146
> > subVendorId: 1894
> > subDeviceId: 003a
> > pciType: 1
> > pcidom:0
> > pcibus: 0
> > pcidev: a
> > pcifn: 0
> >
> >
> > I couldnt find the 003a device id any of the sources.
> >
> > Any hint what to try as many of the similar cards are working ok.
> >
> > Card info:
> > http://www.dvbshop.net/product_info.php/info/p312_SATELCO-EasyWatch-PCI-DVB-T--Basic-Edition-.html
> >
> >
> > Br,
> > Kim Sandberg
> >
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
--
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] saa7146 vpeirq
Simeon Walker wrote:
> Hi,
>
> Since upgrading to Ubuntu Gutsy (kernel 2.6.22) I see a lot of these
> messages and the stream is badly corrupted:
>
> saa7146 (0) vpeirq: used 2 times >80%% of buffer (61476 bytes now)
Basically this message means that the interrupt handler is executed very
late. As a workaround you might try to increase the DMA buffer size
('bufsize' module parameter of budget-core).
> The card is an old Win TV Nova-T.
>
> Reverting to 2.6.20 is ok but I would like to be able to use the
> latest dvb-usb drivers for another card. I tried yesterdays v4l-dvb
> checkout which showed the same problems.
Hm - did you test the checkout with the 2.6.20 kernel?
(Just to find out whether it is the driver's fault or the kernel's.)
CU
Oliver
--
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem about mt2131 tuner
Dear: In Linux DVB framework, mt2131 works for atsc tv mode. But the problem is that can I use the same module when I want to see any NTSC tv program? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Review] Multiproto tree
Manu Abraham wrote:
> Oliver Endriss wrote:
> > Card drivers (budget-ci, budget-av)
> > ---
> > I didn't check the details, but the extensions look ok.
> > You might consider whether parts of the stb0899/stb6100 stuff could be
> > factored out into a header file. See bsru6.h for an example.
> > It would reduce the file size, and tables etc could be reused.
>
> I did visit this, but there result looked thus, the device is not specific to
> a tuner
> as it is, and in each of the card configurations, the tables do have some
> changes
> It depends on the card manufacturer.
>
> Thinking thus, i thought of moving all the tables to a header where,
> something
> such as stb0899_config.h where all the card specific tables are thrown in.
> This
> doesn't reduce any of the compiled object size, but it does bring in the
> advantage
> that budget_ci.c, budget_av.c are not cluttered with large tables.
>
> What do you think of moving all the config's to a public config file ?
Fine. Imho we should focus on maintainability, not on object size.
Maintainer's time is the most valuable ressource. Having the configs in
a central file makes it easier to reuse the tables and to keep them
in-sync.
Otherwise someone would probably just copy/paste the stuff for a new
driver, as it was done in the ttpci driver family. There are tons of
config tables which should be cleaned up and (possibly) merged.
Due to lack of hardware and/or testers this is nearly impossible now
without risking to break a driver... :-(
> >
> >
> > + /* Legacy */
> > + if (fe->legacy) {
> > + if (fe->ops.set_frontend)
> > + fe->ops.set_frontend(fe, &fepriv->parameters);
> > + } else {
> > +// if ((dvbfe_sanity_check(fe) == 0)) {
> > + /* Superseding */
> > + if (fe->ops.set_params)
> > + fe->ops.set_params(fe, &fepriv->fe_params);
> > +// } else
> > +// return -EINVAL;
> > + }
> >
> > Sanity checks should be done in FE_SET_FRONTEND/DVBFE_SET_PARAMS ioctls.
> > (See HG master where I added this some time ago.)
> > Otherwise the application would not see an error status.
>
> Since you already have a check, i guess i can drop the dvbfe_sanity_check()
Yep. Feel free to add more checks to dvb_frontend_check_parameters().
Atm it only checks the limits of frequency and symbol rate.
> >/* don't actually do anything if we're in the LOSTLOCK state,
> > -* the frontend is set to FE_CAN_RECOVER, and the max_drift is 0 */
> > - if ((fepriv->state & FESTATE_LOSTLOCK) &&
> > - (fe->ops.info.caps & FE_CAN_RECOVER) && (fepriv->max_drift ==
> > 0)) {
> > - dvb_frontend_swzigzag_update_delay(fepriv, s & FE_HAS_LOCK);
> > - return;
> > +* the frontend is set to FE_CAN_RECOVER, and the max_drift is 0
> > +*/
> > + /* Legacy */
> > + if (fe->legacy) {
> > + if ((fepriv->state & FESTATE_LOSTLOCK) &&
> > (fepriv->max_drift == 0)) {
> > + if (fe->ops.get_frontend_algo)
> > + if (fe->ops.get_frontend_algo(fe) ==
> > DVBFE_ALGO_RECOVERY)
> > +
> > dvb_frontend_swzigzag_update_delay(fepriv, s & FE_HAS_LOCK);
> > +
> > + return 0;
> > + }
> > + } else {
> > + if (fepriv->state & FESTATE_LOSTLOCK) {
> > + if (fe->ops.get_frontend_algo) {
> > + if ((fe->ops.get_frontend_algo(fe) ==
> > DVBFE_ALGO_RECOVERY) &&
> > + (fepriv->max_drift == 0)) {
> > +
> > +
> > dvb_frontend_swzigzag_update_delay(fepriv, s & DVBFE_HAS_LOCK);
> > + return 0;
> > + }
> > + }
> > + }
> > }
> >
> > The 'if (fe->legacy)' branch looks broken:
> > fe->ops.get_frontend_algo is most likely zero, so
> > dvb_frontend_swzigzag_update_delay will not be called for old drivers.
> >
>
> This one's fixed although i see no usage of FE_CAN_RECOVER which is used in
> the
> tree currently, rather than bogus usage
>
> > Finally, I did a quick test with this tree, and it worked. ;-)
> > - dvb-ttpci driver with DVB-S Rev 1.3 (ves1x93)
> > - budget driver with DVB-S Nova Rev 1.0 (stv0299)
> > - VDR (using old API)
>
> Marco pointed to another bug a wrong copy, which breaks backward compatibility
> for DVBFE_GET_PARAMS
>
> Any further issues that you see ?
No.
> Additionally i did work upon the Multiple TS stuff, haven't got it working
> yet.
> The concept works like this, unlike what we thought would be:
>
> Manu,
>
> The filtering is just like an IP address and subnet mask.
> ISI_ENTRY equivalent to IP add
[linux-dvb] LifeView TV Walker Twin DVB-T (LR540)
I just brought one of these and am testing - several lockups so far :) For the wiki page (http://linuxtv.org/v4lwiki/index.php/LifeView_TV_Walker_Twin_DVB-T_(LR540)#People_who_own_such_a_device) there is an experiment branch (http://linuxtv.org/hg/~aapot/m920x). Is that still current? - last edit was 6 months ago, or is it all merged into the trunk now? Thanks, lindsay -- Lindsay http://members.optusnet.com.au/~blackpaw1/album/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvbloop - A virtual DVB adapter
Hello Steven, Steven Toth wrote: > Exposing an input to the kernel demux via userspace doesn't sound like a > bad idea. It would certainly allow developers to build DVB/ATSC > applications without having access to live feeds, instead using canned > loops provided by who-ever. > > Any reason why this feature (not necessarily this specific patch) > couldn't be part of the regular v4l-dvb tree? I think the feature you want is already available. You can write a TS to dvr0. What makes dvbloop different is that it provides a virtual adapter (which might also be useful). Regards, Andreas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] CAM inserted/used reduces signal and SNR ?
Luc Brosens wrote: > Manu, > > your guess is correct, under W2K no tuning problems. The scrambled channels > tune in an instance, now and then there are some artifacts though. But > tuning works ! > > so my hardware setup works, now how to find that 'tenderness' in the driver ? > You think that the tuning-part of the drivers (that would be the > STV0299-stuff wouldn't it ?) It can be the STV0299 + the tuner on it. What tuner do you have on the card ? Maybe it is bad tuner programming, before looking elsewhere. Tuners wrongly programmed cause such weird issues, one can say. > > if somebody can set me off in the right direction, I'll get it solved > > the Windows TV-viewer that came with the cards reports a signal of 95%, even > for scrambled channels : another indication that tuning could be done a > bit better ? > > Luc > Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvbloop - A virtual DVB adapter
Luc Brosens wrote: > would this enable me to descramble a recording made without a CAM ? I have > two cards, but of course only the single CAM, and would like to be able to > store recordings without unscrambling using the card-without-CAM and > afterwards descramble them using the CAM (which of course is fully paid for > and > entitles me to do this) Well you can't do this with the onboard CAM on any DVB card. You can do the same with a normal SoftCAM in userland alone, without any gimmicks Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Review] Multiproto tree
Oliver Endriss wrote:
> Hi,
>
> now we had bad weather, and I had some time to review the code. ;-)
>
>
Had an unstable link last week, got fixed.
> General note
>
> Obviously, the multiproto tree has not been updated from master for a
> very long time. When merging care must be taken that no regressions flow
> back to the main development tree.
>
> For now I ignored all differences, except for:
> - frontend.h
> - dvb_frontend.[ch]
> - budget-ci.c
> - budget-av.c
>
>
> API extensions (frontend.h)
> ---
> looks fine
>
>
> Card drivers (budget-ci, budget-av)
> ---
> I didn't check the details, but the extensions look ok.
> You might consider whether parts of the stb0899/stb6100 stuff could be
> factored out into a header file. See bsru6.h for an example.
> It would reduce the file size, and tables etc could be reused.
>
I did visit this, but there result looked thus, the device is not specific to a
tuner
as it is, and in each of the card configurations, the tables do have some
changes
It depends on the card manufacturer.
Thinking thus, i thought of moving all the tables to a header where, something
such as stb0899_config.h where all the card specific tables are thrown in. This
doesn't reduce any of the compiled object size, but it does bring in the
advantage
that budget_ci.c, budget_av.c are not cluttered with large tables.
What do you think of moving all the config's to a public config file ?
>
> dvb-core: dvb_frontend.c
>
> fe->legacy is turned on/off by various ioctls:
> - FE_SET_FRONTEND, FE_GET_FRONTEND -> 1
> - DVBFE_SET_PARAMS -> 0/1
> - DVBFE_GET_PARAMS, DVBFE_GET_DELSYS, DVBFE_GET_INFO -> 0
>
> fe->legacy controls how the frontend thread works.
>
> Since the frontend device can be accessed by multiple readers,
> fe->legacy might be toggled in funny ways.
> This might confuse the fe thread or dvb_frontend_add_event. ;-(
Fixed.
> Imho ioctls should not set fe->legacy. All parameter conversions should
> be done within the ioctl. For example:
> - new driver: FE_SET_FRONTEND converts parms to new driver API
> - old driver: DVBFE_SET_PARAMS converts parms to old driver API
>
> Then the fe thread can simply use the old driver interface
> (fe->legacy==1) or the new one (fe->legacy==0).
>
>
> The error msg should display the offending parameter:
> Instead of
> + printk("%s: Unsupported FEC\n", __func__);
> you might use
> + printk(KERN_ERR "%s: Unsupported FEC %x\n", __func__,
> new_fec);
> (same way for other conversion routines)
Done
>
>
> + /* Legacy */
> + if (fe->legacy) {
> + if (fe->ops.set_frontend)
> + fe->ops.set_frontend(fe, &fepriv->parameters);
> + } else {
> +// if ((dvbfe_sanity_check(fe) == 0)) {
> + /* Superseding */
> + if (fe->ops.set_params)
> + fe->ops.set_params(fe, &fepriv->fe_params);
> +// } else
> +// return -EINVAL;
> + }
>
> Sanity checks should be done in FE_SET_FRONTEND/DVBFE_SET_PARAMS ioctls.
> (See HG master where I added this some time ago.)
> Otherwise the application would not see an error status.
Since you already have a check, i guess i can drop the dvbfe_sanity_check()
>/* don't actually do anything if we're in the LOSTLOCK state,
> -* the frontend is set to FE_CAN_RECOVER, and the max_drift is 0 */
> - if ((fepriv->state & FESTATE_LOSTLOCK) &&
> - (fe->ops.info.caps & FE_CAN_RECOVER) && (fepriv->max_drift == 0))
> {
> - dvb_frontend_swzigzag_update_delay(fepriv, s & FE_HAS_LOCK);
> - return;
> +* the frontend is set to FE_CAN_RECOVER, and the max_drift is 0
> +*/
> + /* Legacy */
> + if (fe->legacy) {
> + if ((fepriv->state & FESTATE_LOSTLOCK) && (fepriv->max_drift
> == 0)) {
> + if (fe->ops.get_frontend_algo)
> + if (fe->ops.get_frontend_algo(fe) ==
> DVBFE_ALGO_RECOVERY)
> +
> dvb_frontend_swzigzag_update_delay(fepriv, s & FE_HAS_LOCK);
> +
> + return 0;
> + }
> + } else {
> + if (fepriv->state & FESTATE_LOSTLOCK) {
> + if (fe->ops.get_frontend_algo) {
> + if ((fe->ops.get_frontend_algo(fe) ==
> DVBFE_ALGO_RECOVERY) &&
> + (fepriv->max_drift == 0)) {
> +
> +
> dvb_frontend_swzigzag_update_delay(fepriv, s & DVBFE_HAS_LOCK);
> + return 0;
> + }
> + }
> + }
> }
>
> The 'if (fe->legacy)' branch looks broken:
> fe->ops.get_frontend_algo is mo
Re: [linux-dvb] dvbloop - A virtual DVB adapter
Christian Prähauser wrote: > Steven Toth wrote: >> Exposing an input to the kernel demux via userspace doesn't sound like >> a bad idea. It would certainly allow developers to build DVB/ATSC >> applications without having access to live feeds, instead using canned >> loops provided by who-ever. >> >> Any reason why this feature (not necessarily this specific patch) >> couldn't be part of the regular v4l-dvb tree? >> >> - Steve > Hello Steve! > > If desired, I could provide an updated version of dvbloop (with a few > bugfixes and adaptations to current kernel/v4ldvb version) during the > next days. I would actually love to see such a thing merged into the kernel. Please do post your patch -- I hope that others would agree with me, and would like to see this functionality added to the kernel. :-) Cheers, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvbloop - A virtual DVB adapter
Luc Brosens wrote: > Christian Prähauser wrote: > >> Hello Jean! >> Thanks for the hint. The server is now back online! >> >> Cheers, >> Christian. >> >> Jean-Claude Repetto schrieb: >> >>> Christian Praehauser wrote : >>> >>> I wrote a Linux kernel module which provides one or more virtual DVB adapters. When loaded, it creates a char device of the form /dev/dvbloop for every virtual DVB adapter. All Transport Stream packets written to a char device will be delivered on the corresponding virtual DVB adapter. You can get the sources at http://cpn.dyndns.org/projects/dvbloop.shtml. >>> Hello, >>> >>> This site seems to be down. Can I download this module from another >>> site, or is there another way to send a file containing a TS stream to >>> the DVB drivers ? >>> >>> Thanks, >>> Jean-Claude >>> >> > > Christian, > > would this enable me to descramble a recording made without a CAM ? I have > two cards, but of course only the single CAM, and would like to be able to > store recordings without unscrambling using the card-without-CAM and > afterwards descramble them using the CAM (which of course is fully paid for > and > entitles me to do this) > > by the way, the site is down again > if you want, you can send me the sources by mail > I'd also be happy to host the sources for you on my website, if you want > > thanks, > > Luc > Hello Luc! Interesting idea to use dvbloop for viewing scrambled TS recordings! As I do not have much experience with the CA system in Linux-DVB, please give me a few days to check whether and how this could be done. Thanks for kind invitation to host dvbloop. It seems that my apache does not like working 24h a day ;-). From now on, I'll keep an eye on it. However, if problems continue, I may come back to your offer so that we've sort of a mirror for dvbloop. Cheers, Christian. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvbloop - A virtual DVB adapter
Steven Toth wrote: > > I wrote a Linux kernel module which provides one or more virtual > DVB adapters. When loaded, it creates a char device of the form > /dev/dvbloop for every virtual DVB adapter. All Transport > Stream packets written to a char device will be delivered on the > corresponding virtual DVB adapter. > > You can get the sources at > http://cpn.dyndns.org/projects/dvbloop.shtml. > Hello, This site seems to be down. Can I download this module from another site, or is there another way to send a file containing a TS stream to the DVB drivers ? Thanks, Jean-Claude >>> >> >> Christian, >> >> would this enable me to descramble a recording made without a CAM ? I >> have two cards, but of course only the single CAM, and would like to >> be able to >> store recordings without unscrambling using the card-without-CAM and >> afterwards descramble them using the CAM (which of course is fully >> paid for and >> entitles me to do this) >> >> by the way, the site is down again >> if you want, you can send me the sources by mail >> I'd also be happy to host the sources for you on my website, if you want > > Mauro, > > Exposing an input to the kernel demux via userspace doesn't sound like > a bad idea. It would certainly allow developers to build DVB/ATSC > applications without having access to live feeds, instead using canned > loops provided by who-ever. > > Any reason why this feature (not necessarily this specific patch) > couldn't be part of the regular v4l-dvb tree? > > - Steve Hello Steve! If desired, I could provide an updated version of dvbloop (with a few bugfixes and adaptations to current kernel/v4ldvb version) during the next days. Cheers, Christian. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Any improvment in the HVR-4000 front ?
On Sun, Nov 25, 2007 at 05:47:07PM +0300, Igor Nikanov wrote: Hello :-) > yes, there's some news. I'm using 4x1 diseqc switch and we together with > Darron have tried to find the > solution for diseqc-problem & hvr4000. That's why on > http://dev.kewl.org/hvr4000/ you can find several > patches. > But this patches couldn't decide the diseqc-problem. Today I have found the > variant when the diseqc > switch worked properly. I disconnected from AA and AB input my two LNB and > connected them to BA and BB. > After that the diseqc started to work properly. I recommend to you make the > same actions and to try. I have a diseqc with four input, and I only use 3 of them, so I think it's alsmost the same as your's. It's also works fine under windows, and my others cards with similar diseqc works just fine so. The weather here is not good enough to try to switch the cable :-) This card is really hard to make work... Thank for the update. -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] szap2 & snr/signal (hvr4000)
Hi I'm using szap2 from http://dev.kewl.org/hvr4000/ is it possible to apply the dB for signal and snr ? why for snr/ber/unc I can see only zero ? ./szap2 -c 60e -n1 -t0 -mq reading channels from file '60e' zapping to 1 'Kuban-RTV': sat 2, frequency = 11490 MHz V, symbolrate 5787000, vpid = 0x0064, apid = 0x0065 sid = 0x0001 (fec = -2147483648, mod = 2) Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' --> Using 'Conexant CX24116 DVB-S' DVB-S diseqc: sat_no:2 pol_vert:1 hi_band:0 cmd:e0 10 38 f8 wait:0 do_tune: API version=2, delivery system = 0 do_tune: Frequency = 174, Srate = 5787000 (DVB-S) do_tune: Frequency = 174, Srate = 5787000 (SET_PARAMS) status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal | snr | ber | unc | FE_HAS_LOCK status 03 | signal | snr | ber | unc | status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b333 | snr | ber | unc | FE_HAS_LOCK status 1f | signal b333 | snr | ber | unc | FE_HAS_LOCK status 1f | signal b333 | snr | ber | unc | FE_HAS_LOCK status 1f | signal b333 | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b333 | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK status 1f | signal b4cc | snr | ber | unc | FE_HAS_LOCK ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvbloop - A virtual DVB adapter
I wrote a Linux kernel module which provides one or more virtual DVB adapters. When loaded, it creates a char device of the form /dev/dvbloop for every virtual DVB adapter. All Transport Stream packets written to a char device will be delivered on the corresponding virtual DVB adapter. You can get the sources at http://cpn.dyndns.org/projects/dvbloop.shtml. >>> Hello, >>> >>> This site seems to be down. Can I download this module from another >>> site, or is there another way to send a file containing a TS stream to >>> the DVB drivers ? >>> >>> Thanks, >>> Jean-Claude >> > > Christian, > > would this enable me to descramble a recording made without a CAM ? I have > two cards, but of course only the single CAM, and would like to be able to > store recordings without unscrambling using the card-without-CAM and > afterwards descramble them using the CAM (which of course is fully paid for > and > entitles me to do this) > > by the way, the site is down again > if you want, you can send me the sources by mail > I'd also be happy to host the sources for you on my website, if you want Mauro, Exposing an input to the kernel demux via userspace doesn't sound like a bad idea. It would certainly allow developers to build DVB/ATSC applications without having access to live feeds, instead using canned loops provided by who-ever. Any reason why this feature (not necessarily this specific patch) couldn't be part of the regular v4l-dvb tree? - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] problem with stb0899: delivery system is zero
Hi, I installed manus driver. Everytime I want to scan for channels, it complains about the delivery system. stb0899_read_status: Unsupported delivery system: 0 I added a parameter to print the actual value: dprintk(verbose, FE_DEBUG, 1, "Unsupported delivery system: %X", state->delsys); is this correct? this is what I have done: cd /usr/src apt-get source linux-image-2.6.22-14-generic ln -s linux-source-2.6.22-2.6.22 linux wget http://linuxtv.org/hg/~manu/stb0899/archive/tip.tar.bz2 tar xjf stb0899-5b19ac1cddb5.tar.bz2 cd stb0899-5b19ac1cddb5 make xconfig # switched off a lot of modules make make install modprobe stb6100 modprobe stb0899 modprobe lnbp21 modprobe saa7146 modprobe budget-ci My software - ubuntu 7.10 64bit - kaffeine My hardware - Technotrend S2-3200. - Nvidia 8600GT - Athlon X2 4400 any idea what I could do next? thanks in advance JPT -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Any improvment in the HVR-4000 front ?
Hello, > anything new ? yes, there's some news. I'm using 4x1 diseqc switch and we together with Darron have tried to find the solution for diseqc-problem & hvr4000. That's why on http://dev.kewl.org/hvr4000/ you can find several patches. But this patches couldn't decide the diseqc-problem. Today I have found the variant when the diseqc switch worked properly. I disconnected from AA and AB input my two LNB and connected them to BA and BB. After that the diseqc started to work properly. I recommend to you make the same actions and to try. So, I have other disecs switch 2x1 - with it the diseqc-problem there's. Both diseqc switches normally operating in dreambox 7000, TT2300, and with hvr4000 under Windows (WinTV 4.0). Here http://allrussian.info/thread.php?threadid=87371&page=4&sid=bea433aec2767682dd178b2425ea6a3b you can find the oscillogramm with diseqc commands. regards Igor ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dvb-t network downlink and dvb-h
hi, found new transponder in vienna (59400) dvbnet pidscan gives - Transponder PID-Scan... - PID found:0 (0x) [SECTION: Program Association Table (PAT)] PID found:2 (0x0002) PID found: 16 (0x0010) [SECTION: Network Information Table (NIT) - actual network] PID found: 17 (0x0011) [SECTION: Service Description Table (SDT) - actual transport stream] PID found: 20 (0x0014) [SECTION: Time Date Table (TDT)] PID found: 21 (0x0015) [SECTION: ITU-T Rec. H.222.0|ISO/IEC13818 reserved] PID found: 32 (0x0020) PID found: 117 (0x0075) [unknown] PID found: 179 (0x00b3) [SECTION: Program Map Table (PMT)] PID found: 180 (0x00b4) [SECTION: Program Map Table (PMT)] PID found: 181 (0x00b5) [SECTION: Program Map Table (PMT)] PID found: 182 (0x00b6) [SECTION: Program Map Table (PMT)] PID found: 183 (0x00b7) [SECTION: Program Map Table (PMT)] PID found: 184 (0x00b8) [SECTION: Program Map Table (PMT)] PID found: 185 (0x00b9) [SECTION: Program Map Table (PMT)] PID found: 186 (0x00ba) [SECTION: Program Map Table (PMT)] PID found: 187 (0x00bb) [SECTION: Program Map Table (PMT)] PID found: 188 (0x00bc) [SECTION: Program Map Table (PMT)] PID found: 189 (0x00bd) [SECTION: Program Map Table (PMT)] PID found: 190 (0x00be) [SECTION: Program Map Table (PMT)] PID found: 191 (0x00bf) [SECTION: Program Map Table (PMT)] PID found: 224 (0x00e0) PID found: 256 (0x0100) PID found: 1096 (0x0448) PID found: 1110 (0x0456) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1120 (0x0460) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1130 (0x046a) [SECTION: MPE-FEC Table (MFT)] PID found: 1140 (0x0474) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1160 (0x0488) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1161 (0x0489) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1170 (0x0492) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1172 (0x0494) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1174 (0x0496) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1175 (0x0497) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1180 (0x049c) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 1200 (0x04b0) [SECTION: IP/MAC Notification Table (INT) [EN 301 192]] PID found: 1201 (0x04b1) [SECTION: DSM-CC - private data section // DVB datagram] PID found: 8191 (0x1fff) some ideas how to play this streams (btw. streams from captured data?) there are some linux apps for playing radio streams, can kaffeine do this? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MSI DigiVOX mini II v2.0
Markus Rechberger wrote: > On 11/10/07, pat <[EMAIL PROTECTED]> wrote: >> Hello, >> >> I've searched for information about *subject* and found that there's not a >> driver for it. Is it true or did I missed something? >> > > I'm also a bit confused by the product naming of those DigiVox mini > devices, can you post the output of usbview (you can usually copy the > content by selecting the content and pushing the middle mousebutton > (or in case of 2 button mice the left and the right mousebutton at the > same time)). > > regards, > Markus > Hello Mark, Sorry for delay, but I was in hurry :-( The usbview output is: DIGIVOX mini II V2.0 Manufacturer: MSI Serial Number: 01010101061 Speed: 480Mb/s (high) USB Version: 2.00 Device Class: 00(>ifc ) Device Subclass: 00 Device Protocol: 00 Maximum Default Endpoint Size: 64 Number of Configurations: 1 Vendor Id: 10fd Product Id: 3564 Revision Number: 2.00 Config Number: 1 Number of Interfaces: 2 Attributes: 80 MaxPower Needed: 500mA Interface Number: 0 Name: (none) Alternate Number: 0 Class: ff(vend.) Sub Class: 00 Protocol: 00 Number of Endpoints: 4 Endpoint Address: 81 Direction: in Attribute: 2 Type: Bulk Max Packet Size: 512 Interval: 0ms Endpoint Address: 02 Direction: out Attribute: 2 Type: Bulk Max Packet Size: 512 Interval: 0ms Endpoint Address: 84 Direction: in Attribute: 2 Type: Bulk Max Packet Size: 512 Interval: 0ms Endpoint Address: 85 Direction: in Attribute: 2 Type: Bulk Max Packet Size: 512 Interval: 0ms Interface Number: 1 Name: usbhid Alternate Number: 0 Class: 03(HID ) Sub Class: 00 Protocol: 01 Number of Endpoints: 1 Endpoint Address: 83 Direction: in Attribute: 3 Type: Int. Max Packet Size: 64 Interval: 4096ms Regards, Pat ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
