Sid Boyce wrote:
> Sid Boyce wrote:
>> Michael Krufky wrote:
>>> Sid Boyce wrote:
>>>> # modprobe cx88-dvb
>>>> FATAL: Error inserting cx88_dvb
>>>> (/lib/modules/2.6.22-rc3-smp/kernel/drivers/media/video/cx88/cx88-dvb.ko):
>>&
Sid Boyce wrote:
> # modprobe cx88-dvb
> FATAL: Error inserting cx88_dvb
> (/lib/modules/2.6.22-rc3-smp/kernel/drivers/media/video/cx88/cx88-dvb.ko):
> No such device
>
> dmesg spits this out after trying "modprobe cx88-dvb"
> cx2388x dvb driver version 0.0.6 loaded
> cx8802_register_driver()
Markus Rechberger wrote:
> On 5/29/07, Michael Krufky <[EMAIL PROTECTED]> wrote:
>> Markus Rechberger wrote:
>> > I'm adding Michael, maybe he has some ideas about it.
>> >> The reason why i asked, is that their other HVR product, the HVR-1600
>>
Markus Rechberger wrote:
> I'm adding Michael, maybe he has some ideas about it.
>> The reason why i asked, is that their other HVR product, the HVR-1600
>> (different chipset I think), also said "QAM currently not supported",
>> but then they released a beta driver that does. So I am wondering if
Uwe Bugla wrote:
> Am Freitag, 18. Mai 2007 16:44 schrieben Sie:
>
>> Uwe Bugla wrote:
>>
>>> Am Freitag, 18. Mai 2007 14:11 schrieb e9hack:
>>>
Uwe Bugla wrote:
> P. S.: Ich bin bescheiden: Eine öffentliche Entschuldigung gegenüber
> den betroffenen Leuten
ded.
Uwe, I understand that you are trying to help. Everybody helps in their own
way. On the contrary, all you've done is cause people like me to stop reading
our email. If you _really_ want to help, then please just leave us all alone.
--
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Mauro Carvalho Chehab wrote:
>
>> I do frown upon code duplication, however, in this case it is a safer
>> alternative to the one currently on the table. Earlier versions of
>> the xc3028 tuner driver were bound to the video4linux tuner.ko
>> module, for the sake of tuning analog television statio
> On Thu, 03 May 2007 Michael Krufky wrote :
>
>> Suresh S wrote:
>>
>>> Hi,
>>>
>>> The dvb card which i am using is DVICO's FusionHDTV 5 RT Lite and I m using
>>> Linux DVB version 3 API. Is there any API provision to acc
developers as to the reasons why we need a better solution. I
do believe that this will be a catalyst to discovering a proper solution later
on. If we decide to go this route, then I will volunteer to keep up the
maintenance of the xc3028-fe module until that proper, better sol
Markus Rechberger wrote:
> The problem is that we have no documentation about specific settings
> for your device. Daniel just took the firmware which he captured from
> the USB bus, which is the easiest solution to get a step forward. Next
> step would be to ask Dvico if they could send us the fi
addresses the use count bug?
If that is the case, are you suggesting that that patch be applied to the
repository instead of Trent's changesets?
Moreso, if that is the case, then the patch in the above link lacks a
sign-off... We need to apply SOMETHING to fix this problem, and you know the
s
one step at a time.
If anybody has an issue with these changes, please say so...
Cheers,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
r branch tomorrow.
Thanks to Trent Piepho for his suggestions and review. Thanks also to Linus
Torvalds for pushing me to make this cleanup.
Cheers,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Anthony Giggins wrote:
> Hello Everyone,
>
> I am using this card with Mythtv under mythdora distro (www.mythdora.com)
> for DVB with minimal problems but I am unable too get any audio via
> composite/s-video input, video works fine.
> This is pretty much my last remaining problem, I've searched e
Manu Abraham wrote:
> Uwe Bugla wrote:
>
>> If you download the thing as tar.bz2 you get a zero file down.
>>
>
> I think could be a bug in hgweb probably.
[snip]
> Let me see why hgweb gives a zero length archive
>
Manu,
We reported this bug to the selenic guys quite a long time ago...
On Thu, 03 May 2007 Michael Krufky wrote :
>> Suresh S wrote:
>>
>>> Hi,
>>>
>>> The dvb card which i am using is DVICO's FusionHDTV 5 RT Lite and I m using
>>> Linux DVB version 3 API. Is there any API provision to access the video
>
Petey Leinonen wrote:
> I have a problem building a fresh download of the main v4l-dvb repository.
>
> I get the following error:
>
> VIDEO_PLANB: Requires at least kernel 2.6.99
> VIDEO_CAFE_CCIC: Requires at least kernel 2.6.19
> Created default (all yes) .config file
> ./scripts/make_myconfig.
decoder is only useful for dealing with analog video. Digital video is
provided by the lgdt3303 demod, and is passed over to the pci bus, untouched.
It is up to software to handle PID filtering and MPEG decoding, etc.
Regards,
Michael Krufky
___
linux-
ow, so if
> there are comments now is the time.
This patch is quite a nice cleanup of the handling of the fmd1216me tuner. The
change looks more than fine to me. Would be nice to see an Ack from Hartmut,
but I see no harm can come from applying this patch.
Signed-off-by:
Uwe Bugla wrote:
> And I swear that this dvb-pll.c is completely obsolete for this scenario!
> For that reason (old variant):
> # CONFIG_DVB_TUNER_LGH06XF is not set
>
> And this old variant was NOT done by Trent Piepho, it was NOT done by Andrew
> Quincey,
> but it was produ
ct has matured enough for testing.
I'm not the guy working on this, in case you're wondering. ...that's all I can
say about it right now.
Regards,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[EMAIL PROTECTED] wrote:
> Hi Mike,
>
> --- Michael Krufky <[EMAIL PROTECTED]> wrote:
>
>
>> This, however, isn't clear to me: "zl10353 demodulator is disabled (0x0c ->
>> &0x50)" ... can you show a usbsnoop log snippet of this behavior?
&
[EMAIL PROTECTED] wrote:
> Hi all,
>
> A brief update. Firstly I've confirmed my newly created firmware file (pulled
> from usbsnoop logs) being sent to the xc3028 is identical to windows.
> Secondly, apart from a gate register being written, the ZL10353 should be
> consistent as well. Thirdly
Michael Krufky wrote:
> Marco Gittler wrote:
>> here the new patch against main hg.
>> -the tuner i2c addr now without define (as wanted).
>> -now 7 bit addr are used (the power_ctrl fkt ist ok so, because this
>> is a raw write)
>> -the addr >> 1 , addr
Marco Gittler wrote:
> here the new patch against main hg.
> -the tuner i2c addr now without define (as wanted).
> -now 7 bit addr are used (the power_ctrl fkt ist ok so, because this
> is a raw write)
> -the addr >> 1 , addr << 1 is ok so, i think beause the read write is
> now taken from the last
Mauro Carvalho Chehab wrote:
> Em Sex, 2007-04-20 às 13:53 +0200, Johannes Stezenbach escreveu:
>> On Fri, Apr 20, 2007, Mauro Carvalho Chehab wrote:
>>> Argh! Too much flood for two simple defines!
>> I _think_ the point Mike was driving at is that there
>> is an established coding pattern of havi
Mauro Carvalho Chehab wrote:
> Em Qui, 2007-04-19 às 16:41 -0400, Michael Krufky escreveu:
>
>> Marco Gittler wrote:
>>
>>> this patch has applied the hints from mkrufky (dvb_attach,
>>> firmware-naming)
>>> and also one working rewrite of the
Marco Gittler wrote:
> this patch has applied the hints from mkrufky (dvb_attach,
> firmware-naming)
> and also one working rewrite of the i2c addresses stuff to fit the
> kernel i2c reqs.
>
> Signed-off-by: Marco Gittler<[EMAIL PROTECTED]>
> diff -r c8b73ec18b42 linux/drivers/media/dvb/dvb-usb/ope
; done, except the i2c addr (reason is like above)
fine. Once the i2c handling is converted, we'll change this as appropriate.
This will be OK in the meantime.
>>> + return 0;
>>> +}
>>> +
[snip]
>>> +static struct dvb_usb_device_properties opera1_properties
lly change after firmware
download)
Again, you do not need a driver for cy7c68013A -- you need to instead find the
firmware used in your device, and then write a driver to interact with that
firmware.
If you google for cypress fx2, you will find muc
Markus Rechberger wrote:
> Hi,
>
> I had a closer look at the dvb framework and fixed the hotplugging
> issues for dvb-usb and em28xx/dvb devices (which are not merged into
> the kernel)
>
> So please test it and have a look at the last 3 patches, I was only
> able to test scanning for channels s
Michael Krufky wrote:
> I imported that changeset directly from hg on kernel.org, so I forgot to add
> the
> 'kernel-sync' tag before pushing it up. (otherwise, I would have asked for
> the
> pull earlier)
I fixed that issue, the tree is now ready for normal pull.
Mauro Carvalho Chehab wrote:
> Em Qua, 2007-04-11 às 10:44 -0400, Michael Krufky escreveu:
>> Brett Taylor wrote:
>>>> Out of curiosity, what happens if you switch RF inputs? There was a
>>>> patch submitted about two weeks or so ago that may have affect the RF
&g
n this repository:
http://linuxtv.org/hg/~mkrufky/kernel-sync
This fix has already been merged into 2.6.20.y -stable kernel series, AND
2.6.21-rc
It isn't yet in the v4l-dvb master branch, but it will get there eventually.
--
Michael Krufky
__
ository is dated as two months ago, because at that point he
updated the repository with the changesets from the master branch.
We were looking for feedback as to whether or not his rounding fixes for the
dvb-pll module did the trick for tuning in Australia -- Thank you for this
feedback.
Cheers,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Mauro Carvalho Chehab wrote:
> Em Qui, 2007-04-05 às 17:10 -0400, Michael Krufky escreveu:
>
>> It appears that I may have been misunderstood.
>>
>> Your argument is completely valid, I only ask that nobody touch tda8290.c or
>> tda827x.c until Hartmut and I are
Mauro,
Mauro Carvalho Chehab wrote:
> Michael,
>
> Em Qui, 2007-04-05 às 16:31 -0400, Michael Krufky escreveu:
>> Mauro Carvalho Chehab wrote:
>>> Also, for silicon tuners, we have a recent case, where tda897x deals
>>> with dvb, while tda8290 deals also wit
handle hybrid silicon, I will handle the
conversion for the tda827x tuners.
Regards,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Michael Krufky wrote:
> Patrick Boettcher wrote:
>> On Thu, 5 Apr 2007, Borgi2008 wrote:
>>
>>> Am Mittwoch, den 04.04.2007, 23:29 +0300 schrieb Antti Seppälä:
>>>> Borgi2008 wrote:
>>>>> Hello,
>>>>>
>>>>>
>>> atomic context so there is no use in making the handler protected by a
>>> spinlock. Am I missing something here?
>>>
>>> I think the spinlock is unnecessary and should be removed entirely.
>
> Even on SMP systems? ISRs are only atomic on one CPU.
john owen-jones wrote:
> hi
> I apologise for doing this incorrectly but i haven't a clue how to
> upload the diff file
> this works very well with the kworld dvb-t 210 essentially its a clone
> of a philips reference design and really just entails identifying the card.
>
> I checked out the sourc
hermann pitton wrote:
> ...
>> Mike,
>>
>> I still think Manu should give the dvb-maintainer for some months and
>> after it also the v4l-dvb maintainer at least for half a year.
>>
>> We should at least have a chance to disagree about much less.
>>
>
> To make it more simple and more annoying.
>
},
> + },
> + }
> +};
> +
> +static struct m9206_inits megasky_rc_init [] = {
> + { M9206_RC_INIT2, 0xa8 },
> + { M9206_RC_INIT1, 0x51 },
> + { } /* terminating entry */
> +};
> +
> +static struct m9206_inits tvwalkertwin_rc
Nick Andrew wrote:
> On Sun, Mar 18, 2007 at 10:10:59AM -0400, Michael Krufky wrote:
>> Would you mind if I send this one in through the m920x tree? Both Pierre
>> and Nick's patches depend on this one, and it makes sense to push these
>> changes together.
>
>
Hartmut Hackmann wrote:
> Here is the experimental patch i promised:
> The struct tda1004x_config has a new entry: .ts_mode
> Possible values are TDA10046_TS_PARALLEL or TDA10046_TS_SERIAL
> There always is only one interface active, default is parallel.
> Can you please give it a try?
>
> Hartmut
int serial_mpeg;
... in practice, some devices are using parallel, while others are using serial.
I think you should go ahead with your patch.
Regards,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
xtv.org/~mkrufky/pending/msi-digivox-mini-ii.patch
( applies against: http://linuxtv.org/hg/~mkrufky/m920x )
Please send an updated patch when ready.
Cheers,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
u32 freq_khz = fep->frequency / 1000;
> u32 tfreq = ((freq_khz + 36125)*6 + 500) / 1000;
>
> If you multiple that out and reduce it, you get:
>tfreq = (fep->frequency + 36125000 + 17/2) / 17;
>
> But the dvb-pll definition is using 36125000 + 17.
Mauro Carvalho Chehab wrote:
> Ok, I've reviewed the text, adding some more useful info for developers.
>
> Cheers,
> Mauro
Mauro,
Please see the following correction:
>
>
> --------
>
> +Mich
hermann pitton wrote:
> Am Dienstag, den 06.03.2007, 11:14 -0500 schrieb Michael Krufky:
>> Mauro Carvalho Chehab wrote:
>>> Hi Guys,
>>>
>>> The last time we've reviewed our procedures were on March, 2006. I think
>>> it is time to review the docu
IMHO, better to stay
consistent.
#2, I have made some corrections to the document. Please see these corrections
inline below.
Regards,
Michael Krufky
>
>
>
>
>
> diff -r 299dd4a8b598 README.deve
Aapo Tahkola wrote:
> On Fri, 02 Mar 2007 23:06:15 +0100
> Pierre Willenbrock <[EMAIL PROTECTED]> wrote:
>
>> Michael Krufky schrieb:
>>> Pierre Willenbrock wrote:
>>>> Hi list,
>>>>
>>>> I am owner of a "MSI DIGIVOX mini-II&q
[EMAIL PROTECTED] wrote:
> Hello, i compiled the v4l-dvb driver with the patch posted at
> http://www.mail-archive.com/linux-dvb@linuxtv.org/msg21957.html,
>
> any idea what is my problem.
>
> I have following dmesg.
>
> dvb-usb: found a 'MSI DIGI VOX mini II DVB-T USB2.0' in warm state.
> PM: A
Trent Piepho wrote:
> On Mon, 26 Feb 2007, Michael Krufky wrote:
>> Trent Piepho wrote:
>>> I think the problem is not with firmware for the tuner, but firmware for
>>> the bridge. For instance, all the other dvb-pll tuners used in cxusb.c
>>> have NULL speci
Trent Piepho wrote:
> On Mon, 26 Feb 2007, Michael Krufky wrote:
>> Trent Piepho wrote:
>>> There is one other difference. dvb-pll will probe for the presence of an
>>> I2C pll chip by doing a one byte read, the lgh06xf driver did not do
>>> this. In some d
Michael Krufky wrote:
> Apart from that, it all looks correct to me, but I ran into some problems
> unrelated to
> your change...
>
> For some reason, the build system in your tree doesn't want to build
> cx88-dvb.ko Even after doing "make allyesconfig&
2c 90 ce 04
...works well for me. Please make the fixes above to the Kconfig files before
requesting
merge into master.
Acked-by: Michael Krufky <[EMAIL PROTECTED]>
Regards,
Mike
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
o detect*/
> + if (fe->ops.i2c_gate_ctrl)
> + fe->ops.i2c_gate_ctrl(fe, 1); /* open i2c_gate */
> +
> + /* Try to detect tuner chip. Probably this is not correct
> register. */
> + if (tda8275_readreg(priv, 0x29, &id) != 0 || (id != 0x39)) {
> + kfree(priv);
> + return NULL;
> + }
> +
> + if (fe->ops.i2c_gate_ctrl)
> + fe->ops.i2c_gate_ctrl(fe, 0); /* close i2c_gate */
> + }
> +
> + printk(KERN_INFO "Philips TDA8275 probably identified.\n");
> + memcpy(&fe->ops.tuner_ops, &tda8275_tuner_ops, sizeof(struct
> dvb_tuner_ops));
> +
> + fe->tuner_priv = priv;
> + return fe;
> +}
> +EXPORT_SYMBOL(tda8275_attach);
> +
> +MODULE_DESCRIPTION("Philips TDA8275 silicon tuner driver");
> +MODULE_AUTHOR("Pierre Willenbrock <[EMAIL PROTECTED]>");
> +MODULE_VERSION("0.1");
> +MODULE_LICENSE("GPL");
> diff -r 4d012cd162f5 linux/drivers/media/dvb/frontends/tda8275.h
> --- /dev/null Thu Jan 01 00:00:00 1970 +
> +++ b/linux/drivers/media/dvb/frontends/tda8275.h Thu Feb 22 21:43:32
> 2007 +0100
> @@ -0,0 +1,53 @@
> +/*
> + * Driver for Philips tda8275 silicon tuner
> + *
> + * Copyright (C) 2007 Pierre Willenbrock <[EMAIL PROTECTED]>
> + * Based on qt1010 driver
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
> + */
> +
> +#ifndef TDA8275_H
> +#define TDA8275_H
> +
> +#include "dvb_frontend.h"
> +
> +struct tda8275_config {
> + u8 i2c_address;
> +};
> +
> +/**
> + * Attach a tda8275 tuner to the supplied frontend structure.
> + *
> + * @param fe frontend to attach to
> + * @param i2c i2c adapter to use
> + * @param cfg tuner hw based configuration
> + * @return fe pointer on success, NULL on failure
> + */
> +#if defined(CONFIG_DVB_TUNER_TDA8275) ||
> (defined(CONFIG_DVB_TUNER_TDA8275_MODULE) && defined(MODULE))
> +extern struct dvb_frontend *tda8275_attach(struct dvb_frontend *fe,
> + struct i2c_adapter *i2c,
> + struct tda8275_config *cfg);
> +#else
> +static inline struct dvb_frontend *tda8275_attach(struct dvb_frontend *fe,
> + struct i2c_adapter *i2c,
> + struct tda8275_config *cfg)
> +{
> + printk(KERN_WARNING "%s: driver disabled by Kconfig\n", __FUNCTION__);
> + return NULL;
> +}
> +#endif // CONFIG_DVB_TUNER_TDA8275
> +
> +#endif
>
>
>
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
CityK wrote:
> Its not DiBcom based. It uses the LG DT3303 demodulator. Other
> components are the Microtune MT2060 tuner and Cypress FX2 usb bridge.
If the usb control API uses the same as the Conexant USB 2.0 hybrid reference
design, then
you should have an easy time adding support for this to
Phil Taylor wrote:
> A few weeks ago you made the following response re a problem with the usb
> DigiTV tuner, as noted below.
> I have just installed a recent distro using the 2.6.20 kernel, and the
> problem still persists. Can you give me any idea when these patched will be
> included in a re
I dont know. I won't touch this until after a
clean, fully functional and GPL'd xc3028 driver appears in the master branch.
That wont happen right away.
If you want to try to add support for this card yourself, you can take a look at
how Markus added xc2028 support for a cardbus cx88 card in his v4l-dvb-kernel
tree.
I hope this helps,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[EMAIL PROTECTED] wrote:
> Hi There,
>
> I have just tried installing a DViCO DVB-T PRO card under
> Fedora Core 6. I thought I would save myself some pain and
> go
> with FC rather than FreeBSD. It appears not.
>
> 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:16:31 EST 2007 x86_64
> x86_64 x86_64 GNU
ning_function;
> }
Hartmut,
NO! Please take a look inside tua6100.c ... you will notice that there are more
tuner_ops being filled besides only set_params. There is no bug here, the
current code is optimal.
--
Michael Krufky
___
Andrew Kennan wrote:
>
>> All I know is that people in Melbourne are having trouble -- I havent
>> heard
>> from anybody else in AU. One of my testers has the Dual Digital 1
>> card, which
>> uses an mt352 demod -- this one is working just fine. (He has it in
>> the same
>> box with the Dual Dig
m quite sure that any other device with a zl10353 will produce the same
problematic behavior when used in this area.
> On Saturday 17 February 2007 05:27, Michael Krufky wrote:
>> It would be nice to hear if there are _any_ linux users with a
>> zl10353-based device working in
uch I can do from here... If there are any developers located in
the area, please feel free to try to debug the problem.
Sorry,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
ass
'index=1' to cx88-alsa, then it will use the 2nd minor, instead of the first.
A much better practice would be to instead, pass 'index=0' to the module that
actually drives your sound card. use the modinfo command to check that the
option is available.
HTH,
Michael Kru
in the form:
Signed-off-by: Your Name <[EMAIL PROTECTED]>
...so that I can add your patch into the official sources.
For more info, see: http://linuxtv.org/hg/v4l-dvb?f=-1;file=README.patches
Regards,
Michael Krufky
---
linux/drivers/media/dvb/dvb-usb/cxusb.c |4 ++--
1 fi
Brett Ryan wrote:
> Hi guys, I'm just wondering how the development for the DViCO FusionHDTV
> DVB-T Dual Digital 4 driver is going. I'm keen to get my card working, if I
> can lend a hand at all let me know though I'm only a java/c# developer and
> not had any experience with kernel development.
>
tim belina wrote:
[snip]
> However, the card doesn't work properly:
>
> 1) I see only a single card in YaST, which describes the card as a
> FusionHDTV DVB-T Dual Digital. Perhaps that is correct, but I'm unsure
> if I should see one for each of the "dual" receivers.
Do, "modprobe cx88-dvb" ...
tree for this? The code in ~hverkuil/v4l-dvb2 has
nothing to do with your device.
Steve Toth's multiproto tree is an experimental development branch that should
work for your device.
I hope this helps,
Michael Krufky
___
linux-dvb mailin
[EMAIL PROTECTED] wrote:
>
> hi,
> i'm on gentoo linux and 'd been using my twinhan dvb-t until the update to
> v4l-dvb-hg.
>
> after tweaking my kernel, it's just one error left:
>
> *Code:*
>
> dvb_bt8xx: Unknown symbol dvb_pll_lg_tdvs_h06xf
This symbol would be found in the dvb-pll module.
e is DVBFE_GET_INFO, working with that as a base.
> It is extendable to the adapter object.
>
> Currrently playing around with a bit with some devices on the same in
> that aspect
Manu,
I don't think that Hartmut is talking about multiple frontends per adapter, as
you are describing.
Hartmut is trying to establish a means in telling the difference between the
frontends installed on the multiple devices in a single given system.
For instance, I have a mythtv backend server with five PCI cards inside... each
of which use the LG DT3303 ATSC demod.
Given that each of these frontends identify themselves as an LG Electronics DT
3303, how does the user know which frontend is associated to the FusionHDTV 5
Gold? Which one is the AirStar HD5000? Which one is the FusionHDTV5 USB Gold?
Does this explain the question any better?
--
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hartmut Hackmann wrote:
> Hi, folks
>
> Currently most boards report the type of the channel decoder as
> the frontend name. This has the disadvantage that if you have multiple
> (hybrid) cards with the same channel decoder type, you will not be
> able to distinguish them in the applications. Espe
Jan wrote:
> Michael Krufky wrote:
>> I believe that as of today, I´ve caught up on all of the pending
>> changesets to the megasky tree.
>>
>> Please test the two following trees to confirm proper operation:
>>
>> http://linuxtv.org/hg/~mkrufky/megask
luebird firmware is not compatible with
your device.
Adding support for this device is on my to-do list, but it is going to be a
while before I get there.
If you want to help speed along the process, then please take a usbsnoop of the
driver traffic while in windows, and post it to a web
Sam Bakara wrote:
> Greetz,
>
> I have Ubuntu-Edgy kernel 2.6.17-10-generic
> USB Device: MSI MegaSky 580 id 5580
>
> Compiled & Installed latest drivers and loaded module as follows:
>
> [17179598.452000] dvb-usb: downloading firmware from file
> 'dvb-usb-megasky-02.fw'
> [17179599.064000] dvb_
Antti Palosaari wrote:
> moikka!
> Take 2. Same patch generated against different tree, this one is for
> http://linuxtv.org/hg/~mkrufky/megasky.new . All other information from
> previous mail applies to this patch also.
>
> Signed-off-by: Antti Palosaari <[EMAIL PROTECTED]>
>
Antti-
I've gott
to account for this. I apologize for any
inconvenience this may cause.
--
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Aapo Tahkola wrote:
> On Sun, 21 Jan 2007 16:11:21 -0500
> Michael Krufky <[EMAIL PROTECTED]> wrote:
>> Please test the two following trees to confirm proper operation:
>>
>> http://linuxtv.org/hg/~mkrufky/megasky(expected to work for
>> everybody)
pport your device. Thanks
anyway for testing, though.
--
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Tino Keitel wrote:
> Hi folks,
>
> I noticed that udev does not create a symlink for the CinergyT2 remote input
> device in /dev/input/by-id, which is required if I want to have a
> unique device name for lircd.
>
> The attached patch tries to achive this. However, udev still omits the
> input devi
I believe that as of today, I´ve caught up on all of the pending
changesets to the megasky tree.
Please test the two following trees to confirm proper operation:
http://linuxtv.org/hg/~mkrufky/megasky(expected to work for everybody)
http://linuxtv.org/hg/~mkrufky/megasky.new(possible pro
Chris Rankin wrote:
> Hi,
>
> This patch writes the USB vendor and product IDs into the
> /sys/class/input/inputX/id/ files, so
> that udev can find them. A rule like this does the trick for me:
>
> KERNEL="event*", SYSFS{../id/vendor}=="2040", SYSFS{../id/product}=="9301",
> SYMLINK+="input/dvb-r
n't find any information on its compatability
> under Linux.
There is no such device available yet with Linux support. Maybe we can add
support for the LR351... What chips are used inside that device?
--
Michael Krufky
___
linux-dvb mailing list
l
the cx88-mpeg
switching on the hvr1300 before we apply this.
Cheers,
Michael Krufky
--- v4l-dvb.orig/linux/drivers/media/video/cx88/cx88.h 2007-01-01 14:11:59.0 +0100
+++ v4l-dvb/linux/drivers/media/video/cx88/cx88.h 2007-01-02 23:30:54.0 +0100
@@ -351,6 +351,7 @@
/* cx88-video needs
ll make an announcement once my driver is ready and tested, but I
cant say how soon that will be.
> BTW, I'm in Adelaide if it makes any difference.
I don't know if it makes a difference. I live in Brooklyn. :-)
Cheers,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
ou do deserve some credit :-)
> I will take care of updating the wiki with the new info for this card.
>
> Thanks for everything.
No Problem... I'll have this merged into the master repository for you.
Cheers,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Giorgio Moscardi wrote:
> Alle 01:58, martedì 16 gennaio 2007, Michael Krufky ha scritto:
>> I suspect that you will encounter the same exact problem as you had before.
>> If this is the case, you may want to play around with the following info:
>
> OK, here's the patch
Giorgio Moscardi wrote:
> Alle 00:15, martedì 16 gennaio 2007, Hartmut Hackmann ha scritto:
>> Thanks for the info, Michael!
>> Giorgio can you please test and report?
> Sure! Thanks a lot! I'll do that straight tomorrow. I guess I should apply it
> to the mercurial tree, right?
Yes, but you migh
uggest removing the "PCMCIA" from the text
name of card #105 --- the card setup *seems* to be identical, but there is
only so much that I can tell without trying myself.
If you decide to apply this patch, Hartmut, then here is my sign-off:
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Dwaine Garden wrote:
> Finished testing... Looks like the patch did not switch over to the second
> RF connection.
>
> Could be related to this issue.. The Kworld device does display a picture
> for a split second
> then it goes black with various green boxes shooting around the screen. The
John wrote:
> Thanks, I'd be happy to test it out. It's not working
> for me but I want to make sure I did it right.
>
> The links says the following.
>
> static int nxt200x_set_pll_input(u8 *buf, int input)
> {
> - if (input)
> - buf[3] |= 0x08;
> - else
> - buf[3
John wrote:
> Thanks, I look forward to seeing if it works on your
> system. I also tried it on a the latest livedvd
> Knoppix distro and it diplayed the same behavior.
>
> --- Dwaine Garden <[EMAIL PROTECTED]> wrote:
>
>> I'll do some testing too. I have not tried both
>> analog and digital on
Fraser wrote:
> Hello,
>
> I had my digitv up and running fine in Fedora core 5 (using a 2.6.17 kernel).
> I
> recently upgraded to fedora core 6 (2.6.18) and since doing this my device has
> stopped working properly. Initialisation etc appears fine but the device will
> not
> tune. Tuning proce
of his older patches, but unfortunately those were never
applied. If we are not able to reach Henry, then we should at least put
somewhere in the description of the changeset something to the effect of,
"KS003/KS007 support based on the original work by Henry Wong"
Cheers,
Mic
ard is programmed to allow analog video inputs from either
svideo or composite.
Try to use an analog video application, such as tvtime, or xawtv.
You can use the controls within the application to determine which
input is used.
HTH,
Michael Krufky
__
James Evans wrote:
> Hello,
>
> I have searched all over the place and didn't find anything, so I figured
> this would be the place to go.
>
> I have recently purchased a DViCo FusionHDTV5 Express card and placed it into
> a gentoo linux box. The current kernel drivers do not
> appear to suppo
hermann pitton wrote:
> Hi!
>
> Am Donnerstag, den 16.11.2006, 13:54 -0500 schrieb Michael Krufky:
>> Lucian Iuga wrote:
> [snip]
>
>> The MFPE05 tuner is not yet supported, but probably wont be difficult to add
>> support for.
>
> Mike, we found the
above.
I do not think this device will receive digital television -- it seems to be
analog-only.
What are your thoughts?
Regards,
Michael Krufky
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
201 - 300 of 378 matches
Mail list logo
