Hi!
I'm trying to get an Hauppauge Live Usb 2 video grabber to run on on Omap4
(Gumstix Duovero). I'm using Sakomans omap-3.6 head kernel sources from
http://git.sakoman.com/git/gitweb.cgi?p=linux.git;a=summary . The hardware is
successfully detected on the USB host port, the driver loads perfe
Modified the G2D driver (which initially supported only H/W Rev.3)
to support H/W Rev.4.1 present on Exynos4x12 and Exynos52x0 SOCs.
-- Set the SRC and DST type to 'memory' instead of using reset values.
-- FIMG2D v4.1 H/W uses different logic for stretching(scaling).
-- Use CACHECTL_REG only with
On Thu, Jan 17, 2013 at 3:31 AM, Mauro Carvalho Chehab
wrote:
> Em Wed, 16 Jan 2013 19:29:28 +
> Simon Farnsworth escreveu:
>
>> On Wednesday 16 January 2013 23:56:48 Manu Abraham wrote:
>> > On Wed, Jan 16, 2013 at 10:51 PM, Mauro Carvalho Chehab
>>
>> > >
>> > > It is a common sense that t
On Thu, Jan 17, 2013 at 3:41 AM, Mauro Carvalho Chehab
wrote:
> Em Thu, 17 Jan 2013 03:07:21 +0530
> Manu Abraham escreveu:
>
>> With ISDB-T, with the 3 layers, you have BER/UNC for each of the layers,
>> though
>> the rate difference could be very little.
>
> Where? There's no way to report per
These variables are implicitly initialized by passing them to
xc_get_version(). However, initializing them to 0 explicitly will avoid
compile warnings.
Signed-off-by: Simon Que
---
drivers/media/tuners/xc4000.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/m
Is there anything else I can provide to help with this?
On 12/01/13 01:48, Greg Bell wrote:
Hi Guys,
I'm trying to get my DVICO DVB-T Dual Express2 card working on an
Ubuntu 12.10 system with the 3.5.0 kernel.
lspci tells me it's a "Conexant Systems, Inc. CX23885 PCI Video and
Audio Decod
Em Thu, 17 Jan 2013 03:07:21 +0530
Manu Abraham escreveu:
> With ISDB-T, with the 3 layers, you have BER/UNC for each of the layers,
> though
> the rate difference could be very little.
Where? There's no way to report per-layer report with DVBv3.
And no, the difference is not very little:
$ d
Em Wed, 16 Jan 2013 19:29:28 +
Simon Farnsworth escreveu:
> On Wednesday 16 January 2013 23:56:48 Manu Abraham wrote:
> > On Wed, Jan 16, 2013 at 10:51 PM, Mauro Carvalho Chehab
>
> > >
> > > It is a common sense that the existing API is broken. If my proposal
> > > requires adjustments, ple
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:Wed Jan 16 19:00:17 CET 2013
git hash:3151d14aa6e983aa36d51a80d0477859f9ba12af
gcc version: i686-linux-gcc (GCC
On Thu, Jan 17, 2013 at 12:52 AM, Mauro Carvalho Chehab
wrote:
> Em Wed, 16 Jan 2013 23:56:48 +0530
> Manu Abraham escreveu:
>
>> Consider this simple situation:
>> Your new API is using get_frontend and is polling the hardware, Now an
>> existing application is also doing monitoring of the stati
On Thu, Jan 17, 2013 at 12:59 AM, Simon Farnsworth
wrote:
> On Wednesday 16 January 2013 23:56:48 Manu Abraham wrote:
>> On Wed, Jan 16, 2013 at 10:51 PM, Mauro Carvalho Chehab
>
>> >
>> > It is a common sense that the existing API is broken. If my proposal
>> > requires adjustments, please comme
On Wednesday 16 January 2013 23:56:48 Manu Abraham wrote:
> On Wed, Jan 16, 2013 at 10:51 PM, Mauro Carvalho Chehab
> >
> > It is a common sense that the existing API is broken. If my proposal
> > requires adjustments, please comment on each specific patchset, instead
> > of filling this thread of
Em Wed, 16 Jan 2013 23:56:48 +0530
Manu Abraham escreveu:
> Consider this simple situation:
> Your new API is using get_frontend and is polling the hardware, Now an
> existing application is also doing monitoring of the statistics. So, now all
> the decision box calculations are screwed.
-EREADT
Al 16/01/2013 5:26, En/na Manu Abraham ha escrit:
The simplest and easiest way to achieve commonality between the various
demodulators is to use the existing API and scale whatever documented
demodulators to that scacle, to best possible way, rather than adding more
ambiguity and breakage.
Not
On Wed, Jan 16, 2013 at 10:51 PM, Mauro Carvalho Chehab
wrote:
>> If you have sufficient documentation, you can scale your demodulator
>> statistics
>> to fit in that window area. I had done something similarly with a MB86A16
>> demodulator. IIRC, some effort was done on the STV0900 and STV0903
Hi Volokh,
On Wed, Jan 16, 2013 at 10:42 AM, Volokh Konstantin wrote:
> On Wed, Jan 16, 2013 at 04:35:45PM +0300, Dan Carpenter wrote:
>> The problem is that the firmware was being unloaded on disconnect?
>>
> If no firmware was loaded (no exists,wrong or some error) then rmmod fails
> with OOPS
Em Wed, 16 Jan 2013 20:49:05 +0530
Manu Abraham escreveu:
> On Wed, Jan 16, 2013 at 7:26 PM, Mauro Carvalho Chehab
> wrote:
> > Em Wed, 16 Jan 2013 09:56:12 +0530
> > Manu Abraham escreveu:
> >
> >> On Wed, Jan 16, 2013 at 2:07 AM, Antti Palosaari wrote:
> >> > On 01/15/2013 07:12 PM, Mauro Ca
On 01/16/2013 05:15 PM, Radoslaw Moszczynski wrote:
With Ubuntu's 3.5 kernel, the DVB-C frontend is not registered at all --
only DVB-T/T2 is available.
I'll do some more testing with newer/older kernels over the next few days.
That is because of changed functionality, multi-frontend to
singl
On Wed, Jan 16, 2013 at 7:26 PM, Mauro Carvalho Chehab
wrote:
> Em Wed, 16 Jan 2013 09:56:12 +0530
> Manu Abraham escreveu:
>
>> On Wed, Jan 16, 2013 at 2:07 AM, Antti Palosaari wrote:
>> > On 01/15/2013 07:12 PM, Mauro Carvalho Chehab wrote:
>> >>
>> >> Em Tue, 15 Jan 2013 17:26:17 +0200
>> >>
With Ubuntu's 3.5 kernel, the DVB-C frontend is not registered at all --
only DVB-T/T2 is available.
I'll do some more testing with newer/older kernels over the next few days.
Regards-
-Radek
-Original Message-
From: Antti Palosaari [mailto:cr...@iki.fi]
Sent: Wednesday, January 16, 2
On 01/16/2013 03:58 PM, Radoslaw Moszczynski wrote:
Hi,
I'm not sure if this has been already reported, but I was playing around
with Nanostick 290e today and I encountered some weird behavior with the
DVB-C frontend.
The DVB-C frontend only seems to work once after plugging in the device.
Duri
On Wed, Jan 16, 2013 at 06:00:13PM +0400, Volokh Konstantin wrote:
> On Wed, Jan 16, 2013 at 04:36:08PM +0300, Dan Carpenter wrote:
> > You've added the writes for GO7007_BOARDID_ADLINK_MPG24 but removed
> > them for GO7007_BOARDID_XMEN and GO7007_BOARDID_XMEN_III. Won't
> > that break those board
Hi Sachin,
I tested your patch on Exynos 4210 and it works. Ack on my side.
Best wishes,
--
Kamil Debski
Linux Platform Group
Samsung Poland R&D Center
> From: Sachin Kamat [mailto:sachin.ka...@linaro.org]
> Sent: Wednesday, January 16, 2013 11:24 AM
> To: Sylwester Nawrocki
> Cc: linux-media@v
On Wed, Jan 16, 2013 at 04:36:08PM +0300, Dan Carpenter wrote:
> You've added the writes for GO7007_BOARDID_ADLINK_MPG24 but removed
> them for GO7007_BOARDID_XMEN and GO7007_BOARDID_XMEN_III. Won't
> that break those boards?
>
I don`t remove code for GO7007_BOARDID_XMEN and GO7007_BOARDID_XMEN_II
Hi,
I'm not sure if this has been already reported, but I was playing around
with Nanostick 290e today and I encountered some weird behavior with the
DVB-C frontend.
The DVB-C frontend only seems to work once after plugging in the device.
During subsequent uses, it fails to lock on to signal. How
Em Wed, 16 Jan 2013 09:56:12 +0530
Manu Abraham escreveu:
> On Wed, Jan 16, 2013 at 2:07 AM, Antti Palosaari wrote:
> > On 01/15/2013 07:12 PM, Mauro Carvalho Chehab wrote:
> >>
> >> Em Tue, 15 Jan 2013 17:26:17 +0200
> >> Antti Palosaari escreveu:
> >>
> >>> On 01/15/2013 04:49 PM, Antti Palos
On Wed, Jan 16, 2013 at 04:35:45PM +0300, Dan Carpenter wrote:
> The problem is that the firmware was being unloaded on disconnect?
>
> regards,
> dan carpenter
If no firmware was loaded (no exists,wrong or some error) then rmmod fails with
OOPS,
so need some protection stuff
>
--
To unsubscribe
Em Tue, 15 Jan 2013 22:37:40 +0200
Antti Palosaari escreveu:
> On 01/15/2013 07:12 PM, Mauro Carvalho Chehab wrote:
> > Em Tue, 15 Jan 2013 17:26:17 +0200
> > Antti Palosaari escreveu:
> >
> >> On 01/15/2013 04:49 PM, Antti Palosaari wrote:
> >>> I am a little bit lazy to read all those patches,
You've added the writes for GO7007_BOARDID_ADLINK_MPG24 but removed
them for GO7007_BOARDID_XMEN and GO7007_BOARDID_XMEN_III. Won't
that break those boards?
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vge
The problem is that the firmware was being unloaded on disconnect?
regards,
dan carpenter
--
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.html
On Wed, Jan 16, 2013 at 05:00:48PM +0400, Volokh Konstantin wrote:
> Signed-off-by: Volokh Konstantin
Acked-by: Dan Carpenter
--
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.kern
Signed-off-by: Volokh Konstantin
---
drivers/staging/media/go7007/go7007-driver.c |2 +-
drivers/staging/media/go7007/go7007-v4l2.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/go7007/go7007-driver.c
b/drivers/staging/media/go7007/go7007-d
Signed-off-by: Volokh Konstantin
---
drivers/staging/media/go7007/go7007-v4l2.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/media/go7007/go7007-v4l2.c
b/drivers/staging/media/go7007/go7007-v4l2.c
index a69250f..2330861 100644
--- a/drivers/staging/me
Signed-off-by: Volokh Konstantin
---
drivers/staging/media/go7007/go7007-driver.c |5 +
drivers/staging/media/go7007/go7007-usb.c|3 ---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/media/go7007/go7007-driver.c
b/drivers/staging/media/go7007/go70
Signed-off-by: Volokh Konstantin
---
drivers/staging/media/go7007/go7007-usb.c |2 +-
drivers/staging/media/go7007/go7007-v4l2.c |3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/go7007/go7007-usb.c
b/drivers/staging/media/go7007/go7007-usb.c
i
2013/1/16 Maarten Lankhorst :
> Op 16-01-13 07:28, Inki Dae schreef:
>> 2013/1/15 Maarten Lankhorst :
>>> This type of fence can be used with hardware synchronization for simple
>>> hardware that can block execution until the condition
>>> (dma_buf[offset] - value) >= 0 has been met.
>>>
>>> A soft
Op 16-01-13 07:28, Inki Dae schreef:
> 2013/1/15 Maarten Lankhorst :
>> This type of fence can be used with hardware synchronization for simple
>> hardware that can block execution until the condition
>> (dma_buf[offset] - value) >= 0 has been met.
>>
>> A software fallback still has to be provided
Hi Sylwester,
On 16 January 2013 15:43, Sylwester Nawrocki wrote:
> Hi Sachin,
>
> I have just one small comment...
>
> On 01/07/2013 07:44 AM, Sachin Kamat wrote:
>> +static void *g2d_get_drv_data(struct platform_device *pdev)
>> +{
>> + struct g2d_variant *driver_data = NULL;
>> +
>> +
Hi Sachin,
I have just one small comment...
On 01/07/2013 07:44 AM, Sachin Kamat wrote:
> +static void *g2d_get_drv_data(struct platform_device *pdev)
> +{
> + struct g2d_variant *driver_data = NULL;
> +
> + driver_data = (struct g2d_variant *)
> + platform_get_device_id(pdev)
On Tue 15 January 2013 18:06:57 Frank Schäfer wrote:
> Am 14.01.2013 10:20, schrieb Hans Verkuil:
> > On Sun January 13 2013 13:50:50 Frank Schäfer wrote:
> >> Signed-off-by: Frank Schäfer
> >> ---
> >> drivers/media/usb/em28xx/em28xx-video.c |8
> >> 1 Datei geändert, 8 Zeilen hinzu
40 matches
Mail list logo
