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: Thu Jan 9 04:00:24 CET 2014
git branch: test
git hash: dad4c41827c71a84c8455e19431278e8c1edf118
gcc versio
This patch adds the Makefile and memory to memory (m2m) interface
functionality for the SCALER driver.
[arun...@samsung.com: fix compilation issues]
Signed-off-by: Shaik Ameer Basha
Signed-off-by: Arun Kumar K
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/Kconfig
This patch adds support for SCALER device which is a
new device for scaling, blending, color fill and color space
conversion on EXYNOS5410/5420 SoCs.
This device supports the following as key features.
input image format
- YCbCr420 2P(UV/VU), 3P
- YCbCr422 1P(YUYV/UYVY/YVYU),
This patch adds the DT binding documentation for the
Exynos5420/5410 based SCALER device driver.
Signed-off-by: Shaik Ameer Basha
Reviewed-by: Sylwester Nawrocki
---
.../devicetree/bindings/media/exynos5-scaler.txt | 22
1 file changed, 22 insertions(+)
create mode 100
This patch adds the core functionality for the SCALER driver.
Signed-off-by: Shaik Ameer Basha
Reviewed-by: Sylwester Nawrocki
---
drivers/media/platform/exynos-scaler/scaler.c | 1231 +
drivers/media/platform/exynos-scaler/scaler.h | 376
2 files changed, 1607
This patch adds support for SCALER device which is a new device
for scaling, blending, color fill and color space conversion
on EXYNOS5410 and EXYNOS5420 SoCs.
This device supports the followings as key feature.
input image format
- YCbCr420 2P(UV/VU), 3P
- YCbCr422 1P(YUYV/UY
Hello,
I sent the following message to the linux-usb mailing list and they
suggested I try here.
I'm trying to get a "Dazzle Video Capture USB V1.0" video capture card
working on a Linux device but it doesn't look like the chip set is
supported yet. I believe this card is the next version of
- implement the service location descriptor (0xa1)
- small cleanups
Signed-off-by: André Roth
---
lib/include/descriptors.h| 4 +-
lib/include/descriptors/desc_service_location.h | 68
lib/libdvbv5/descriptors/desc_service_location.c | 79 ++
Unfortunately the section ids are not granted to be incremented by one.
This means the last section id is not necessarily equal to the total
number of sections. The only way to know if everything has been parsed, is
to stop when a repeating section id has been found.
The sections do not need to co
Sylwester, Devin,
Thank you.
On Wed, Jan 8, 2014 at 1:19 PM, Sylwester Nawrocki
wrote:
> On 01/08/2014 08:15 PM, m silverstri wrote:
>>
>> Thanks.
>>
>> I am studying android source code.
>> From here, it has code which open("/dev/video11", O_RDWR, 0) as
>> decoding device.
>>
>>
>> http://and
Luis, yes, here we're or more exactly you're again, because it's clear
now you have the exact same patterns - i told you already - one time
any excuse may fly, when it's a pattern it's a whole new story. so,
excuses like this one:
http://www.spinics.net/lists/linux-media/msg65889.html
and the poi
On 01/08/2014 08:15 PM, m silverstri wrote:
Thanks.
I am studying android source code.
From here, it has code which open("/dev/video11", O_RDWR, 0) as
decoding device.
http://androidxref.com/4.4.2_r1/xref/hardware/samsung_slsi/exynos5/libhwjpeg/ExynosJpegBase.cpp
What you're looking for mig
ATTN: Dear,
I am Dr. Musa Hamed Executive Director of the Bank of Africa
Plc B.O.A,Cotonou Benin Rep. I have a very lucrative Business proposal
worth of 21,500,000.00 USD.
An Iraqi named Hamadi Hashem a business man made a fixed deposit of
21,500,000.00 USD . Upon maturity several notices was sen
Hi,
On 01/01/2014 12:39 AM, m silverstri wrote:
Hi,
I am looking for an example which uses samsung jpeg v4l2 mem2mem driver.
For example the 'Exynos4 JPEG codec v4l2 driver' described here
http://lwn.net/Articles/468547
I am new to linux v4l2 driver. I am looking for example to pass an
input
On Wed, Jan 8, 2014 at 1:42 AM, CrazyCat wrote:
> Konstantin Dimitrov пишет:
>
>> so, i was waiting Manu to upstream his SAA716x driver code some day
>> and then submit the improvements i made to it. yet again you're trying
>> to take that from me and again, conveniently you included many people
>
Hi Tim,
On Wed, Jan 8, 2014 at 12:12 AM, Tim Mester wrote:
> Commit 2e68a75990011ccd looks interesting. It makes sense to me
> that if we are gating the clock, and it is possible that we are
> glitching the clock line, it could put the internal synchronous logic
> into a bad state. If that ha
On Wed, 8 Jan 2014, Mauro Carvalho Chehab wrote:
> Hi Hans/Takashi,
>
> I'm getting an weird behavior with em28xx, especially when the device
> is connected into an audio port.
>
> I'm using, on my tests, an em28xx HVR-950 device, using this tree:
>
> http://git.linuxtv.org/mchehab/experi
Greetings
I am a US Army officer currently on military
assignment in Iraq, I humbly ask of your assistance secure and invest
some money for me in your country. As a matter of fact, I have the sum
of US$5 Million which I would like you to help me to invest.
I will appreciate it if you can assis
Am 08.01.2014 12:55, schrieb Mauro Carvalho Chehab:
> Em Tue, 07 Jan 2014 18:28:45 +0100
> Frank Schäfer escreveu:
...
>
>> But we also get this when a slave device isn't present or doesn't
>> answer, which means it doesn't ACK the data.
>> So ETIMEDOUT is wrong.
> It is still a timeout: the devic
Thanks.
I am studying android source code.
>From here, it has code which open("/dev/video11", O_RDWR, 0) as
decoding device.
http://androidxref.com/4.4.2_r1/xref/hardware/samsung_slsi/exynos5/libhwjpeg/ExynosJpegBase.cpp
I want to find out which is the corresponding driver code for device
'/dev
Am 08.01.2014 15:10, schrieb Mauro Carvalho Chehab:
> Em Tue, 07 Jan 2014 18:03:50 +0100
> Frank Schäfer escreveu:
>
>> Am 05.01.2014 22:25, schrieb Mauro Carvalho Chehab:
>>> Em Sun, 05 Jan 2014 22:02:40 +0100
>>> Frank Schäfer escreveu:
>>>
Am 04.01.2014 11:55, schrieb Mauro Carvalho Cheha
On Wed, Jan 8, 2014 at 2:03 PM, m silverstri
wrote:
> Thanks. I don't have the a running hardware.
> If I can only search within the code space, how can I find out which
> driver is for '/dev/video11'?
>
> Is there a config file which I can look it up?
If you don't actually have the hardware plat
Thanks. I don't have the a running hardware.
If I can only search within the code space, how can I find out which
driver is for '/dev/video11'?
Is there a config file which I can look it up?
Thank you.
On Wed, Jan 8, 2014 at 10:56 AM, Devin Heitmueller
wrote:
> On Wed, Jan 8, 2014 at 1:50 PM, m
Hi Hans/Takashi,
I'm getting an weird behavior with em28xx, especially when the device
is connected into an audio port.
I'm using, on my tests, an em28xx HVR-950 device, using this tree:
http://git.linuxtv.org/mchehab/experimental.git/shortlog/refs/heads/em28xx-v4l2-v6
Where the alsa dri
On Wed, Jan 8, 2014 at 1:50 PM, m silverstri
wrote:
> In linux kernel, a device (e.g. codec) can register as a file (e.g.
> /dev/video11).
>
> How can I find out from the code which driver is registered as
> '/dev/video11'. i.e. what is the driver will be invoked when I
> open('/dev/video11', O_RD
In linux kernel, a device (e.g. codec) can register as a file (e.g.
/dev/video11).
How can I find out from the code which driver is registered as
'/dev/video11'. i.e. what is the driver will be invoked when I
open('/dev/video11', O_RDWR,0) in my user space code?
--
To unsubscribe from this list: s
Em Wed, 08 Jan 2014 15:05:12 -0200
Mauro Carvalho Chehab escreveu:
> Em Wed, 08 Jan 2014 14:31:28 -0200
> Mauro Carvalho Chehab escreveu:
>
> > Em Thu, 02 Jan 2014 14:07:22 -0800
> > Sarah Sharp escreveu:
> >
> > > On Sun, Dec 29, 2013 at 02:54:40AM -0200, Mauro Carvalho Chehab wrote:
> > > >
Em Wed, 08 Jan 2014 14:31:28 -0200
Mauro Carvalho Chehab escreveu:
> Em Thu, 02 Jan 2014 14:07:22 -0800
> Sarah Sharp escreveu:
>
> > On Sun, Dec 29, 2013 at 02:54:40AM -0200, Mauro Carvalho Chehab wrote:
> > > It seems that usb_unlink_urb() is causing troubles with xHCI: the
> > > endpoint sto
Em Thu, 02 Jan 2014 14:07:22 -0800
Sarah Sharp escreveu:
> On Sun, Dec 29, 2013 at 02:54:40AM -0200, Mauro Carvalho Chehab wrote:
> > It seems that usb_unlink_urb() is causing troubles with xHCI: the
> > endpoint stops streaming, but, after that, it doesn't start again,
> > and lots of debug mess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
于 2014年01月08日 22:42, Kamil Debski 写道:
> Hi Randy,
>
>> From: randy [mailto:lxr1...@hotmail.com] Sent: Friday, January
>> 03, 2014 4:17 PM
>>
>> I rewrite my program, it takes the order as below 1.request
>> buffer. 2.mmap input buffer with OUTPUT 3.o
Hi Alexey,
On 01/08/2014 03:51 PM, Alexey Klimov wrote:
> On Fri, Dec 13, 2013 at 4:26 PM, Hans Verkuil wrote:
>> This patch series adds the new radio-raremono driver for the USB
>> 'Thanko's Raremono' AM/FM/SW receiver.
>>
>> Since it (ab)uses the same USB IDs as the si470x SiLabs Reference
>> D
On Fri, Dec 13, 2013 at 4:26 PM, Hans Verkuil wrote:
> This patch series adds the new radio-raremono driver for the USB
> 'Thanko's Raremono' AM/FM/SW receiver.
>
> Since it (ab)uses the same USB IDs as the si470x SiLabs Reference
> Design I had to add additional checks to si470x to tell the two a
Hi Randy,
> From: randy [mailto:lxr1...@hotmail.com]
> Sent: Friday, January 03, 2014 4:17 PM
>
> I rewrite my program, it takes the order as below 1.request buffer.
> 2.mmap input buffer with OUTPUT
> 3.output buffer with CAPTURE.
> 4.filled input buffer with the first frame.
> 5.enqueue the fir
Em Tue, 07 Jan 2014 18:15:38 +0100
Frank Schäfer escreveu:
> Am 05.01.2014 21:57, schrieb Mauro Carvalho Chehab:
> > Em Sun, 05 Jan 2014 21:38:31 +0100
> > Frank Schäfer escreveu:
> >
> >> Am 04.01.2014 11:55, schrieb Mauro Carvalho Chehab:
> >>> In the lack of a better spec, let's assume the ti
Em Tue, 07 Jan 2014 18:00:07 +0100
Frank Schäfer escreveu:
> Am 05.01.2014 14:17, schrieb Mauro Carvalho Chehab:
> > Em Sun, 05 Jan 2014 12:29:11 +0100
> > Frank Schäfer escreveu:
> >
> >> Am 04.01.2014 11:55, schrieb Mauro Carvalho Chehab:
> >>> Better to first write the GPIOs of the input mux,
Em Wed, 08 Jan 2014 14:33:30 +0100
Andrzej Hajda escreveu:
> On 01/08/2014 01:21 PM, Mauro Carvalho Chehab wrote:
> > Em Wed, 8 Jan 2014 11:37:37 +0300
> > Dan Carpenter escreveu:
> >
> >> The other thing that concerned me with this was the sparse warning:
> >>
> >> drivers/media/i2c/s5k5baf.c:4
Em Tue, 07 Jan 2014 18:03:50 +0100
Frank Schäfer escreveu:
> Am 05.01.2014 22:25, schrieb Mauro Carvalho Chehab:
> > Em Sun, 05 Jan 2014 22:02:40 +0100
> > Frank Schäfer escreveu:
> >
> >> Am 04.01.2014 11:55, schrieb Mauro Carvalho Chehab:
> >>> From: Mauro Carvalho Chehab
> >> Is this line st
Hello All,
On 2014-01-03 16:51, Ricardo Ribalda Delgado wrote:
Hello Hans
What if we move the dma_map_sg and dma_unmap_sg to the vb2 interface,
and there do something like:
n_sg= dma_map_sg()
if (n_sg=-ENOMEM){
split_table() //Breaks down the sg_table into monopages sg
n_sg= dma_map_sg
On 01/08/2014 01:21 PM, Mauro Carvalho Chehab wrote:
> Em Wed, 8 Jan 2014 11:37:37 +0300
> Dan Carpenter escreveu:
>
>> The other thing that concerned me with this was the sparse warning:
>>
>> drivers/media/i2c/s5k5baf.c:481:26: error: bad constant expression
> Hmm...
> static void s5k5baf_
Hi folks,
with my Terratec H5 Stick, the remote control wasn't working, so I
started to dig around and found this thread:
http://www.spinics.net/lists/linux-media/msg48499.html
Basically, just adding the IR codes map of the Cinergy XS did the
trick there and in fact also worked for me. As far as
On Wed, Jan 08, 2014 at 12:58:35PM +0100, Andrzej Hajda wrote:
> On 01/08/2014 10:58 AM, Dan Carpenter wrote:
> > Hello Andrzej Hajda,
> >
> > The patch 7d459937dc09: "[media] Add driver for Samsung S5K5BAF
> > camera sensor" from Dec 5, 2013, leads to the following
> > static checker warning:
> >
On 01/08/2014 09:37 AM, Dan Carpenter wrote:
> The other thing that concerned me with this was the sparse warning:
>
> drivers/media/i2c/s5k5baf.c:481:26: error: bad constant expression
>
> It was hard to verify that this couldn't go over 512. I guess 512 is
> what we would consider an error in
Em Wed, 8 Jan 2014 11:37:37 +0300
Dan Carpenter escreveu:
> The other thing that concerned me with this was the sparse warning:
>
> drivers/media/i2c/s5k5baf.c:481:26: error: bad constant expression
Hmm...
static void s5k5baf_write_arr_seq(struct s5k5baf *state, u16 addr,
Em Wed, 08 Jan 2014 12:52:53 +0100
Hans Verkuil escreveu:
> On 01/08/2014 12:13 PM, Hans Verkuil wrote:
> > Hi Mauro,
> >
> > The daily build fails when building v4l-utils:
> >
> > apps: ERRORS
> > ../../lib/include/descriptors/vct.h:28:37: fatal error:
> > descriptors/atsc_header.h: No such f
On 01/08/2014 10:58 AM, Dan Carpenter wrote:
> Hello Andrzej Hajda,
>
> The patch 7d459937dc09: "[media] Add driver for Samsung S5K5BAF
> camera sensor" from Dec 5, 2013, leads to the following
> static checker warning:
>
> drivers/media/i2c/s5k5baf.c:1043 s5k5baf_set_power()
> warn:
Le 07/01/2014 11:12, Enrico a écrit :
On Mon, Jan 6, 2014 at 11:11 AM, Julien BERAUD wrote:
Le 03/01/2014 12:30, Enrico a écrit :
On Wed, Dec 18, 2013 at 11:09 AM, Enrico wrote:
On Tue, Dec 17, 2013 at 2:11 PM, Florian Vaussard
wrote:
So I converted the iommu to DT (patches just sent), us
Em Tue, 07 Jan 2014 18:28:45 +0100
Frank Schäfer escreveu:
> Am 06.01.2014 10:55, schrieb Mauro Carvalho Chehab:
> > Em Sun, 05 Jan 2014 21:40:38 +0100
> > Frank Schäfer escreveu:
> >
> >> Am 04.01.2014 11:55, schrieb Mauro Carvalho Chehab:
> >>> The proper error code for I2C errors are EREMOTEI
On 01/08/2014 12:13 PM, Hans Verkuil wrote:
> Hi Mauro,
>
> The daily build fails when building v4l-utils:
>
> apps: ERRORS
> ../../lib/include/descriptors/vct.h:28:37: fatal error:
> descriptors/atsc_header.h: No such file or directory
> make[3]: *** [libdvbv5_la-dvb-file.lo] Error 1
> make[2]:
Hi Mauro, Shaik,
I had consulted our local DT expert, Tomasz Figa, about this.
His interpretation is in line with my opinion that this is
a trivial DT binding. It uses only existing properties and does
not introduce new things.
If you insist on having an ack from a DT maintainer then I will
sen
The following changes since commit 6892f65b7b9e14fe29b6e4f0dc4f7ed3796a6e71:
exynos-scaler: Add DT bindings for SCALER driver (2013-12-24 10:37:23
+0100)
are available in the git repository at:
git://linuxtv.org/kdebski/media.git master
for you to fetch changes up to 0f6616ebb7a04219ad7aa84
Hi Andrzej,
On 8 January 2014 16:30, Andrzej Hajda wrote:
> On 01/06/2014 12:48 PM, Sachin Kamat wrote:
> Hi Sachin,
>
> Thanks for the fixes.
>
>> Gentle ping on this series :)
>
> Sorry for late reply, but it seems Mauro has merged them already.
No worries. Yes, Mauro has queued them for 3.14.
The Master Guide Table is used in ATSC. Implementation
according to specs A/65:2009
Signed-off-by: André Roth
---
lib/include/descriptors/mgt.h | 79 +++
lib/libdvbv5/Makefile.am | 3 +-
lib/libdvbv5/descriptors.c | 1 +
lib/libdvbv5/descriptors/mgt.c | 140 ++
ATSC has a different EIT table then DVB. This implements
the parser according to secifications defined in A/65:2009.
Signed-off-by: André Roth
---
lib/include/descriptors/atsc_eit.h | 90 +++
lib/libdvbv5/Makefile.am| 4 +-
lib/libdvbv5/descriptors.c |
The ATSC standard header is slightly different from the one used
in DVB. This implements the parser for it, and will be used by
the VCT table for example.
Signed-off-by: André Roth
---
lib/include/descriptors/atsc_header.h | 63 ++
lib/libdvbv5/descriptors/atsc_h
Hi Mauro,
The daily build fails when building v4l-utils:
apps: ERRORS
../../lib/include/descriptors/vct.h:28:37: fatal error:
descriptors/atsc_header.h: No such file or directory
make[3]: *** [libdvbv5_la-dvb-file.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Erro
> > +void atsc_table_eit_init(struct dvb_v5_fe_parms *parms, const uint8_t
> > *buf, ssize_t buflen, uint8_t *table, ssize_t *table_length)
> > +{
> > + const uint8_t *p = buf;
> > + struct atsc_table_eit *eit = (struct atsc_table_eit *) table;
> > + struct atsc_table_eit_event **head;
> >
On 01/06/2014 12:48 PM, Sachin Kamat wrote:
Hi Sachin,
Thanks for the fixes.
> Gentle ping on this series :)
Sorry for late reply, but it seems Mauro has merged them already.
Regards
Andrzej
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to m
Hi Dan,
On 8 January 2014 14:39, Dan Carpenter wrote:
> Hello Andrzej Hajda,
>
> This is a semi-automatic email about new static checker warnings.
>
> The patch 7d459937dc09: "[media] Add driver for Samsung S5K5BAF
> camera sensor" from Dec 5, 2013, leads to the following Smatch
> complaint:
>
>
Hello Andrzej Hajda,
The patch 7d459937dc09: "[media] Add driver for Samsung S5K5BAF
camera sensor" from Dec 5, 2013, leads to the following
static checker warning:
drivers/media/i2c/s5k5baf.c:1043 s5k5baf_set_power()
warn: add some parenthesis here?
drivers/media/i2c/s5k5baf.c
Hello,
On 2014-01-08 09:01, Ricardo Ribalda Delgado wrote:
This patch adds a test preventing streamon() if there is no buffer
ready.
Without this patch, a user could call streamon() before
preparing any buffer. This leads to a situation where if he calls
close() before calling streamoff() the d
Hello Andrzej Hajda,
This is a semi-automatic email about new static checker warnings.
The patch 7d459937dc09: "[media] Add driver for Samsung S5K5BAF
camera sensor" from Dec 5, 2013, leads to the following Smatch
complaint:
drivers/media/i2c/s5k5baf.c:554 s5k5baf_fw_get_seq()
warn: v
The other thing that concerned me with this was the sparse warning:
drivers/media/i2c/s5k5baf.c:481:26: error: bad constant expression
It was hard to verify that this couldn't go over 512. I guess 512 is
what we would consider an error in this context. This seems like it
could be determined by
This patch adds a test preventing streamon() if there is no buffer
ready.
Without this patch, a user could call streamon() before
preparing any buffer. This leads to a situation where if he calls
close() before calling streamoff() the device is kept streaming.
Signed-off-by: Ricardo Ribalda Delga
63 matches
Mail list logo
