On Wednesday, August 10, 2011 01:37:27 Sakari Ailus wrote:
On Tue, Aug 09, 2011 at 09:26:30AM +0200, Hans Verkuil wrote:
...
Wouldn't that be a security issue ? Any application with permissions to
access
the video device could DoS the system.
How is this any different from an
The following changes since commit
46540f7ac646ada7f22912ea7ea9b761ff5c4718:
[media] ir-mce_kbd-decoder: include module.h for its facilities (2011-07-29
12:52:23 -0300)
are available in the git repository at:
git://linuxtv.org/jfrancois/gspca.git for_v3.1
Jean-François Moine (2):
Hi,
On 08/10/2011 02:34 AM, Theodore Kilgore wrote:
snip
but this is the way how
the current discussion feels to me. If we agree on aiming for
doing it right then with that comes to me doing a software
design from scratch, so without taking into account what is
already there.
Here, a
Videobuf2 accepted any userptr buffer without verifying if its size is
large enough to store the video data from the driver. The driver reports
the minimal size of video data once in queue_setup and expects that
videobuf2 provides buffers that match these requirements. This patch
adds the required
Just one comment:
On Wednesday, August 10, 2011 10:21:28 Marek Szyprowski wrote:
Videobuf2 accepted any userptr buffer without verifying if its size is
large enough to store the video data from the driver. The driver reports
the minimal size of video data once in queue_setup and expects that
Hello,
On Wednesday, August 10, 2011 10:46 AM Hans Verkuil wrote:
Just one comment:
On Wednesday, August 10, 2011 10:21:28 Marek Szyprowski wrote:
Videobuf2 accepted any userptr buffer without verifying if its size is
large enough to store the video data from the driver. The driver
Both driver has been merged to v3.1-rc1, so add its authors as maintainers.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Kamil Debski k.deb...@samsung.com
Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
On Tuesday, August 09, 2011 06:36:19 pm nitesh moundekar wrote:
I am worried about direction v4l2 is taking. It looks against the basic
principle of driver i.e. hardware abstraction.
There definitely should be an API which is hardware independent.
However, the problem is that the hardware is
On Wednesday, August 10, 2011 11:08:20 Marek Szyprowski wrote:
Hello,
On Wednesday, August 10, 2011 10:46 AM Hans Verkuil wrote:
Just one comment:
On Wednesday, August 10, 2011 10:21:28 Marek Szyprowski wrote:
Videobuf2 accepted any userptr buffer without verifying if its size is
dvb_usb_device_init calls the frontend_attach method of this driver which
uses vp7045_usb_ob. In order to have a buffer ready in vp7045_usb_op, it has to
be allocated before that happens.
Luckily we can use the whole private data as the buffer as it gets separately
allocated on the heap via
nitesh moundekar wrote:
Hi Sakari,
Hi Nitesh,
So without touching these controls, drivers should be able to work with
default or internal settings calculated from frame rate and resolution. And
when application like DSLR wants more control it can access those controls.
The current interface
Hello, Sakari.
I would like to understand how to use subdevice (like adp1653) in
current v4l2 framework from user space.
My understanding is following.
Kernel has two drivers (simplified view):
- camera device
- flash device
Kernel initializes a camera driver from a platform specific setup
Em 10-08-2011 05:41, Sylwester Nawrocki escreveu:
Why not? I never saw an embedded hardware that allows physically changing
the
sensor.
I understood Laurent's statement that you can have same ISP driver deployed on
multiple boards fitted with various sensors. Hence the multiple
This patchset fixes the occasional failure of CCDC capture during
suspend/resume.
Cc: Vaibhav Hiremath hvaib...@ti.com
Cc: Abhilash K V abhilash...@ti.com
---
Abhilash K V (2):
omap3: ISP: Fix the failure of CCDC capture during suspend/resume
omap3: ISP: Kernel crash when attempting suspend
From: Abhilash K V abhilash...@ti.com
While resuming from the suspended to memory state,
occasionally CCDC fails to get enabled and thus fails
to capture frames any more till the next suspend/resume
is issued.
This is a race condition which happens only when a CCDC
frame-completion ISR is pending
From: Abhilash K V abhilash...@ti.com
This patch fixes the kernel crash introduced by the previous
patch:
omap3: ISP: Fix the failure of CCDC capture during
suspend/resume.
This null pointer exception happens when attempting suspend
while the ISP driver is not being used. The
On Tue, 9 Aug 2011, Hans de Goede wrote:
Hi,
On 08/09/2011 04:19 PM, Alan Stern wrote:
On Tue, 9 Aug 2011, Hans de Goede wrote:
According to Theodore, we have developed 5 drivers for them because the
stillcam modes in different devices use four different vendor-specific
drivers.
On Wed, 10 Aug 2011, Alan Stern wrote:
On Tue, 9 Aug 2011, Hans de Goede wrote:
Hi,
On 08/09/2011 04:19 PM, Alan Stern wrote:
On Tue, 9 Aug 2011, Hans de Goede wrote:
According to Theodore, we have developed 5 drivers for them because the
stillcam modes in different devices
On Wed, 10 Aug 2011, Theodore Kilgore wrote:
Okay, I didn't realize that the different cameras used different webcam
drivers as well as different stillcam drivers.
Oh, yes. They are Proprietary devices. And that means what it says. :-)
And all different from each other, too.
As far
On Wed, 10 Aug 2011, Alan Stern wrote:
On Wed, 10 Aug 2011, Theodore Kilgore wrote:
Okay, I didn't realize that the different cameras used different webcam
drivers as well as different stillcam drivers.
Oh, yes. They are Proprietary devices. And that means what it says. :-)
And
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:Wed Aug 10 19:00:41 CEST 2011
git hash:9bed77ee2fb46b74782d0d9d14b92e9d07f3df6e
gcc version: i686-linux-gcc (GCC)
On Wednesday, August 10, 2011 20:33:25 Theodore Kilgore wrote:
On Wed, 10 Aug 2011, Alan Stern wrote:
On Wed, 10 Aug 2011, Theodore Kilgore wrote:
Okay, I didn't realize that the different cameras used different webcam
drivers as well as different stillcam drivers.
Oh,
On Wed, Aug 10, 2011 at 01:33:25PM -0500, Theodore Kilgore wrote:
-- moving the kernel webcam drivers out of the kernel and doing with these
cameras _everything_ including webcam function through libusb. I myself do
not have the imagination to be able to figure out how this could be done
On Wednesday, August 10, 2011 21:27:35 Hans Verkuil wrote:
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:Wed Aug 10 19:00:41 CEST 2011
git hash:
Em 10-08-2011 15:33, Theodore Kilgore escreveu:
Hans seems to have argued cogently for doing all of this in the kernel and
for abandoning the usbfs-based drivers for these particular drivers for
dual-mode cameras and, I would conjecture, for drivers for dual-mode
hardware in general.
On Wed, 10 Aug 2011, Greg KH wrote:
On Wed, Aug 10, 2011 at 01:33:25PM -0500, Theodore Kilgore wrote:
-- moving the kernel webcam drivers out of the kernel and doing with these
cameras _everything_ including webcam function through libusb. I myself do
not have the imagination to be
On Wed, 10 Aug 2011, Mauro Carvalho Chehab wrote:
Em 10-08-2011 15:33, Theodore Kilgore escreveu:
Hans seems to have argued cogently for doing all of this in the kernel and
for abandoning the usbfs-based drivers for these particular drivers for
dual-mode cameras and, I would
[ 1736.936937] em28xx: New device USB 2870 Device @ 480 Mbps
(eb1a:2870, interface 0, class 0)
[ 1736.941002] em28xx #0: chip ID is em2870
[ 1737.100772] em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 70 28 c0 12
62 00 6a 22 00 00
[ 1737.100796] em28xx #0: i2c eeprom 10: 00 00 04 57 00 1d 00 00 00 00
On 08/08/2011 19:06, Nima Mohammadi wrote:
Hi folks,
I was reading the source code of various dvb related utilities and I
was wondering about forming up the message which instructs the DiSEqC
switch. But I found out that different programs produce the command
differently.
The confusing thing
On Tuesday 09 August 2011, Hans de Goede wrote:
Hi,
On 08/09/2011 10:31 PM, Adam Baker wrote:
On Tuesday 09 August 2011, Hans de Goede wrote:
snip
It has also just occured to me that it might be possible to solve the
issues we are facing just in the kernel. At the moment when the
On 03/21/2011 08:46 PM, Rico Tzschichholz wrote:
Hello,
I would like to know if there is any intention to include this patch
soon? https://patchwork.kernel.org/patch/244201/
Currently using 2.6.38 results in switching-timeouts on my S2-3200 and
this patch fixes this for good.
So it would be
31 matches
Mail list logo
