Hi Laurent,
On Sat, Apr 4, 2015 at 3:44 PM, Laurent Pinchart
wrote:
> I'm not sure that adding a device-specific quirk is the bast way to handle
> this problem, as it wouldn't really scale if other devices expose buggy
> descriptors. A more generic way to patch or override descriptors might be
>
.
Signed-off-by: Daniel Drake
---
drivers/media/usb/uvc/uvc_driver.c | 36
drivers/media/usb/uvc/uvcvideo.h | 1 +
2 files changed, 37 insertions(+)
diff --git a/drivers/media/usb/uvc/uvc_driver.c
b/drivers/media/usb/uvc/uvc_driver.c
index cf27006
The code attempts to maintain a "user format" and a "sensor format",
but in this case it looks like a typo is passing the user format down
to the sensor.
This was preventing display of video at anything other than 640x480.
Signed-off-by: Daniel Drake
---
drivers/media/video
The code attempts to maintain a "user format" and a "sensor format",
but in this case it looks like a typo is passing the user format down
to the sensor.
This was preventing display of video at anything other than 640x480.
Signed-off-by: Daniel Drake
---
drivers/media/video
On Wed, May 16, 2012 at 3:12 PM, Jonathan Corbet wrote:
> On Tue, 15 May 2012 20:43:31 +0100 (BST)
> Daniel Drake wrote:
>
>> Jon, is it OK to assume that XO-1.75 is the only mmp-camera user?
>
> It's the only one I know of at the moment, certainly.
>
> Even so,
this information to the ov7670 driver, to fix an issue where
a framerate faster than the requested amount was being provided.
Signed-off-by: Daniel Drake
---
drivers/media/video/marvell-ccic/mmp-driver.c |7 +++
1 file changed, 7 insertions(+)
Jon, is it OK to assume that XO-1.75 is the
On Mon, Apr 30, 2012 at 5:27 PM, Jonathan Corbet wrote:
> On Mon, 30 Apr 2012 23:06:27 +0100 (BST)
> Daniel Drake wrote:
>
>> For the ov7670 camera to return images at the requested frame rate,
>> it needs to make calculations based on the clock speed, which is
>> a
this information to the ov7670 driver, to fix an issue where
a framerate of 3x the requested amount was being provided.
Signed-off-by: Daniel Drake
---
drivers/media/video/via-camera.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/media/video/via
dealing with. Work around this
problem by disabling RGB support. YUYV scaling works just fine.
Test case:
gst-launch v4l2src ! video/x-raw-rgb,bpp=16,width=320,height=240 ! \
ffmpegcolorspace ! xvimagesink
Signed-off-by: Daniel Drake
---
drivers/media/video/via-camera.c | 10
Hi Jon,
We're dealing with a via-camera issue from the Scratch application.
The latest version of scratch uses libv4l2 and requests RGB24 images
as that is what it uses internally.
via-camera/ov7670 doesn't support RGB24 but libv4l2 kicks in with its
format conversion and chooses RGB565, which we
This enables module autoloading.
Signed-off-by: Daniel Drake
---
drivers/media/video/marvell-ccic/mmp-driver.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/marvell-ccic/mmp-driver.c
b/drivers/media/video/marvell-ccic/mmp-driver.c
index d6b7645
This fixes autoloading of the module.
Signed-off-by: Daniel Drake
---
drivers/media/video/via-camera.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/via-camera.c b/drivers/media/video/via-camera.c
index 8c780c2..85d3048 100644
--- a/drivers/media
On 10 March 2011 16:24, Jonathan Corbet wrote:
> Did the check need to move for some reason? If so, a one-of-these-days
> nice feature might be to allow changing override_serial at run time.
Yes. Otherwise the check would execute if that driver is loaded on
XO-1. The check either had to be modif
eliminate this code when CONFIG_OLPC=n
(due to machine_is_olpc() always returning false).
Signed-off-by: Daniel Drake
---
drivers/media/video/via-camera.c | 83 +-
1 files changed, 37 insertions(+), 46 deletions(-)
diff --git a/drivers/media/video/via-camera.c
Add suspend/resume support to the via-camera driver, so that the video
continues streaming over a suspend-resume cycle.
Originally implemented by Jon Corbet.
Signed-off-by: Daniel Drake
---
drivers/media/video/via-camera.c | 64 ++
1 files changed, 64
Hi,
>> Another reason why s_config is a bad idea.
Thanks a lot for working on this. I had a quick look and don't have
any objections.
>> This has been extensively tested on my humble OLPC laptop (and it took me 4-5
>> hours just to get the damn thing up and running with these drivers).
In futur
On 28 October 2010 20:08, Jonathan Corbet wrote:
> This makes every user carry a bit of OLPC-specific code. But there are
> no non-OLPC users currently, the code is small, and we get rid of some
> #ifdefs, which is always a good thing. Seems good to me.
I think the compiler might be smart enoug
I can reproduce a crash on via-camera module unload. Running latest
linux-next. Simple modprobe then rmmod reproduces it.
I guess cafe_ccic is affected too.
BUG: unable to handle kernel paging request at 6b6b6b6b
IP: device_del
I've diagnosed it, but don't know the solution.
viacam_remove() call
6 so there won't be any problems including
the olpc.h header directly.
Signed-off-by: Daniel Drake
---
drivers/media/video/via-camera.c | 82 ++
1 files changed, 39 insertions(+), 43 deletions(-)
diff --git a/drivers/media/video/via-camera.c b/drivers/
http://dev.laptop.org/ticket/10190
Signed-off-by: Daniel Drake
---
drivers/media/video/cafe_ccic.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/video/cafe_ccic.c b/drivers/media/video/cafe_ccic.c
index 7bc3667..d147525 100644
--- a/drivers/media/video
For some reason, commit 1aafeb30104a is missing one change that was
included in the email submission.
The sensor configuration must be passed down to the ov7670 subdev.
Signed-off-by: Daniel Drake
---
drivers/media/video/cafe_ccic.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions
Force smbus communication, disable QCIF mode, and set the correct
clock speed on the OLPC XO-1.
Signed-off-by: Daniel Drake
---
drivers/media/video/cafe_ccic.c | 33 +++--
1 files changed, 31 insertions(+), 2 deletions(-)
diff --git a/drivers/media/video
probe routine had to be moved later (into s_config),
because we can't do any I/O until we know which I/O method has been
selected through this mechanism.
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c | 133 ++
drivers/media/video/ov767
The QVGA mode has a green horizontal line on the left hand side, and a red
(or sometimes blue) vertical line at the bottom. Tweak the visible area
to remove them.
Thanks to Mauro for explaining how to fix this.
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c |8
1
On 8 October 2010 22:13, Jonathan Corbet wrote:
> A problem like that will be at the controller level, not the sensor
> level. Given that this is an XO-1 report, I'd assume something
> requires tweaking in the cafe_ccic driver. I wasn't aware of this; I
> know it worked once upon a time.
I repo
On 8 October 2010 22:11, Jonathan Corbet wrote:
> I'm certainly not attached to this mode, but...does it harm anybody if
> it's there?
Yes. Applications like gstreamer will pick this resolution if its the
closest resolution to the target file resolution. On XO-1 we always
pick a low res so gstrea
Hi,
The cafe_ccic + ov7670 combination is currently broken in mainstream
on the OLPC XO-1 laptop because of it's move to i2c (2bf7de4), in
order to work on the new XO-1.5 laptop. The smbus IO code was brought
back in 467142093 but this code is never triggered - CONFIG_OLPC_XO_1
doesn't exist.
I w
parameter wins over whatever we
might have set through the DMI table.
Based on earlier work by Jonathan Corbet.
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c | 71 -
1 files changed, 62 insertions(+), 9 deletions(-)
diff --git a/drivers/media
This super-low-resolution mode only captures from a small portion of
the sensor FOV, making it a bit useless.
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/media/video/ov7670.c b/drivers/media
Capturing at this resolution results in an ugly green horizontal line
at the left side of the image. Disable until fixed.
http://dev.laptop.org/ticket/10231
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a
Hi Mauro,
Just a quick reminder about 4 pending cafe_ccic/ov7670 patches, all
acked by Jon Corbet:
http://www.spinics.net/lists/linux-media/msg23371.html
http://www.spinics.net/lists/linux-media/msg23373.html
http://www.spinics.net/lists/linux-media/msg23372.html
http://www.spinics.net/lists/linu
delays before reading registers).
Reintroduce the 1-second CAFE_SMBUS_TIMEOUT to catch and avoid this
strange hardware bug.
Signed-off-by: Daniel Drake
---
drivers/media/video/cafe_ccic.c | 36 +---
1 files changed, 17 insertions(+), 19 deletions(-)
diff --git
From: Jonathan Corbet
Inquiring minds (and gstreamer) want to know.
Signed-off-by: Jonathan Corbet
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c | 21 ++---
1 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/media/video/ov7670.c b/drivers
GStreamer uses this.
Signed-off-by: Daniel Drake
---
drivers/media/video/ov7670.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/ov7670.c b/drivers/media/video/ov7670.c
index f551f63..214cebf 100644
--- a/drivers/media/video/ov7670
This allows GStreamer to pick appropriate framerates and resolutions
based on desired capture parameters.
Signed-off-by: Daniel Drake
---
drivers/media/video/cafe_ccic.c | 26 ++
1 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video
35 matches
Mail list logo