Hi,
Nicolas Will wrote:
Torgeir,
I think that you are not running the latest code with the latest
firmware.
Aug 1 00:01:16 htpc2 kernel: dib0700: loaded with support for 3 different
device-types
It should say 5 different devices, not 3.
Aug 1 00:01:16 htpc2 kernel:
On Mon, 2007-08-06 at 01:32 +0100, Chris Murton wrote:
drivers would not lock to most channels
Do you have the LNA turned on?
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#On-board_amplifier
Nico
___
linux-dvb mailing list
Hello,
has anyone seen errors like this before?:
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0 frequency 151 out of
range
Lars Buerding wrote:
Hello,
has anyone seen errors like this before?:
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0
Hi,
at least for its true, that my old IR receiver and the Hauppauge remote
from the PVR350 do NOT work with the T500. At least not yet ;)
I was testing the latest changes on Saturday and was not seeing anything
with irw and/or event-something. One of the final resorts was using the
remote
Hi Nico,
Nicolas Will wrote:
On Mon, 2007-08-06 at 01:32 +0100, Chris Murton wrote:
drivers would not lock to most channels
Do you have the LNA turned on?
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#On-board_amplifier
Certainly do :-
basil:~# cat
On 8/6/07, Lars Buerding [EMAIL PROTECTED] wrote:
Hello,
has anyone seen errors like this before?:
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17 gwmuc
Well,
Let's refine the final things about this card's support.
I am still getting tons of this message in my logs:
Aug 6 08:35:47 favia kernel: [55193.646677] dib0700: Unknown remote controller
key : 18 7C
Nico
___
linux-dvb mailing list
Hello,
I guess these are new to the dvb-usb scene, since a google search for
Sumvision T680 linux brings up very few (and all unrelated to linux
dvb) results.
I have bought a Sumvision T680 usb stick. It was cheap (£20). It does
not work in Linux. I modprobed every dvb-usb module (that is
Hello Michael,
Working version:
- Kernel V2.6.22.1 / dvb-pll-0549f1757f66
^^^ This is an invalid revision.
Where did you get that tree?
I dont remember exactly, but this was short before I subscribed
to linuxtv-dvb, and I think I got it
Hello Manu,
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0 frequency 151 out of
range (95..140)
Aug 6 07:08:05 gwmuc
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
http://www.fusionhdtv.co.kr/ENG/products/DVBTDualExpress.aspx
It would appear they may have left their 'usb' adoptions behind
Main chipset: CX23885
Tuner: Xceive
I noticed someone asked about
On 8/6/07, Lars Buerding [EMAIL PROTECTED] wrote:
Hello Manu,
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0 frequency
On 8/6/07, Shannon Wynter [EMAIL PROTECTED] wrote:
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
http://www.fusionhdtv.co.kr/ENG/products/DVBTDualExpress.aspx
It would appear they may have left their 'usb' adoptions behind
Main chipset:
Manu Abraham wrote:
On 8/6/07, Lars Buerding [EMAIL PROTECTED] wrote:
Hello Manu,
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17 gwmuc kernel: DVB: frontend 0
Shannon Wynter wrote:
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
Do you know which demodulators they're using? If we already have
demodulator drivers then getting some basic support for the board into
linux would only take a few days,
On 8/6/07, Steven Toth [EMAIL PROTECTED] wrote:
Shannon Wynter wrote:
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
Do you know which demodulators they're using? If we already have
demodulator drivers then getting some basic support
Steven Toth wrote:
Shannon Wynter wrote:
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
Do you know which demodulators they're using? If we already have
demodulator drivers then getting some basic support for the board into
linux
Michael Krufky wrote:
Steven Toth wrote:
Shannon Wynter wrote:
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
Do you know which demodulators they're using? If we already have
demodulator drivers then getting some basic
Steven Toth wrote:
LGH064F
I take it this is the demod. Is a datasheet available for that?
That's the NIM ... it utilizes the LG DT3303 demodulator for digital
(and TDA9887 demod for analog)
___
linux-dvb mailing list
linux-dvb@linuxtv.org
Steven Toth wrote:
Michael Krufky wrote:
Steven Toth wrote:
Shannon Wynter wrote:
G'day all.
What do you think my chances of getting the FusionHDTV DVB-T Dual
Express working?
Do you know which demodulators they're using? If we already have
demodulator drivers then
Coincidently, DViCO has just put up news for their next generation:
**FusionHDTV6 Cool
**http://www.fusionhdtv.co.kr/ENG/Boards/PressRelease.aspx?act=RDitemid=376pg=1
___
linux-dvb mailing list
linux-dvb@linuxtv.org
Steven Toth wrote:
Ahh.
Hmm, the picture of the board doesn't show a NIM though. It looks like
a 10046 maybe. I'm maybe confusing the original thread product with
Michaels announcement, which is actually a different product.
Yep, exactly -- two different products being discussed. The NIM is
Guys,
The HVR4000 looks good on paper, but activity in not heavy, and it has
that design flow that prevents it from being real useful (cannot do T
and S at the same time).
So I am looking for a dedicated DVB-S2 only solution in order to expand
my HTPC.
So what about the Hauppauge WinTV
CityK wrote:
Steven Toth wrote:
LGH064F
I take it this is the demod. Is a datasheet available for that?
That's the NIM ... it utilizes the LG DT3303 demodulator for digital
(and TDA9887 demod for analog)
Ahh.
Hmm, the picture of the board doesn't show a NIM though.
CityK wrote:
Coincidently, DViCO has just put up news for their next generation:
**FusionHDTV6 Cool
**http://www.fusionhdtv.co.kr/ENG/Boards/PressRelease.aspx?act=RDitemid=376pg=1
I'm relying on you, CityK, to find out what PCI Bridge chipset is used on that
device... Do I see, DIBCOM
Nicolas Will wrote:
Guys,
The HVR4000 looks good on paper, but activity in not heavy, and it has
that design flow that prevents it from being real useful (cannot do T
and S at the same time).
So I am looking for a dedicated DVB-S2 only solution in order to expand
my HTPC.
So what about
Steven Toth wrote:
Nicolas Will wrote:
Guys,
The HVR4000 looks good on paper, but activity in not heavy, and it has
that design flow that prevents it from being real useful (cannot do T
and S at the same time).
So I am looking for a dedicated DVB-S2 only solution in order to expand
my
Michael Krufky wrote:
Steven Toth wrote:
Nicolas Will wrote:
Guys,
The HVR4000 looks good on paper, but activity in not heavy, and it has
that design flow that prevents it from being real useful (cannot do T
and S at the same time).
So I am looking for a dedicated DVB-S2 only
Steven Toth wrote:
Michael Krufky wrote:
Steven Toth wrote:
Nicolas Will wrote:
Guys,
The HVR4000 looks good on paper, but activity in not heavy, and it has
that design flow that prevents it from being real useful (cannot do T
and S at the same time).
So I am looking for a
On Monday 06 August 2007 17:42:08 Michael Krufky wrote:
CityK wrote:
Coincidently, DViCO has just put up news for their next generation:
**FusionHDTV6 Cool
**http://www.fusionhdtv.co.kr/ENG/Boards/PressRelease.aspx?act=RDi
temid=376pg=1
I'm relying on you, CityK, to find out what PCI
Hello,
Further to my email above, I have taken apart the case and found some chips.
One labelled MT2061F (which doesn't seem to have anything useful
online about it)
Another labelled WJCE6353 (which I think is an intel (-compatible?)
353 tuner chip. Will throw Zarlink MT352/3 module at it
Michael Krufky wrote:
Manu Abraham wrote:
On 8/6/07, Lars Buerding [EMAIL PROTECTED] wrote:
Hello Manu,
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
--
Aug 6 07:07:17
Oliver Endriss wrote:
According to the crippled datasheet, a symbol rate from 12..30 MSym/s
should be correct for the TDA8083.
The Grundig 29504-451 tuner uses the TDA8060 down-converter, which has a
frequency range from 920..2200MHz.
So the attached patch should fix the range issues. Ok?
On 8/6/07, Oliver Endriss [EMAIL PROTECTED] wrote:
Michael Krufky wrote:
Manu Abraham wrote:
On 8/6/07, Lars Buerding [EMAIL PROTECTED] wrote:
Hello Manu,
I am getting these messages using the latest available tip-version
(v4l-dvb-5bb1af77fdc5).
Steven Toth wrote:
... But were a way off, perhaps months from seeing multiproto accept in
v4l-dvb hg.
Why? I think it's time to get multiproto into the main tree.
We should review the API and dvb core changes asap.
For me the API looks fine except for the modified FE_GET_EVENT ioctl,
which
On Mon, 6 Aug 2007, Michael Krufky wrote:
Manu Abraham wrote:
In frontends/tda8083.c
Look for this:
446 .frequency_min = 95, /* FIXME:
guessed! */
447 .frequency_max = 140,/* FIXME:
guessed! */
change to
On 8/6/07, Steven Toth [EMAIL PROTECTED] wrote:
My goal is to get basic hvr4000 DVB-S/S2 support merged first (after
multiproto is merged), then follow that with the 'multiple frontend on a
single bus' HVR3000 patches, thereby enabling DVB-T/S and S2 all in one go.
... But were a way off,
Manu Abraham wrote:
On 8/6/07, Steven Toth [EMAIL PROTECTED] wrote:
My goal is to get basic hvr4000 DVB-S/S2 support merged first (after
multiproto is merged), then follow that with the 'multiple frontend on a
single bus' HVR3000 patches, thereby enabling DVB-T/S and S2 all in one go.
CityK wrote:
Janne Grunau wrote:
On Monday 06 August 2007 17:42:08 Michael Krufky wrote:
CityK wrote:
Coincidently, DViCO has just put up news for their next generation:
**FusionHDTV6 Cool
**http://www.fusionhdtv.co.kr/ENG/Boards/PressRelease.aspx?act=RDi
temid=376pg=1
Hi,
the min frequencies of the DVB-C frontends are wrong. In Europe, the center
frequency of the lowest
channel is 50.5MHz and not 51MHz. All known cards with the
stv0297/tda0002x/ves1820 frontend are
able to tune to this frequency. I've changed the range to the lowest channel -
1/2 bandwidth
Hi Trent,
Trent Piepho wrote:
On Mon, 6 Aug 2007, Chris Murton wrote:
The aerial configuration has not changed, I have line of sight to the
transmitter in question and dmesg looks reasonably healthy:
dib0700: loaded with support for 5 different device-types
usb 3-3: reset full speed USB
Hi,
48200 has replaced 64200. There are now 3 other TV-channels and also
some parameters have changed (guard_interval).
49800 is new and the TV-channels were formerly on 48200.
bye
Karsten
Christoph Pfister wrote:
[ adding CC to the contributor of this file; maybe you have
e9hack wrote:
Hi,
the min frequencies of the DVB-C frontends are wrong. In Europe, the center
frequency of the lowest
channel is 50.5MHz and not 51MHz. All known cards with the
stv0297/tda0002x/ves1820 frontend are
able to tune to this frequency. I've changed the range to the lowest
On Mon, 6 Aug 2007, Chris Murton wrote:
The aerial configuration has not changed, I have line of sight to the
transmitter in question and dmesg looks reasonably healthy:
dib0700: loaded with support for 5 different device-types
usb 3-3: reset full speed USB device using ohci_hcd and address 2
Greg Manning wrote:
Hello,
Further to my email above, I have taken apart the case and found some chips.
One labelled MT2061F (which doesn't seem to have anything useful
online about it)
its the tuner: http://www.microtune.com/products/
Another labelled WJCE6353 (which I think is an
Why not merge DVB-S support only, into the master branch, so that users of
that
card can use the features of it that are NOT still up in the air?
Receiving the changes splitted into smaller pieces means easier work to
me. I prefer, however, that the DVB-S2 stuff would be into a second
patch,
Michael Krufky schrieb:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6
Should we be checking fe-ops.tuner_ops.info.frequency_min|max , instead of
Hi Trent,
Chris Murton wrote:
Hi Trent,
Trent Piepho wrote:
On Mon, 6 Aug 2007, Chris Murton wrote:
The aerial configuration has not changed, I have line of sight to the
transmitter in question and dmesg looks reasonably healthy:
dib0700: loaded with support for 5 different device-types
e9hack wrote:
Michael Krufky schrieb:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6
Should we be checking fe-ops.tuner_ops.info.frequency_min|max , instead of
Oliver Endriss wrote:
Michael Krufky wrote:
e9hack wrote:
Hi,
the min frequencies of the DVB-C frontends are wrong. In Europe, the center
frequency of the lowest
channel is 50.5MHz and not 51MHz. All known cards with the
stv0297/tda0002x/ves1820 frontend are
able to tune to
Michael Krufky wrote:
Oliver Endriss wrote:
Michael Krufky wrote:
e9hack wrote:
Hi,
the min frequencies of the DVB-C frontends are wrong. In Europe, the
center frequency of the lowest
channel is 50.5MHz and not 51MHz. All known cards with the
stv0297/tda0002x/ves1820
Oliver Endriss wrote:
Michael Krufky wrote:
Oliver Endriss wrote:
Michael Krufky wrote:
e9hack wrote:
Hi,
the min frequencies of the DVB-C frontends are wrong. In Europe, the
center frequency of the lowest
channel is 50.5MHz and not 51MHz. All known
On Mon, 6 Aug 2007, Chris Murton wrote:
Trent Piepho wrote:
DVB: Unable to find symbol mt2060_attach()
That is your problem. You didn't compile the mt2060 module, or it's not
installed, or your modprobe information is out of date (run depmod), or
your module utils version is too old
Trent Piepho wrote:
On Mon, 6 Aug 2007, e9hack wrote:
Michael Krufky schrieb:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6
Should we be checking
Oliver Endriss wrote on 05/08/2007 06:14:
Sven Mueller wrote:
Oliver Endriss wrote on 01/08/2007 00:27:
Sven Mueller wrote:
Hi.
I don't know which hardware interrupts those are mapped from/to and
currently don't know how to find out.
If you need any further data to give a helpful answer,
Hi Trent,
Trent Piepho wrote:
On Mon, 6 Aug 2007, Chris Murton wrote:
Trent Piepho wrote:
DVB: Unable to find symbol mt2060_attach()
That is your problem. You didn't compile the mt2060 module, or it's not
installed, or your modprobe information is out of date (run depmod), or
your module
On 8/6/07, Sven Mueller [EMAIL PROTECTED] wrote:
Oliver Endriss wrote on 05/08/2007 06:14:
Sven Mueller wrote:
Oliver Endriss wrote on 01/08/2007 00:27:
Sven Mueller wrote:
Hi.
I don't know which hardware interrupts those are mapped from/to and
currently don't know how to find out.
Hi,
some firmware for DVB-T cards based on TDA10046 cannot be retrieved any longer
using Andrew de Quincey's
get_dvb_firmware script distributed within the linux kernel's Documentation/dvb
directory,
because the vendor has withdrawn the file fetched by the script and replaced by
an updated
Andreas Arens wrote:
Hi,
some firmware for DVB-T cards based on TDA10046 cannot be retrieved any
longer using Andrew de Quincey's
get_dvb_firmware script distributed within the linux kernel's
Documentation/dvb directory,
because the vendor has withdrawn the file fetched by the script and
Michael Krufky wrote:
Trent Piepho wrote:
On Mon, 6 Aug 2007, e9hack wrote:
Michael Krufky schrieb:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6
Should we be
Oliver Endriss wrote:
Michael Krufky wrote:
Trent Piepho wrote:
On Mon, 6 Aug 2007, e9hack wrote:
Michael Krufky schrieb:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6
Michael Krufky wrote:
Oliver Endriss wrote:
Michael Krufky wrote:
Trent Piepho wrote:
On Mon, 6 Aug 2007, e9hack wrote:
Michael Krufky schrieb:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
Hi Trent,
Trent Piepho wrote:
On Mon, 6 Aug 2007, Chris Murton wrote:
Hi Trent,
Trent Piepho wrote:
On Mon, 6 Aug 2007, Chris Murton wrote:
Trent Piepho wrote:
DVB: Unable to find symbol mt2060_attach()
That is your problem. You didn't compile the mt2060 module, or it's not
installed,
On 8/7/07, Oliver Endriss [EMAIL PROTECTED] wrote:
I didn't see the ranges from the tuner, because the dvb-c drivers don't
use the pll framework. They
have very simple tuning functions only. We should use both values. One
part may be more restrictive
than the other one.
e9hack wrote:
Currently, I'm missing something in the tuner modules (and I didn't ask for
it). It isn't possible
to wait for getting the pll lock. The tuning function of the TT-C2300 does
wait. It isn't possible
to switch the time constant of the loop filter after getting the lock.
On 8/7/07, Trent Piepho [EMAIL PROTECTED] wrote:
Most demodulators don't have frequency ranges. They just take whatever the
tuner gives them at a fixed intermediate frequency. It's really the tuner
that has the frequency range.
Not true: look at the MB86A16. It is a DC (Direct Conversion)
On 8/6/07, Michael Krufky [EMAIL PROTECTED] wrote:
Now I'm beginning to have doubts about Oliver's original patch:
dvb_frontend: Range check of frequency and symbol rate
http://linuxtv.org/hg/v4l-dvb/rev/8186a34dd0a6
Should we be checking fe-ops.tuner_ops.info.frequency_min|max , instead of
On Tue, 7 Aug 2007, Manu Abraham wrote:
On 8/7/07, Trent Piepho [EMAIL PROTECTED] wrote:
Most demodulators don't have frequency ranges. They just take whatever the
tuner gives them at a fixed intermediate frequency. It's really the tuner
that has the frequency range.
Not true: look
Yeah, you're right... I just zoomed in on the image. The tuner is an XC5000.
Heh... Probably going to be quite a while before that PCI bridge is supported.
I don't see any demod, and I didnt read the Auvitek site yet, so I'll have to
assume that the bridge chip does ATSC demod as well.
Yeah,
70 matches
Mail list logo
