Hi Laurent,
Sorry for the late reply. I'll post a patch of your revised version,
but I don't see the documentation anywhere in your git repositories. I
guess I'll download the file (preserving directory structure), update
it, and send you a diff -run. If this is not how it is done, please
let me k
Hi,
the chip CX23103 that is used in various devices sold e.g. in germany works
with the cx231xx stock driver.
The author of that driver is not reachable via the email adress stated in the
source file: srinivasa.de...@conexant.com
[ host cnxtsmtp1.conexant.com [198.62.9.252]: 550 5.1.1
: Reci
On 06/23/2013 10:53 PM, Sylwester Nawrocki wrote:
@@ -558,7 +566,23 @@ EXPORT_SYMBOL(v4l2_ctrl_get_menu);
*/
const s64 const *v4l2_ctrl_get_int_menu(u32 id, u32 *len)
{
[...]
Then this would became:
return __v4l2_qmenu_int_len(qmenu_int_vpx_num_partitions, &len);
erratum:
return __v4l2_qm
Hi Arun,
On 06/18/2013 02:56 PM, Arun Kumar K wrote:
This patch adds new V4L controls for VP8 encoding.
Signed-off-by: Arun Kumar K
Signed-off-by: Kiran AVND
I think your signed-off-by should be last one, since you're submitting
the patch.
---
Documentation/DocBook/media/v4l/controls.xml
Hi Arun,
On 06/18/2013 02:56 PM, Arun Kumar K wrote:
@@ -806,6 +820,7 @@ const char *v4l2_ctrl_get_name(u32 id)
case V4L2_CID_FM_RX_CLASS: return "FM Radio Receiver
Controls";
case V4L2_CID_TUNE_DEEMPHASIS: return "De-Emphasis";
case V4L2_CID_RDS_RE
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Sun Jun 23 19:00:20 CEST 2013
git branch: test
git hash: ee17608d6aa04a86e253a9130d6c6d00892f132b
gcc versi
On Sun, Jun 23, 2013 at 7:31 PM, Lars-Peter Clausen wrote:
> client->driver->id_table will always point to the first entry in the device id
> table. So all devices will use the same init sequence. Use the id table entry
> that gets passed to the driver's probe() function to get the right init
> se
Hi Guennadi,
Thanks for the review.
On Sun, Jun 23, 2013 at 8:49 PM, Guennadi Liakhovetski
wrote:
> On Sat, 22 Jun 2013, Prabhakar Lad wrote:
>
>> From: "Lad, Prabhakar"
>>
>> Both synchronous and asynchronous tvp514x subdevice probing is supported by
>> this patch.
>>
>> Signed-off-by: Prabhak
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
> From: "Lad, Prabhakar"
>
> Both synchronous and asynchronous tvp514x subdevice probing is supported by
> this patch.
>
> Signed-off-by: Prabhakar Lad
> Cc: Guennadi Liakhovetski
> Cc: Laurent Pinchart
> Cc: Hans Verkuil
> Cc: Sakari Ailus
> Cc: M
client->driver->id_table will always point to the first entry in the device id
table. So all devices will use the same init sequence. Use the id table entry
that gets passed to the driver's probe() function to get the right init
sequence.
Signed-off-by: Lars-Peter Clausen
---
Changes since v1:
On Sun, 23 Jun 2013, Guennadi Liakhovetski wrote:
> On Sat, 22 Jun 2013, Prabhakar Lad wrote:
>
> > From: "Lad, Prabhakar"
> >
> > Both synchronous and asynchronous adv7343 subdevice probing is supported by
> > this patch.
> >
> > Signed-off-by: Lad, Prabhakar
> > Cc: Guennadi Liakhovetski
>
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
> From: "Lad, Prabhakar"
>
> Both synchronous and asynchronous adv7343 subdevice probing is supported by
> this patch.
>
> Signed-off-by: Lad, Prabhakar
> Cc: Guennadi Liakhovetski
> Cc: Laurent Pinchart
> Cc: Hans Verkuil
> Cc: Sakari Ailus
> Cc:
12 matches
Mail list logo