Hi,
The KVM folks suggested that it would be good to get USB and
virtualization developers together to talk about how to virtualize the
xHCI host controller. The xHCI spec architect worked closely with
VMWare to get some extra goodies in the spec to help virtualization, and
I'd like to see th
Hi,
On 06/10/2011 02:21 AM, Sarah Sharp wrote:
I'm pleased to announce a USB mini-summit at LinuxCon Vancouver.
What: USB mini-summit
When: Tuesday, August 16th, all day
Where: At the conference venue, room TBD pending confirmation from
Angela Brown.
Proposed topics include USB vi
Hi all,
The current API for managing kernel -> userspace is a bit
rough around the edges, so I would like to discuss extending
the API.
First of all an example use case scenarios where the current API
falls short.
1) Redirection of USB devices to a virtual machine, qemu, vbox, etc.
all have the
Laurent Pinchart wrote:
> Hi Sakari,
>
> On Monday 16 May 2011 15:00:39 Sakari Ailus wrote:
>> This patch adds the driver for the adp1653 LED flash controller. This
>> controller supports a high power led in flash and torch modes and an
>> indicator light, sometimes also called privacy light.
>>
>
Hi,
On Fri, Jun 10, 2011 at 09:55:13AM +0200, Hans de Goede wrote:
> Currently this will cause the usb mass storage driver to see a
> disconnect, and any possible still pending writes are lost ...
>
> This is IMHO unacceptable, but currently there is nothing we can
> do to avoid this.
>
> 2) So
Hi,
On 06/10/2011 10:22 AM, Felipe Balbi wrote:
Hi,
On Fri, Jun 10, 2011 at 09:55:13AM +0200, Hans de Goede wrote:
Currently this will cause the usb mass storage driver to see a
disconnect, and any possible still pending writes are lost ...
This is IMHO unacceptable, but currently there is no
Hi,
On Fri, Jun 10, 2011 at 10:36:47AM +0200, Hans de Goede wrote:
> >On Fri, Jun 10, 2011 at 09:55:13AM +0200, Hans de Goede wrote:
> >>Currently this will cause the usb mass storage driver to see a
> >>disconnect, and any possible still pending writes are lost ...
> >>
> >>This is IMHO unaccepta
Jannis Achstetter web.de> wrote:
> [...] I can't
> test functionality right now since I'm not at home where the device is but I
> will test first thing when I get home.
The card works absolutely fine. So it's not more than applying a single patch
against 2.6.39.1 to get the card supported (+ a f
Hi Hans,
The v4l2_ctrl_new_std() doesn't allow setting the is_volatile bit in the
bit field. The adp1653 driver needs that for the faults control.
Would you prefer just setting the bit in the driver, or, as Laurent
suggested, a new v4l2_ctrl_new_std_volatile() function which would mark
the contro
On Fri, Jun 10, 2011 at 6:47 AM, Jonathan Corbet wrote:
> Hi, Kassey,
>
> I've been looking at the driver some to understand how you're using the
> hardware. One quick question:
>
>> The driver is based on soc-camera + videobuf2 frame
>> work, and only USERPTR is supported.
>
> Since you're limit
On Friday, June 10, 2011 10:47:09 Sakari Ailus wrote:
> Hi Hans,
>
> The v4l2_ctrl_new_std() doesn't allow setting the is_volatile bit in the
> bit field. The adp1653 driver needs that for the faults control.
>
> Would you prefer just setting the bit in the driver, or, as Laurent
> suggested, a n
On Fri, 10 Jun 2011, Kassey Lee wrote:
> hi, Guennadi:
>
> in drivers/media/video/soc_camera.c
> static int soc_camera_open(struct file *file)
>
> it will call soc_camera_set_fmt to configure the sensor and host controller.
> for sensor, this means it will trigger download setting, thi
Hi Mauro,
This patch series adds support for handling autofoo/foo type controls (e.g.
autogain/gain, autoexposure/exposure, etc) and adds a new event for control
changes, either a value or a status change.
The changes against the RFCv3 patch series are minor: one small bug was fixed
in the autofo
Hi Mauro,
This pull request adds the bitmask controls, flash API and the adp1653
driver. What has changed since the patches is:
- Adp1653 flash faults control is volatile. Fix this.
- Flash interface marked as experimental.
- Moved the DocBook documentation to a new location.
- The target version
From: KAMEZAWA Hiroyuki
This commit introduces alloc_contig_freed_pages() function
which allocates (ie. removes from buddy system) free pages
in range. Caller has to guarantee that all pages in range
are in buddy system.
Along with this function, a free_contig_pages() function is
provided which
From: Michal Nazarewicz
This commit adds a gen_pool_alloc_aligned() function to the
generic allocator API. It allows specifying alignment for the
allocated block. This feature uses
the bitmap_find_next_zero_area_off() function.
It also fixes possible issue with bitmap's last element being
not
From: Michal Nazarewicz
The MIGRATE_CMA migration type has two main characteristics:
(i) only movable pages can be allocated from MIGRATE_CMA
pageblocks and (ii) page allocator will never change migration
type of MIGRATE_CMA pageblocks.
This guarantees that page in a MIGRATE_CMA page block can
a
This patch is an example how CMA can be activated for particular devices
in the system. It creates one CMA region and assigns it to all s5p-fimc
devices on Samsung Aquila S5PC110 board.
Signed-off-by: Marek Szyprowski
Signed-off-by: Kyungmin Park
---
arch/arm/mach-s5pv210/Kconfig |1 +
From: Michal Nazarewicz
This commit adds a bitmap_find_next_zero_area_off() function which
works like bitmap_find_next_zero_area() function expect it allows an
offset to be specified when alignment is checked. This lets caller
request a bit such that its number plus the offset is aligned
accordi
From: Michal Nazarewicz
This commit changes various functions that change pages and
pageblocks migrate type between MIGRATE_ISOLATE and
MIGRATE_MOVABLE in such a way as to allow to work with
MIGRATE_CMA migrate type.
Signed-off-by: Michal Nazarewicz
Signed-off-by: Kyungmin Park
Signed-off-by:
This patch adds support for CMA to dma-mapping subsystem for ARM
architecture. CMA area can be defined individually for each device in
the system. This is up to the board startup code to create CMA area and
assign it to the devices.
Buffer alignment is derived from the buffer size, but for only fo
From: Michal Nazarewicz
This commit adds the alloc_contig_range() function which tries
to allecate given range of pages. It tries to migrate all
already allocated pages that fall in the range thus freeing them.
Once all pages in the range are freed they are removed from the
buddy system thus all
The Contiguous Memory Allocator is a set of functions that lets
one initialise a region of memory which then can be used to perform
allocations of contiguous memory chunks from.
CMA allows for creation of separate contexts. Kernel is allowed to
allocate movable pages within CMA's managed memory so
Hello everyone,
Like I've promised during the Memory Management summit at Linaro Meeting
in Budapest I continued the development of the CMA. The goal is to
integrate it as tight as possible with other kernel subsystems (like
memory management and dma-mapping) and finally merge to mainline.
This v
From: KAMEZAWA Hiroyuki
Memory hotplug is a logic for making pages unused in the specified
range of pfn. So, some of core logics can be used for other purpose
as allocating a very large contigous memory block.
This patch moves some functions from mm/memory_hotplug.c to
mm/page_isolation.c. This
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/Kconfig |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/Kconfig b/drivers/media/Kconfig
index dc61895..c2ee0aa 100644
--- a/drivers/media/Kconfig
+++ b/drivers/media/Kconfig
@@ -87,7 +87,7 @@ config DVB
I am curious about one thing
Why do we need this allocator. Why not use allocate_resource and friends.
The kernel generic resource handler already handles object alignment and
subranges. It just seems to be a surplus allocator that could perhaps be
mostly removed by using the kernel resource alloc
Hans, Mauro:
I have tried to compile the sources at git://linuxtv.org/media_build.git,
using build.sh
At
cx18-driver.h:659:
struct workqueue_struct *out_work_queue;
char out_workq_name[12]; /* "cx18-NN-out" */
struct workqueue_struct *out_work_queue;
char out_workq_name[12]; /*
Hello,
On Wednesday, June 08, 2011 10:48 PM Uwe Kleine-König wrote:
> I'm still debugging my new video overlay device driver. The current
> problem is again when playing back a second video.
>
> After streamoff is called at the end of the first video, I disable the
> overlay and call vb2_buffer_
queued_count variable was left untouched during the queue reinitialization
in __vb2_queue_cancel, what might lead to mismatch between the real number
of queued buffers and queued_count variable.
Reported-by: Uwe Kleine-König
Signed-off-by: Marek Szyprowski
CC: Pawel Osciak
---
drivers/media/vi
Hi,
On 06/10/2011 10:42 AM, Felipe Balbi wrote:
Hi,
On Fri, Jun 10, 2011 at 10:36:47AM +0200, Hans de Goede wrote:
On Fri, Jun 10, 2011 at 09:55:13AM +0200, Hans de Goede wrote:
So what do we need to make this situation better:
1) A usb_driver callback alternative to the disconnect callba
Hello,
On Friday, June 10, 2011 1:25 PM Alan Cox wrote:
> I am curious about one thing
>
> Why do we need this allocator. Why not use allocate_resource and friends.
> The kernel generic resource handler already handles object alignment and
> subranges. It just seems to be a surplus allocator tha
Hello.
On Mon, 2011-05-23 at 13:06 +0200, ext Hans Verkuil wrote:
> Hi Mauro,
>
> Here are a few fixes: the first fixes a bug in the wl12xx drivers (I hope
> Matti's
> email is still correct). The second fixes a few DocBook validation errors, and
I'm still here... And it's a nice surprise that
Hi,
On Fri, Jun 10, 2011 at 02:19:20PM +0200, Hans de Goede wrote:
> So what do we need to make this situation better:
> 1) A usb_driver callback alternative to the disconnect callback,
> I propose to call this soft_disconnect. This serves 2 purposes
> a) It will allow the
Jan Hoogenraad wrote:
>Hans, Mauro:
>
>I have tried to compile the sources at
>git://linuxtv.org/media_build.git,
>using build.sh
>
>At
>cx18-driver.h:659:
> struct workqueue_struct *out_work_queue;
> char out_workq_name[12]; /* "cx18-NN-out" */
>
> struct workqueue_struct *out_work_q
les there. Documentation build is stopping earlier.
I'm using the -next tree for 20110610:
$ make defconfig
$ make CONFIG_BUILD_DOCSRC=y -j 16 Documentation/
Documentation/networking/timestamping/timestamping.c:45:30: error:
linux/net_tstamp.h: No such file or directory
Documentation/networking/ti
> I plan to replace it with lib/bitmap.c bitmap_* based allocator (similar like
> it it is used by dma_declare_coherent_memory() and friends in
> drivers/base/dma-coherent.c). We need something really simple for CMA area
> management.
>
> IMHO allocate_resource and friends a bit too heavy here, b
On Fri, Jun 10, 2011 at 8:34 AM, Andy Walls wrote:
> What are the error messages?
>
> Tejun Heo made quite a number of workqueue changes, and the cx18 driver got
> dragged forward with them. So did ivtv for that matter.
>
> Just disable the cx18 driver if you don't need it for an older kernel.
>
On Thu, Jun 9, 2011 at 9:07 AM, Andreas Oberritter wrote:
> ... implemented in *kernel* drivers for several generations of the dreambox.
Well, let's see the source code to the drivers in question, and from
there we can make some decisions on how to best proceed.
Devin
--
Devin J. Heitmueller -
Andy:
Something along the line of id already defined.
I just corrected the code by removing the duplicate lines that are in
the sources of the tar.
The other 3 files have a bad escape sequence in a line saying that this
is the backports. One backslash not removed in a script, I guess.
Devin
On 10.06.2011 15:18, Devin Heitmueller wrote:
On Thu, Jun 9, 2011 at 9:07 AM, Andreas Oberritter wrote:
... implemented in *kernel* drivers for several generations of the dreambox.
Well, let's see the source code to the drivers in question, and from
there we can make some decisions on how to
Sorry; too fast a reaction; I did not realize that the build script
creates a version per kernel, and that my messages thus become hard to
trace.
The cx18 doubles were clear. The one in the code file may be caused by
v2.6.37_dont_use_alloc_ordered_workqueue.patch
but I don't see the problem in
To follow are two patches for the timberdale radio driver.
The first just simplifies the platform data.
The second uses the platform data to find a tuner and DSP on
a provided I2C bus.
--Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message t
On Fri, 10 Jun 2011, Hans de Goede wrote:
> Hi all,
>
> The current API for managing kernel -> userspace is a bit
> rough around the edges, so I would like to discuss extending
> the API.
>
> First of all an example use case scenarios where the current API
> falls short.
>
> 1) Redirection of U
This patch uses the platform data and finds a tuner and DSP. This is
done when the user calls open. Not during probe, to allow shorter bootup
time of the system.
This piece of code was actually missing earlier, many of the functions
were not useful without DSP and tuner.
Signed-off-by: Richard Röj
This patch simplifies the platform data slightly, by removing
unused elements.
Signed-off-by: Richard Röjfors
---
diff --git a/drivers/mfd/timberdale.c b/drivers/mfd/timberdale.c
index 69272e4..696879e 100644
--- a/drivers/mfd/timberdale.c
+++ b/drivers/mfd/timberdale.c
@@ -287,12 +287,8 @@ stati
Em 10-06-2011 11:48, Alan Stern escreveu:
> On Fri, 10 Jun 2011, Hans de Goede wrote:
>
>
> As Felipe has mentioned, this sounds like the sort of problem that
> can better be solved in userspace. A dual-mode device like the one
> you describe really is either a still-cam or a webcam, never bot
;>> kernel code build
>>> when CONFIG_BUILD_DOCSRC=y.
>>>
>>> Sorry, I should have mentioned this earlier.
>>
>> I couldn't reach any troubles there. Documentation build is stopping earlier.
>> I'm using the -next tree for 20110610:
>&g
On Fri, 10 Jun 2011, Mauro Carvalho Chehab wrote:
> Em 10-06-2011 11:48, Alan Stern escreveu:
> > On Fri, 10 Jun 2011, Hans de Goede wrote:
> >
> >
> > As Felipe has mentioned, this sounds like the sort of problem that
> > can better be solved in userspace. A dual-mode device like the one
> >
Em 10-06-2011 11:14, Jan Hoogenraad escreveu:
> Sorry; too fast a reaction; I did not realize that the build script creates a
> version per kernel, and that my messages thus become hard to trace.
>
> The cx18 doubles were clear. The one in the code file may be caused by
> v2.6.37_dont_use_alloc_o
I see these errors not during "make htmldocs" but during a
>>>> kernel code build
>>>> when CONFIG_BUILD_DOCSRC=y.
>>>>
>>>> Sorry, I should have mentioned this earlier.
>>>
>>> I couldn't reach any troubles there. Document
Em 10-06-2011 12:34, Mauro Carvalho Chehab escreveu:
> Em 10-06-2011 11:14, Jan Hoogenraad escreveu:
>> Sorry; too fast a reaction; I did not realize that the build script creates
>> a version per kernel, and that my messages thus become hard to trace.
>>
>> The cx18 doubles were clear. The one in
On Friday 10 June 2011, Marek Szyprowski wrote:
>The Contiguous Memory Allocator is a set of functions that lets
>one initialise a region of memory which then can be used to perform
>allocations of contiguous memory chunks from.
>
>CMA allows for creation of separate contexts. Kernel is allowed to
On Fri, Jun 10, 2011 at 01:50:37PM +0200, Marek Szyprowski wrote:
> Hello,
>
> On Wednesday, June 08, 2011 10:48 PM Uwe Kleine-König wrote:
>
> > I'm still debugging my new video overlay device driver. The current
> > problem is again when playing back a second video.
> >
> > After streamoff is
On Fri, Jun 10, 2011 at 02:04:38PM +0200, Marek Szyprowski wrote:
> queued_count variable was left untouched during the queue reinitialization
> in __vb2_queue_cancel, what might lead to mismatch between the real number
> of queued buffers and queued_count variable.
>
> Reported-by: Uwe Kleine-Kön
On Fri, 10 Jun 2011 14:52:17 +0200, Alan Cox
wrote:
I plan to replace it with lib/bitmap.c bitmap_* based allocator
(similar like
it it is used by dma_declare_coherent_memory() and friends in
drivers/base/dma-coherent.c). We need something really simple for CMA
area
management.
IMHO all
Hi,
On Fri, Jun 10, 2011 at 01:16:47PM -0500, Theodore Kilgore wrote:
> As I have been involved in writing the drivers (both the kernel and the
> libgphoto2 drivers) for many of the affected cameras, perhaps I should
> expand on this problem. There are lots of responses to this original
> messa
Hello,
The following change set is a S5P/EXYNOS4 FIMC (camera host interface
and video post-processor) driver conversion to the control framework
and Media Controller API. The first and last patch add Runtime PM support
in the mem-to-mem and capture driver respectively.
The s5p-fimc driver suppor
Only the FIMC entity memory-to-memory operation is fully covered,
for the camera capture suspend/resume only stubs are provided.
It's all what is needed to enable the driver on EXYNOS4 series with
power domain driver enabled. Camera capture pipeline suspend/resume
is covered by a separate patch.
S
Camera sensors at FIMC input are no longer selected with S_INPUT ioctl.
They will be attached to required FIMC entity through pipeline
re-configuration at the media device level.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 4
Add intialization of the media entities for video capture
and mem-to-mem video nodes.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 28 --
drivers/media/video/s5p-fimc/fimc-core.c| 27
Do not register video nodes during FIMC device probe. Also make
fimc_register_m2m_device() public for use by the media device driver.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-core.c | 18 +-
drivers/media/video/s5p-fi
Create a helper function for (re)starting streaming PM resume calls.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 78 ---
drivers/media/video/s5p-fimc/fimc-core.c|4 +-
drivers/media/video/s5p-
Add the link_setup handler for the camera capture video node.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 32 +++
drivers/media/video/s5p-fimc/fimc-core.h|2 +
2 files changed, 34 insertions(+
The external sclk_cam clocks will be handled at the media device
driver level.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-core.c | 12 ++--
drivers/media/video/s5p-fimc/fimc-core.h |3 +--
2 files changed, 3 insertions(+),
Currently there is a v4l2_device instance being registered per each
(capture and memory-to-memory) video node created per FIMC H/W instance.
This patch is a prerequisite for using the top level v4l2_device
instantiated by the media device driver.
To retain current debug trace semantic (so it's poss
Create separate VIDIOC_ENUM_FMT ioctl handlers for video capture
and mem-to-mem video node. This is needed as some formats are
valid only for the video capture and some only for the mem-to-mem
video node. Create single function for pixel format lookup out of
find_mbus_format() and find_format().
S
This is a prerequisite for the patch converting the driver to use
the control framework. As the capture driver does not use per file
handle contexts, two separate ioctl handlers are created for it
(vidioc_try_fmt_mplane, and vidioc_g_fmt_mplane) so there is no
handlers shared between the memory-to-
The fimc media device driver is hooked onto "s5p-fimc-md" platform device.
Such a platform device need to be adde in a board initialization code
and then camera sensors need to be specified as it's platform data.
The "s5p-fimc_md" device is a top level entity for all FIMC, mipi-csis
and sensor devi
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 47 +++
drivers/media/video/s5p-fimc/fimc-core.h|2 +
drivers/media/video/s5p-fimc/fimc-mdevice.c |1 +
include/media/s5p_fimc.h
Add support for transparent DMA transfer of JPEG data with MIPI-CSI2
USER1 format. In JPEG mode the color effect, scaling and cropping
is not supported. Same applies to image rotation and flip thus those
controls are marked as inactive when V4L2_PIX_FMT_JPEG pixelformat
is selected.
Signed-off-by:
The sensor subdevs need to be shared between all available FIMC instances.
Remove their registration from FIMC capture driver so they can then be
registered to the media device driver.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c
Also correct and improve *_queue_add/pop functions description.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c |6 ++--
drivers/media/video/s5p-fimc/fimc-core.c|6 ++--
drivers/media/video/s5p-fimc/fimc-core.h| 38
Add format negotiation routine for sensor subdevs not exposing
a device node.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 180 +--
drivers/media/video/s5p-fimc/fimc-core.c| 26 +++--
drivers/medi
This subdev interface exposes the internal scaler and color converter
functionality to user space. Resolution and media bus format can now
be configured explicitly by applications. Camera frame composition
onto the output buffer can be confgured through set/get_crop at FIMC.{n}
source pad. Addition
Add support for whole pipeline suspend/resume. Sensors must support
suspend/resume through s_power subdev operation.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/video/s5p-fimc/fimc-capture.c | 87 +++
drivers/media/video/s5p-fimc/fi
The FIMC entity supports rotation, horizontal and vertical flip
in camera capture and memory-to-memory operation mode.
Due to atomic contexts used in mem-to-mem driver the control
values need to be cached in drivers internal data structure.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmi
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 Jun 10 19:00:40 CEST 2011
git hash:75125b9d44456e0cf2d1fbb72ae33c13415299d1
gcc version: i686-linux-gcc (GCC) 4.5
On Fri, 10 Jun 2011, Hans de Goede wrote:
> Hi all,
>
> The current API for managing kernel -> userspace is a bit
> rough around the edges, so I would like to discuss extending
> the API.
[...]
> 2) So called dual mode cameras are (cheap) stillcams often even
> without an lcdscreen viewfinder
On Thu, Jun 09, 2011 at 08:18:05PM -0700, Greg KH wrote:
> On Thu, Jun 09, 2011 at 05:21:03PM -0700, Sarah Sharp wrote:
> > Topic 1
> > ---
> >
> > The KVM folks suggested that it would be good to get USB and
> > virtualization developers together to talk about how to virtualize the
> > xHCI h
On Fri, Jun 10, 2011 at 12:48:15PM -0700, Sarah Sharp wrote:
> On Thu, Jun 09, 2011 at 08:18:05PM -0700, Greg KH wrote:
> > On Thu, Jun 09, 2011 at 05:21:03PM -0700, Sarah Sharp wrote:
> > > Topic 1
> > > ---
> > >
> > > The KVM folks suggested that it would be good to get USB and
> > > virtua
On Fri, 10 Jun 2011, Felipe Balbi wrote:
> I don't see any problems in this situation. If, for that particular
> product, webcam and still image functionality are mutually exclusive,
> then that's how the product (and their drivers) have to work.
>
> If the linux community decided to put webcam f
Hi,
On Fri, Jun 10, 2011 at 05:18:39PM -0400, Alan Stern wrote:
> > > 2. Until recently in the history of Linux, there was an irreconcilable
> > > conflict. If a kernel driver for the video streaming mode was present and
> > > installed, it was not possible to use the camera in stillcam mode at
Hello,
I just wanted to let you know the Orion StarShoot Solar System Color
Imaging Camera works with the latest v4l git tree
(http://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git).
It needs the "case 0xb1:" for the OV9600 that's not in Linus's tree
yet. I didn't know what sensor
It's not an unknown sensor, please ignore that subject line. That was
before I tested it with the latest v4l tree.
2011/6/10 Paul Thomas :
> Hello,
>
> I just wanted to let you know the Orion StarShoot Solar System Color
> Imaging Camera works with the latest v4l git tree
> (http://git.kernel.org/
On Fri, 10 Jun 2011, Felipe Balbi wrote:
> Hi,
>
> On Fri, Jun 10, 2011 at 01:16:47PM -0500, Theodore Kilgore wrote:
> > As I have been involved in writing the drivers (both the kernel and the
> > libgphoto2 drivers) for many of the affected cameras, perhaps I should
> > expand on this proble
On Fri, 10 Jun 2011, Alan Stern wrote:
> On Fri, 10 Jun 2011, Felipe Balbi wrote:
>
> > I don't see any problems in this situation. If, for that particular
> > product, webcam and still image functionality are mutually exclusive,
> > then that's how the product (and their drivers) have to work.
I think you've missed this line at the end of ttpci-eeprom.c :
EXPORT_SYMBOL(ttpci_eeprom_decode_mac);
--
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://vger.kernel.org/majordomo-info.htm
On Sat, Jun 11, 2011 at 6:43 AM, Theodore Kilgore
wrote:
> I do not believe that we have found the optimal solution, yet. The ideal
> thing would be some kind of hack which allows the kernel to be used when
> it is needed, and when it is not needed it does not interfere.
Just wondering if you can
On Sat, 11 Jun 2011, Xiaofan Chen wrote:
> On Sat, Jun 11, 2011 at 6:43 AM, Theodore Kilgore
> wrote:
> > I do not believe that we have found the optimal solution, yet. The ideal
> > thing would be some kind of hack which allows the kernel to be used when
> > it is needed, and when it is not ne
Hi Mauro,
On Fri, 10 Jun 2011 12:19:12 -0300 Mauro Carvalho Chehab
wrote:
>
> PS.: A full build against next is broken:
> $ make -j 27
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CALLscripts/checksyscalls.sh
> CHK include/generated/compile.h
> C
91 matches
Mail list logo