So, what do these two deep questions, which confound the assembled
wisdom of an entire list of Linux video developers, have to do with
tables in userspace? None that I can see, unless someone wants to
provide a mechanism for the information, having been collected in the
module, to be availab
Please, please, please, can we concentrate on the subject?
What I did with the other out-of-tree em28xx-new driver was that
I printed out the urb->kref.refcount before and after each urb operation.
The result was that when the urb->complete function is called, the reference
count was still 2, ins
On Wed, 25 Feb 2009, Mauro Carvalho Chehab wrote:
On Tue, 24 Feb 2009 20:12:00 -0600 (CST)
kilg...@banach.math.auburn.edu wrote:
For sure we need to have a way for retrieving this information for devices
like the sq905 cameras, where the information can't be currently be
determined by usersp
On Wed, 25 Feb 2009, Thomas Kaiser wrote:
Also an overview is often very helpful. Also trying to visualize what
might be needed in the future is helpful. All of this can be extremely
helpful. But not everyone can see or imagine every possible thing. For
example, it seems that some of the bes
On Wed, Feb 25, 2009 at 4:23 AM, Andrew Morton
wrote:
> On Wed, 25 Feb 2009 03:15:35 +0100 Markus Rechberger
> wrote:
>
>> On Wed, Feb 25, 2009 at 3:02 AM, Mauro Carvalho Chehab
>> wrote:
>> > On Tue, 24 Feb 2009 13:57:20 -0800
>> > Andrew Morton wrote:
>> >
>> >>> > In the output of /proc/sla
On Wed, Feb 25, 2009 at 1:06 AM, Markus Rechberger
wrote:
> On Tue, Feb 24, 2009 at 9:43 PM, Jonathan Johnson wrote:
>> Hello all,
>>
>> My vote is YES, why haven't we done this already??
>>
>> My understanding is that we are just drop old kernel support and retaining
>> the vast majority of the
On Wed, 25 Feb 2009 03:15:35 +0100 Markus Rechberger
wrote:
> On Wed, Feb 25, 2009 at 3:02 AM, Mauro Carvalho Chehab
> wrote:
> > On Tue, 24 Feb 2009 13:57:20 -0800
> > Andrew Morton wrote:
> >
> >>> > In the output of /proc/slab_allocators the number of blocks allocated by
> >> > usb_alloc_ur
On Tue, 24 Feb 2009 20:12:00 -0600 (CST)
kilg...@banach.math.auburn.edu wrote:
> > For sure we need to have a way for retrieving this information for devices
> > like the sq905 cameras, where the information can't be currently be
> > determined by userspace.
>
> Yes, indeed. Except for just o
Also an overview is often very helpful. Also trying to visualize what
might be needed in the future is helpful. All of this can be extremely
helpful. But not everyone can see or imagine every possible thing. For
example, it seems that some of the best minds in the business are
stunned when conf
On Wed, Feb 25, 2009 at 3:02 AM, Mauro Carvalho Chehab
wrote:
> On Tue, 24 Feb 2009 13:57:20 -0800
> Andrew Morton wrote:
>
>>> > In the output of /proc/slab_allocators the number of blocks allocated by
>> > usb_alloc_urb() increases, however, the xawtv is no longer running:
>> >
>> > size-2048:
On Tue, 24 Feb 2009 13:57:20 -0800
Andrew Morton wrote:
>> > In the output of /proc/slab_allocators the number of blocks allocated by
> > usb_alloc_urb() increases, however, the xawtv is no longer running:
> >
> > size-2048: 18 usb_alloc_dev+0x1d/0x212 [usbcore]
> > size-2048: 2280 usb_alloc_urb
On Tue, 24 Feb 2009, Mauro Carvalho Chehab wrote:
On Tue, 24 Feb 2009, kilg...@banach.math.auburn.edu wrote:
On Tue, 24 Feb 2009, Mauro Carvalho Chehab wrote:
On Mon, 23 Feb 2009, kilg...@banach.math.auburn.edu wrote:
Theodore,
You're considering just one subset of the V4L usa
Hans Verkuil wrote:
Hi all,
There are lot's of discussions, but it can be hard sometimes to actually
determine someone's opinion.
So here is a quick poll, please reply either to the list or directly to me
with your yes/no answer and (optional but welcome) a short explanation to
your standpo
On Tue, 24 Feb 2009, kilg...@banach.math.auburn.edu wrote:
On Tue, 24 Feb 2009, Mauro Carvalho Chehab wrote:
On Mon, 23 Feb 2009, kilg...@banach.math.auburn.edu wrote:
Theodore,
You're considering just one subset of the V4L usages: notebook webcams.
Actually, the sq905 cameras a
On Tue, 24 Feb 2009, Mauro Carvalho Chehab wrote:
On Mon, 23 Feb 2009, kilg...@banach.math.auburn.edu wrote:
Theodore,
You're considering just one subset of the V4L usages: notebook webcams.
Actually, the sq905 cameras are not "notebook webcams." They are cheap,
consumer entry level
On Tue, 24 Feb 2009 16:00:59 -0800
Auke Kok wrote:
> Auke Kok wrote:
> >
> > All,
> >
> > I have a "Creative Technology, Ltd Webcam Live!/Live! Pro" that until
> > recently worked fine with the out-of-tree gspcav1 driver
> > (gspcav1-20071224.tar.gz is the latest version I used unti 2.6.26).
On Tue, Feb 24, 2009 at 9:43 PM, Jonathan Johnson wrote:
> Hello all,
>
> My vote is YES, why haven't we done this already??
>
> My understanding is that we are just drop old kernel support and retaining
> the vast majority of the drivers.
> If anyone tallied the total number CVE listed vulernabi
Auke Kok wrote:
All,
I have a "Creative Technology, Ltd Webcam Live!/Live! Pro" that until
recently worked fine with the out-of-tree gspcav1 driver
(gspcav1-20071224.tar.gz is the latest version I used unti 2.6.26).
Since this driver (basically) got merged in the kernel I got my hopes up
t
Hi,
Am Dienstag, den 24.02.2009, 16:02 -0500 schrieb Michael Krufky:
> On Sun, Feb 22, 2009 at 5:15 AM, Hans Verkuil wrote:
> > Should we drop support for kernels <2.6.22 in our v4l-dvb repository?
> >
> > _: Yes
> > _: No
>
>
> NO.
>
this is an unwanted reply to Hans' polling, but I also sta
Currently soc-camera doesn't set up any image format without an explicit
S_FMT. According to the API this should be supported, for example,
capture-example.c from v4l2-apps by default doesn't issue an S_FMT. This
patch moves negotiating of available host-camera format translations to
probe() ti
On Tue, Feb 24, 2009 at 10:57 PM, Andrew Morton
wrote:
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Mon, 23 Feb 2009 22:08:37 -0800 (PST)
> bugme-dae...@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=127
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 23 Feb 2009 22:08:37 -0800 (PST)
bugme-dae...@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12768
There's additional info at the link.
>Summary: usb_
Hello all,
My vote is YES, why haven't we done this already??
My understanding is that we are just drop old kernel support and retaining the
vast majority of the drivers.
If anyone tallied the total number CVE listed vulernabilites and other problems
fixed since then they would probably be shoc
All,
I have a "Creative Technology, Ltd Webcam Live!/Live! Pro" that until
recently worked fine with the out-of-tree gspcav1 driver
(gspcav1-20071224.tar.gz is the latest version I used unti 2.6.26).
Since this driver (basically) got merged in the kernel I got my hopes up
that the in-kernel
On Sun, Feb 22, 2009 at 5:15 AM, Hans Verkuil wrote:
> Should we drop support for kernels <2.6.22 in our v4l-dvb repository?
>
> _: Yes
> _: No
NO.
> Optional question:
>
> Why:
Dropping support for older kernels means dropping support for MOST testers.
Sure, it's an inconvenience for the m
Hello,
I'm having some issues. Bad recordings, and always accompanied with the
following:
[10968.525453] saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting
for end of xfer
[10975.963186] saa7146 (2) vpeirq: used 55 times >80% of buffer (163372
bytes now)
[10977.657955] saa7146 (1) vpe
John Pilkington wrote:
Jean Delvare wrote:
* Enterprise-class distributions (RHEL, SLED) are not the right target
for the v4l-dvb repository, so we don't care which kernels these are
running.
I think you should be aware that the mythtv and ATrpms communities
include a significant number
On Sun, 2009-02-22 at 11:15 +0100, Hans Verkuil wrote:
> Hi all,
>
> There are lot's of discussions, but it can be hard sometimes to actually
> determine someone's opinion.
>
> So here is a quick poll, please reply either to the list or directly to me
> with your yes/no answer and (optional but
On Mon, 23 Feb 2009, kilg...@banach.math.auburn.edu wrote:
On Mon, 23 Feb 2009, Adam Baker wrote:
On Monday 23 February 2009, Mauro Carvalho Chehab wrote:
> On Sat, 21 Feb 2009 12:53:57 +0100
>
> Hans Verkuil wrote:
> > Hi Adam,
> >
> > Sorry for the late reply, it's been very busy.
Please reply to this poll if you haven't done so yet. I only count clear
yes/no answers, so if you replied earlier to this in order to discuss a
point then I haven't counted that.
Currently it's 16 yes and 2 no votes, but I'd really like to see some more
input. I want to post the final results
(This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.)
Results of the daily build of v4l-dvb:
date:Tue Feb 24 19:00:03 CET 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 10653:359d95e1d541
gcc version: gcc
On Sun, 22 Feb 2009, Hans Verkuil wrote:
> Hi Mauro,
>
> Please pull from http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-zoran for the
> following:
You might consider posting to the mjpeg users list. Maybe there are
some people who used the playback feature more often.
--
To unsubscribe from this l
2009/2/23 Mauro Carvalho Chehab :
> [...]
> Sebastian,
>
> could you please send it again, being sure that your email won't break long
> lines?
>
diff -uprN -X dontdiff.txt
a/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c
b/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c
--- a/linux/drivers/m
Linus,
if you don't mind receiving yet another new driver this late in the
game, then please pull from the firedtv-merge branch at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
firedtv-merge
to receive the following IEEE 1394 + DVB updates. More information
after
On Mon, Feb 23, 2009 at 05:58:54PM -0500, Devin Heitmueller wrote:
> On Mon, Feb 23, 2009 at 5:48 PM, David Engel wrote:
> > The BER isn't totally unreliable. Yes, when it's low, it does seem to
> > be meaningless. However, when it's high, as in my recent attempts to
> > try a 115 by itself, it
That's great, I really hope your patches finally find their way into
the main tree. I'm just tired of manually downloading & patching HG
sources everytime I needed to recompile the kernel...
Anyway, I've been using the card for some time now (almost a year,
IIRC...) and it runs very well in DVB-S
Add DVB support for Avermedia DVB-S Pro and
Avermedia DVB-S Hybrid+FM card both labled A700.
They use zl10313 demod (driver mt312) and zl10036 tuner.
Signed-off-by: Matthias Schwarzott
Index: v4l-dvb/linux/drivers/media/video/saa7134/Kconfig
=
This driver is based on initial work by Tino Reichardt and was heavily changed.
The datasheet of the zl10036 can be found here and on other places on the net:
http://www.mcmilk.de/projects/dvb-card/datasheets/ZL10036.pdf
The zl10038 is similar to the zl10036, so it is maybe possible to write a co
Hello all!
These patches finally add support for the DVB part of the
Avermedia A700 DVB-S cards.
The first adds the tuner-driver for the Zarlink zl10036.
The second adds the glue code to saa7134-dvb to use it.
After having them lying around a long time I now did a
bit of cleanup and send them ou
From: Beat Michel Liechti
I found that the function fdtv_frontend_init in the file firedtv-fe.c was
missing a case for FIREDTV_DVB_S2 which resulted in "frequency limits
undefined" errors in syslog.
Signed-off-by: Beat Michel Liechti
Change by Stefan R: combine it with case case FIREDTV_DVB_S
Hi Jean:
Jean Delvare wrote:
Hi John,
(re-adding linux-media on Cc as I doubt you dropped it on purpose...)
Right: I do subconsciously expect 'reply' to go to the list, and don't
always remember to check first. No doubt you got two copies.
On Tue, 24 Feb 2009 11:46:04 +, John Pilkingto
# HG changeset patch
# User Uri Shkolnik
# Date 1235483353 -7200
# Node ID ba9020b165e75b80e8c7b499e8068741982c44f6
# Parent 3caff6dae0753d2adb581b7ef5e309a1954820b2
Fixed use of freed memory in smsspicommon
From: Uri Shkolnik
Moved the handling of "unused bytes" before the reporting of messag
On Tue, Feb 24, 2009 at 10:17 PM, Guennadi Liakhovetski
wrote:
> On Mon, 23 Feb 2009, morimoto.kunin...@renesas.com wrote:
>
>>
>> Dear Guennadi.
>>
>> Now MigoR and AP325 board have ov772x camera.
>> However, the lens used is different.
>>
>> And I have a specific good setting value
>> for the le
On Sunday 22 of February 2009, Hans Verkuil wrote:
> Hi all,
>
> There are lot's of discussions, but it can be hard sometimes to actually
> determine someone's opinion.
>
> So here is a quick poll, please reply either to the list or directly to me
> with your yes/no answer and (optional but welcome
On Mon, 23 Feb 2009, morimoto.kunin...@renesas.com wrote:
>
> Dear Guennadi.
>
> Now MigoR and AP325 board have ov772x camera.
> However, the lens used is different.
>
> And I have a specific good setting value
> for the lens of AP325.
>
> So, I would like to add new function for
> specific le
Hi John,
(re-adding linux-media on Cc as I doubt you dropped it on purpose...)
On Tue, 24 Feb 2009 11:46:04 +, John Pilkington wrote:
> Jean Delvare wrote:
>
> > * Enterprise-class distributions (RHEL, SLED) are not the right target
> > for the v4l-dvb repository, so we don't care which ke
Jean Delvare wrote:
* Enterprise-class distributions (RHEL, SLED) are not the right target
for the v4l-dvb repository, so we don't care which kernels these are
running.
I think you should be aware that the mythtv and ATrpms communities
include a significant number of people who have chos
On 23 Feb, Beat Michel Liechti wrote at linux1394-devel:
> --- linux-2.6.28.5-firebranch/drivers/media/dvb/firewire/firedtv-fe.c.orig
> 2009-02-23 22:25:53.0 +0100
> +++ linux-2.6.28.5-firebranch/drivers/media/dvb/firewire/firedtv-fe.c
> 2009-02-23 22:29:10.0 +0100
> @@ -203,6
> can anyone use scan-s2 with cx24116 demodulator saccessfully?
yes, I'm using hvr4000 card with the latest scan-s2 and transponder list with
rolloff = 35 (NOT roll off = auto !!!)
succesfully
corrected transponder list with roll off = 25 for scan-s2 you can download from
here
http://vdr-setti
Hi,
Another way of controlling the numbering schema of your DVB
devices is to blacklist the modules (so udev doesn't load them)m and
then modprobing them manually at system startup. This is what I did
for my Nova T-500 and Avermedia A700.
Briefly (this is for Gentoo, running OpenRC):
In /etc/
50 matches
Mail list logo