Hans Verkuil schrieb:
Hi all,
I've started this as a new thread to prevent polluting the discussions of the
media controller as a concept.
First of all, I have no doubt that everything that you can do with an ioctl,
you can also do with sysfs and vice versa. That's not the problem here.
The pr
Alexey Klimov schrieb:
On Sat, Aug 8, 2009 at 10:01 PM, Trent Piepho wrote:
On Sat, 8 Aug 2009, Alexey Klimov wrote:
Redesign radio->users counter. Don't allow more that 5 users on radio in
Why?
Well, v4l2 specs says that multiple opens are optional. Honestly, i
think tha
Why is the old dvb (linux-dvb) mailing list still alive?
One of the arguments migrating all dvb related stuff to this combined ml
was to reduce overhead.
But in fact some information might be lost now, since not everybody will
look at both ML's.
Wouldn't it be a good idea to close the old ml no
Edouard Lafargue wrote:
On Fri, Jun 19, 2009 at 1:43 PM, Hans Verkuil wrote:
On Friday 19 June 2009 13:36:49 wk wrote:
Is there anything planned/ongoing to support Radio Data System (RDS)
with ivtv supported cards?
Would be quite helpful for analogue radio channel scanning and finding
Hans Verkuil schrieb:
On Friday 19 June 2009 13:36:49 wk wrote:
Is there anything planned/ongoing to support Radio Data System (RDS)
with ivtv supported cards?
Would be quite helpful for analogue radio channel scanning and finding
the matching channel names.
Is there something out to be
Is there anything planned/ongoing to support Radio Data System (RDS)
with ivtv supported cards?
Would be quite helpful for analogue radio channel scanning and finding
the matching channel names.
Is there something out to be tested?
thanks,
Winfried
--
To unsubscribe from this list: send the lin
Hello Jelle,
> My w_scan version 20081106 stopped working on my Debian system. I had
> the following errors:
> ERROR: Sorry - i couldn't get any working frequency/transponder
>
> So I first checked if there was a wscan update.
No reception for some reason - probably the new version will show the
Benster & Jeremy wrote:
The patch works perfectly.
No indicator light, but 28 channels with stronger signal than mce!
Thanks again!
Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Devin Heitmueller wrote:
On Tue, Mar 24, 2009 at 12:35 PM, wk wrote:
While trying to update an application to API v5 some question arised.
Which type of "delivery_system" should be set for ATSC?
says...
SYS_DVBC_ANNEX_AC, <- european DVB-C
SYS_DVBC_ANNEX_B, <- a
While trying to update an application to API v5 some question arised.
Which type of "delivery_system" should be set for ATSC?
says...
SYS_DVBC_ANNEX_AC, <- european DVB-C
SYS_DVBC_ANNEX_B, <- american ATSC QAM
..
SYS_ATSC, <- oops, here we have ATSC again, cable and terrestrial not
na
I have updated my compiled list of the various demods and how they
currently report SNR info (including feedback from people in the last
round).
http://www.devinheitmueller.com/snr.txt
What about signal strength and BER readout in parallel for each device
listed here?
Needs the same docs
Benjamin Zores schrieb:
wk wrote:
Then there must be something ``wrong'' with `w_scan' making
incorrect assumptions about the data which it's parsing.
No - i do not think so.
All of the frequencies found are with 166kHz offset.
w_scan does not use any of these 166k
Then there must be something ``wrong'' with `w_scan' making
incorrect assumptions about the data which it's parsing.
No - i do not think so.
All of the frequencies found are with 166kHz offset.
w_scan does not use any of these 166k offsets, that means this frequency
data was transmitted as
I have some table frequency list here:
http://www.tvnt.net/V2/pages/342/medias/pro-bo-doc-tk-frequences_tnt.pdf
See the "Canal" array, page 20 for "Strasbourg".
I don't know how to determine transponders frequencies from this list.
Please find also the remark inside the file:
"(9) The frequ
by
parsing the NIT ot this channel.
Current w_scan doesn't use +/-167k offsets.
Since in Germany no transmitter uses any freq offsets, the information
comes from the French one.
And for France finding that freq offsets is quite normal.
--wk
--
To unsubscribe from this list: send the
Devin Heitmueller schrieb:
On Fri, Mar 13, 2009 at 6:27 PM, VDR User wrote:
Just wanted to comment that I'm glad there is a lot of interest in
this. I've heard endless talk & confusion on the user end over the
years as to the accuracy of the values, or in some cases (as with
Genpix adapters
Mauro Carvalho Chehab schrieb:
Hi wk,
Let's commit what we currently have. Could you please re-submit the patch
again, this time providing a proper description, and your SOB?
Cheers,
Mauro.
The attached patch provides the following changes to DVB API:
- files changed
- dvbap
Mauro Carvalho Chehab schrieb:
On Mon, 09 Mar 2009 19:46:34 -0400
Andy Walls wrote:
and integrating it into the existing v4l docbook,
I'm not sure of the value in that.
The DVB conversion to docbook allows us to add it at the kernel docbook docs
(probably, not the entire doc
Devin Heitmueller schrieb:
On Mon, Mar 9, 2009 at 6:03 PM, wk wrote:
Its a bad idea to expect someone else, the magic volunteer, doing work with
*deep impact* on the dvb driver API structure or documentation.
Working on this topic determines complete usability of the driver, so MAIN
I think so. The better would be to convert DVB api to docbook (as used
by all other kernel documents), and add a developers document for the
kernel API for both at the kernel documentation structure).
However, this is a huge task that someone should volunteer for doing,
otherwise, it won't h
Hans Verkuil wrote:
Hi Mauro,
I noticed that there is an ancient V4L2 spec in our tree in the v4l/API
directory. Is that spec used in any way? I don't think so, so I suggest
that it is removed.
The V4L1 spec that is there should probably be moved to the v4l2-spec
directory as that is where
Why do I have a feeling even the updated doc will be full of spelling
& grammatical errors? ;)
Probably, because none of the writers so far where native English.
Therefore i'am really happy that *you* now took over all the
responsibility to find all that spelling and grammatical errors.
Mauro Carvalho Chehab wrote:
+
+For this API documentation applies an even/odd versioning scheme, stating
+unstable or stable versions of that API. Only stable API versions should
+be used for developing drivers and applications.
Hmm... I wouldn't add the above. I don't think we should use
Should we drop support for kernels <2.6.22 in our v4l-dvb repository?
_: Yes
_: No
YES.
Optional question:
Why:
I assume that the main goal should be development of linux v4l/dvb
drivers to be included in *new* kernel versions. These dont need compat
code.
But beside of the main g
Since dvb-api doc is still outdated by six years...
The following patch changes dvbapi.pdf as following:
___
- change from twosided book format to singlesided book format.
* By doing so, the readability is improved and
Hans Verkuil wrote:
Comments?
Hans
As only beeing reader of this list.., why not simply reduce the work load by
- reducing the number of supported kernel versions to five major
versions? Currently 2.6.28 would mean down to 2.6.23,
this would be enough cover all nearly up-to-date d
Some time ago two new members were added in frontend.h to
enum fe_code_rate:
- FEC_3_5
- FEC_9_10
But the matching capability flags for that are still missing, signalling
applications support for those:
- FE_CAN_FEC_3_5
- FE_CAN_FEC_9_10
It would be possible to use 0x100, 0x200 f
Mauro Carvalho Chehab wrote:
On Mon, 16 Feb 2009 23:50:50 +0100
Hans Verkuil wrote:
Hi all,
I've made a v4l-dvb tree containing the old DVB API sources as found here:
http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/doc/dvbapi/.
This tree is here: http://www.linuxtv.org/hg/~hverkuil/v4l-d
Devin Heitmueller wrote:
As always we continue to welcome patches, including for the
documentation. Instead of bitching and moaning, how about you roll up
your sleeves and actually help out?
Let's try to remember that pretty much all the developers here are
volunteers, so berating them for not
The last week two guys were kindly asking here on the list where to find
a written DVB-API v5 documentation,
but nobody of the dvb driver community was answering.
http://www.mail-archive.com/linux-media@vger.kernel.org/msg01350.html
http://www.mail-archive.com/linux-media@vger.kernel.org/msg0130
Hello,
I'm running Ubuntu 8.10, and 2.6.27-11-generic kernel. I also tried
compiling the newest modules from linuxtv.
The first problem:
The sound from my HVR1300 is really bad, it like a robotic sound, with
high tones in it!
2nd problem:
cx88-alsa module is not loading automaticly when b
I'm trying to use the cx88_blackbird mpeg encoder on a hvr-1300.
I'm able to get a picture if i'm tuning to a tv frequency, but no sound
(but audio noise, so the mpeg encoder itself works).
Please note: that card supports DVB-T, PAL-{b/g,d/k,-50,-60} and CCIR
L/L' and FM radio,
see datasheet fro
32 matches
Mail list logo
