Andrey Utkin writes:
>> Also, TW686x are (mini) PCIe while SOLO6110 (and earlier SOLO6010 which
>> produces MPEG4 part 2 instead of H.264) are (mini) PCI.
>
> solo6110 is PCI-E, not PCI.
No, it's not, both SOLO6010 and SOLO6110 are 32-bit PCI.
SOLO6110 Data Sheet
1.2.5. PCI/HOST Interface
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: Mon Jul 6 04:00:17 CEST 2015
git branch: test
git hash: 5bab86243d949cf021b0f104faafc18f5d20283c
gcc versi
Convert pxa_camera to dmaengine. This removes all DMA registers
manipulation in favor of the more generic dmaengine API.
The functional level should be the same as before. The biggest change is
in the videobuf_sg_splice() function, which splits a videobuf-dma into
several scatterlists for 3 planes
From: Robert Jarzmik
In preparation for dmaengine conversion, move the camera interrupt
handling into a tasklet. This won't change the global flow, as this
interrupt is only used to detect the end of frame and activate DMA fifos
handling.
Signed-off-by: Robert Jarzmik
---
drivers/media/platfor
From: Robert Jarzmik
Fix the error path where the video buffer wasn't allocated nor
mapped. In this case, in the driver free path don't try to unmap memory
which was not mapped in the first place.
Signed-off-by: Robert Jarzmik
---
drivers/media/platform/soc_camera/pxa_camera.c | 6 --
1 fi
From: Robert Jarzmik
This moves the dma irq handling functions up in the source file, so that
they are available before DMA preparation functions. It prepares the
conversion to DMA engine, where the descriptors are populated with these
functions as callbacks.
Signed-off-by: Robert Jarzmik
---
S
Hi Guennadi,
This is the next round.
Most of your comments are addressed or answered, the one big thing left apart is
the videobuf_sg_cut() implementation and complexity. If you have a better idea,
I'm all ears.
One thing that changed since v1 is that pxa_dma driver was accepted into
dmaengine t
On Fri, Jul 3, 2015 at 1:46 PM, Krzysztof Hałasa wrote:
> Also, TW686x are (mini) PCIe while SOLO6110 (and earlier SOLO6010 which
> produces MPEG4 part 2 instead of H.264) are (mini) PCI.
solo6110 is PCI-E, not PCI.
--
Bluecherry developer.
--
To unsubscribe from this list: send the line "unsub
Hi,
On Sat, 4 Jul 2015 13:07:17 +0200 (SST)
Peter Fassberg wrote:
> Hi all!
>
> I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
> environment.
>
> I have no problem getting DVB-T to work, but I can't tune to any
> DVB-T2 channels. I have tried with three different kernels:
Peter Fassberg wrote:
Peter Fassberg wrote:
I'm trying to get PCTV TripleStick 292e working in a
Raspberry Pi B+ environment.
I have no problem getting DVB-T to work, but I can't tune to
any DVB-T2 channels. I have tried with three different
kernels: 3.18.11, 3.18.16 and 4.0.6. Same prob
Peter Fassberg wrote:
Peter Fassberg wrote:
I'm trying to get PCTV TripleStick 292e working in a
Raspberry Pi B+ environment.
I have no problem getting DVB-T to work, but I can't tune to
any DVB-T2 channels. I have tried with three different
kernels: 3.18.11, 3.18.16 and 4.0.6. Same proble
Peter Fassberg wrote:
I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi
B+ environment.
I have no problem getting DVB-T to work, but I can't tune to any
DVB-T2 channels. I have tried with three different kernels:
3.18.11, 3.18.16 and 4.0.6. Same problem. I also cloned the
m
Peter Fassberg wrote:
I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi
B+ environment.
I have no problem getting DVB-T to work, but I can't tune to any
DVB-T2 channels. I have tried with three different kernels:
3.18.11, 3.18.16 and 4.0.6. Same problem. I also cloned the
med
I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
environment.
I have no problem getting DVB-T to work, but I can't tune to any
DVB-T2 channels. I have tried with three different kernels: 3.18.11,
3.18.16 and 4.0.6. Same problem. I also cloned the media_build
under 4.0.6 t
Peter Fassberg wrote:
Hi all!
I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
environment.
I have no problem getting DVB-T to work, but I can't tune to any
DVB-T2 channels. I have tried with three different kernels: 3.18.11,
3.18.16 and 4.0.6. Same problem. I also cloned
I do still plan to fix this, but I have no idea right now how this can
actually happen: if TOUCHSCREEN_SUR40 is enabled, then this will enable
VIDEOBUF2_DMA_SG, and that will select most of the other V4L2 modules in
turn - or am I missing something here?
Best, Florian1
On 04.07.2015 19:56, kbuild
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 Jul 5 04:00:18 CEST 2015
git branch: test
git hash: 5bab86243d949cf021b0f104faafc18f5d20283c
gcc versi
Hi Florian,
FYI, the error/warning still remains. You may either fix it or ask me to
silently ignore in future.
tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 14a6f1989dae9445d4532941bdd6bbad84f4c8da
commit: e831cd251fb91d6c25352d322743db0d17ea11dd [media
Hi all!
I'm trying to get PCTV TripleStick 292e working in a Raspberry Pi B+
environment.
I have no problem getting DVB-T to work, but I can't tune to any DVB-T2
channels. I have tried with three different kernels: 3.18.11, 3.18.16 and
4.0.6. Same problem. I also cloned the media_build unde
19 matches
Mail list logo
