2011/3/18 Antti Palosaari :
> On 03/08/2011 12:12 AM, adq wrote:
>>
>> Ah well, so its definitely /not/ conflicting i2c writes that cause the
>> tuner problem as it has finally just died. The festats for a "crashed"
>> tuner are:
>> Sig: 50933 SNR: 50 BER: 0 UBLK: 5370554 Stat: 0x01 [SIG ]
>>
An usb_submit_urb should be atomic in a completion handler. This fixes
"BUG: scheduling while atomic" messages.
Signed-off-by: Pete Eberlein
diff --git a/drivers/media/video/s2255drv.c b/drivers/media/video/s2255drv.c
index f5a46c4..85c3158 100644
--- a/drivers/media/video/s2255drv.c
+++ b/drive
Hi,
sparse lead me to what looks like a typo in dib0700_devices.c:
drivers/media/dvb/dvb-usb/dib0700_devices.c:2160:18: warning: Initializer entry
defined twice
drivers/media/dvb/dvb-usb/dib0700_devices.c:2165:18: also defined here
2160.agc1_pt1 = 0,
.
On Fri, 1 Apr 2011 17:58:44 -0600
Grant Likely wrote:
> On Fri, Apr 1, 2011 at 5:52 PM, Samuel Ortiz
> wrote:
> > On Fri, Apr 01, 2011 at 11:56:35AM -0600, Grant Likely wrote:
> >> On Fri, Apr 1, 2011 at 11:47 AM, Andres Salomon
> >> wrote:
> >> > On Fri, 1 Apr 2011 13:20:31 +0200
> >> > Samuel
On Fri, Apr 1, 2011 at 5:52 PM, Samuel Ortiz wrote:
> On Fri, Apr 01, 2011 at 11:56:35AM -0600, Grant Likely wrote:
>> On Fri, Apr 1, 2011 at 11:47 AM, Andres Salomon wrote:
>> > On Fri, 1 Apr 2011 13:20:31 +0200
>> > Samuel Ortiz wrote:
>> >
>> >> Hi Grant,
>> >>
>> >> On Thu, Mar 31, 2011 at 0
On Fri, Apr 01, 2011 at 11:56:35AM -0600, Grant Likely wrote:
> On Fri, Apr 1, 2011 at 11:47 AM, Andres Salomon wrote:
> > On Fri, 1 Apr 2011 13:20:31 +0200
> > Samuel Ortiz wrote:
> >
> >> Hi Grant,
> >>
> >> On Thu, Mar 31, 2011 at 05:05:22PM -0600, Grant Likely wrote:
> > [...]
> >> > Gah. No
On 2 April 2011 04:16, Vishal Rao wrote:
> Hello,
>
> I just got a Gadmei 382 model tv tuner card and tried it with Ubuntu
> 11.04 beta 1 with no luck.
>
> Grepping through the em28xx driver sources I see potential areas where
> this device can be added:
>
> vishal@thunderbird:/media/data/SRC/linu
Hello,
I just got a Gadmei 382 model tv tuner card and tried it with Ubuntu
11.04 beta 1 with no luck.
Grepping through the em28xx driver sources I see potential areas where
this device can be added:
vishal@thunderbird:/media/data/SRC/linux-media-2011-04-01/drivers/media/video/em28xx$
grep -i ga
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:Fri Apr 1 19:00:36 CEST 2011
git hash:28df73703e738d8ae7a958350f74b08b2e9fe9ed
gcc version: i686-linux-gcc (GCC) 4.5
On Fri, Apr 01, 2011 at 10:47:56AM -0700, Andres Salomon wrote:
> On Fri, 1 Apr 2011 13:20:31 +0200
> Samuel Ortiz wrote:
>
> > Hi Grant,
> >
> > On Thu, Mar 31, 2011 at 05:05:22PM -0600, Grant Likely wrote:
> [...]
> > > Gah. Not all devices instantiated via mfd will be an mfd device,
> > > wh
On Fri, Apr 1, 2011 at 11:56 AM, Grant Likely wrote:
> On Fri, Apr 1, 2011 at 11:47 AM, Andres Salomon wrote:
>> On Fri, 1 Apr 2011 13:20:31 +0200
>> Samuel Ortiz wrote:
>>
>>> Hi Grant,
>>>
>>> On Thu, Mar 31, 2011 at 05:05:22PM -0600, Grant Likely wrote:
>> [...]
>>> > Gah. Not all devices in
On Fri, Apr 1, 2011 at 11:47 AM, Andres Salomon wrote:
> On Fri, 1 Apr 2011 13:20:31 +0200
> Samuel Ortiz wrote:
>
>> Hi Grant,
>>
>> On Thu, Mar 31, 2011 at 05:05:22PM -0600, Grant Likely wrote:
> [...]
>> > Gah. Not all devices instantiated via mfd will be an mfd device,
>> > which means that
On Fri, 1 Apr 2011 13:20:31 +0200
Samuel Ortiz wrote:
> Hi Grant,
>
> On Thu, Mar 31, 2011 at 05:05:22PM -0600, Grant Likely wrote:
[...]
> > Gah. Not all devices instantiated via mfd will be an mfd device,
> > which means that the driver may very well expect an *entirely
> > different* platfor
Some v4l drivers currently don't initialize their struct v4l2_subdev
with zeros, and this is a problem since some of the v4l2 code expects
this. One example is the addition of internal_ops in commit 45f6f84,
after that we are at risk of random oopses with these drivers when code
in v4l2_device_regi
> From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
>
> Hi Kamil,
Hi Laurent,
>
> Thanks for the RC. Here are some comments (more might come later when I'll
> get
> a better understanding of some MPEG4 and H264 concepts :-)).
Thank you for your comments. I have answered them be
On Fri, Apr 01, 2011 at 05:05:27PM +0200, Hans Verkuil wrote:
> On Friday, April 01, 2011 16:24:17 Herton Ronaldo Krzesinski wrote:
> > Many v4l drivers currently don't initialize their struct v4l2_subdev
> > with zeros, so since the addition of internal_ops in commit 45f6f84, we
> > are at risk of
On Friday, April 01, 2011 16:24:17 Herton Ronaldo Krzesinski wrote:
> Many v4l drivers currently don't initialize their struct v4l2_subdev
> with zeros, so since the addition of internal_ops in commit 45f6f84, we
> are at risk of random oopses when code in v4l2_device_register_subdev
> tries to der
Herton Ronaldo Krzesinski wrote:
>Hi,
>
>Recently I received a report about crashes with mxb v4l driver
>(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/745213), there
>are
>two slightly different reported crashes which I paste here:
>
>1) BootDmesg.txt crash:
>
>[ 21.210232] general prot
Many v4l drivers currently don't initialize their struct v4l2_subdev
with zeros, so since the addition of internal_ops in commit 45f6f84, we
are at risk of random oopses when code in v4l2_device_register_subdev
tries to dereference sd->internal_ops->*, as can be shown by the report
at http://bugs.l
Hi,
Recently I received a report about crashes with mxb v4l driver
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/745213), there are
two slightly different reported crashes which I paste here:
1) BootDmesg.txt crash:
[ 21.210232] general protection fault: [#1] SMP
[ 21.210292] l
This patch extends the videobuf2 framework with new helper functions and
modifies existing ones to support multi-size video-buffers.
Signed-off-by: Guennadi Liakhovetski
---
v2: fix offset calculation in __setup_offsets()
drivers/media/video/videobuf2-core.c | 195
On Fri, 2011-04-01 at 00:51 +0200, Michal Nazarewicz wrote:
> On Fri, 01 Apr 2011 00:26:51 +0200, Dave Hansen
> wrote:
> >> Bug in the above place does not mean that we could not allocate
> >> memory. It means caller is broken.
> >
> > Could you explain that a bit?
> >
> > Is this a case wher
Hi Grant,
On Thu, Mar 31, 2011 at 05:05:22PM -0600, Grant Likely wrote:
> On Wed, Feb 02, 2011 at 08:08:12PM -0800, Andres Salomon wrote:
> >
> > No need to explicitly set the cell's platform_data/data_size.
> >
> > In this case, move the various platform_data pointers
> > to driver_data. All o
Hi Kamil,
Thanks for the RC. Here are some comments (more might come later when I'll get
a better understanding of some MPEG4 and H264 concepts :-)).
On Tuesday 29 March 2011 11:48:03 Kamil Debski wrote:
> Hi,
>
> I would like to propose a new set of controls for codec devices. By codec
> devic
Hello,
On Friday, April 01, 2011 10:49 AM Jonghun Han wrote:
> On Wednesday, March 30, 2011 4:01 PM Marek Szyprowski wrote:
> > Hello,
> >
> > On V4L2 brainstorming meeting in Warsaw we discussed the need of a
> > framebuffer userspace interface for video output devices. Such
> > framebuffer inte
Hello,
On Friday, April 01, 2011 10:36 AM Jonghun Han wrote:
> On Wednesday, March 30, 2011 4:01 PM Marek Szyprowski wrote:
> >
> > This patch adds generic frame buffer emulator for any video output device
> > that uses videobuf2 framework. This emulator assumes that the driver is
> > capable of
Hi Marek,
On Wednesday, March 30, 2011 4:01 PM Marek Szyprowski wrote:
> Hello,
>
> On V4L2 brainstorming meeting in Warsaw we discussed the need of a
> framebuffer userspace interface for video output devices. Such
> framebuffer interface is aimed mainly for legacy applications and/or
> interop
Hi Marek,
Here is my comments.
On Wednesday, March 30, 2011 4:01 PM Marek Szyprowski wrote:
>
> This patch adds generic frame buffer emulator for any video output device
> that uses videobuf2 framework. This emulator assumes that the driver is
> capable of working in single-buffering mode and u
With this patch it is possible to prequeue buffers of different sizes
in the driver and switch between them by just stopping streaming,
setting a new format, queuing the suitable buffers and re-starting the
streaming escaping the need to allocate buffers on this time-critical
path.
Signed-off-by:
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/video/soc_camera.c | 46 -
1 files changed, 44 insertions(+), 2 deletions(-)
diff --git a/drivers/media/video/soc_camera.c b/drivers/media/video/soc_camera.c
index 11f0f1e..6a41e89 100644
--- a/drivers/m
This patch extends the videobuf2 framework with new helper functions and
modifies existing ones to support multi-size video-buffers.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/video/videobuf2-core.c | 184 ++
include/media/videobuf2-core.h | 1
A possibility to preallocate and initialise buffers of different sizes
in V4L2 is required for an efficient implementation of asnapshot mode.
This patch adds three new ioctl()s: VIDIOC_CREATE_BUFS,
VIDIOC_DESTROY_BUFS, and VIDIOC_SUBMIT_BUF and defines respective data
structures.
Signed-off-by: Gu
Hi all
As discussed at the last V4L2 meeting in Warsaw, one of the prerequisites
to support fast switching between different image formats is an ability to
preallocate buffers of different sizes and handle them over to the driver
in advance. This avoids the need to allocate buffers at the time
33 matches
Mail list logo
