On Tue, Dec 18, 2018 at 7:08 PM Brad Love wrote:
>
>
> On 18/12/2018 18.05, Brad Love wrote:
> > On 18/12/2018 17.46, Alex Deucher wrote:
> >> On Tue, Dec 18, 2018 at 7:45 AM Mauro Carvalho Chehab
> >> wrote:
> >>> Em Mon, 17 Dec 2018 21:05:11 -0500
075/Ryzen%207%201800X/lspci,
> +* 0x1451 is PCI ID for the IOMMU found on Ryzen
> +*/
> + { PCI_VENDOR_ID_AMD, 0x1451 },
Does this issue only happen with the IOMMU is enabled? Is it only for
p2p transfers? Until recently the DMA and PCI subsystems didn't
act
On Tue, Dec 18, 2018 at 7:45 AM Mauro Carvalho Chehab
wrote:
>
> Em Mon, 17 Dec 2018 21:05:11 -0500
> Alex Deucher escreveu:
>
> > On Sun, Dec 16, 2018 at 9:23 AM Mauro Carvalho Chehab
> > wrote:
> > >
> > > Em Sun, 16 Dec 2018 11:37:02 +0100
>
this setup running stable for a few days before
> > replying, that's why I am answering only now.
> >
> > But yes, as expected, with Mauro's hack, the driver has been stable for
> > me for about a week, with several
> > scheduled recordings in tvheadend, none of th
side.
>
It's not clear to me what the pci or platform quirk would do. The
workaround seems to be in the driver, not on the platform.
Alex
On Wed, Apr 25, 2018 at 2:41 AM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 02:24:36AM -0400, Alex Deucher wrote:
>> > It has a non-coherent transaction mode (which the chipset can opt to
>> > not implement and still flush), to make sure the AGP horror show
>>
o make almost
>>> everything incoherent.
>>
>> How do discrete GPUs manage to be incoherent when attached over PCIe?
>
> It has a non-coherent transaction mode (which the chipset can opt to
> not implement and still flush), to make sure the AGP horror show
> doesn'
make almost
>> everything incoherent.
>
> How do discrete GPUs manage to be incoherent when attached over PCIe?
They can do CPU cache snooped (coherent) or non-snooped (incoherent)
DMA. Also for things like APUs, they show up as a PCIe device, but
that actual GPU core is part of t
Sorry, didn't mean to drop the lists here. re-adding.
On Wed, Mar 28, 2018 at 4:05 PM, Alex Deucher wrote:
> On Wed, Mar 28, 2018 at 3:53 PM, Logan Gunthorpe wrote:
>>
>>
>> On 28/03/18 01:44 PM, Christian König wrote:
>>> Well, isn't that exactly what d
struct dvb_frontend *frontend[2];
Maybe define something like CX231XX_MAX_FRONTEND and use it here
rather than using a hardcoded 2.
Alex
>
> /* feed count management */
> struct mutex lock;
> @@ -386,17 +386,17 @@ static int attach_xc5000(u8 addr, struct cx231xx *dev)
>
, but it applies against Linus' tree
> with a couple offsets)
>
> arch/x86/include/asm/atomic64_32.h | 2 +-
> drivers/acpi/custom_method.c | 2 +-
> drivers/acpi/fan.c | 2 +-
> drivers/gpu/drm/amd/displ
On Wed, Nov 1, 2017 at 10:06 AM, Liviu Dudau wrote:
> Mappings need to be unmapped by calling dma_buf_unmap_attachment() and
> not by calling again dma_buf_map_attachment(). Also fix some spelling
> mistakes.
>
> Signed-off-by: Liviu Dudau
Reviewed-by: Alex Deucher
> ---
nel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_acp.c
for the audio side:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/soc/amd/acp-pcm-dma.c
Alex
This patch should be dropped as Jasmin is updating this driver.
Thanks,
On 05/09/2017 02:27 PM, Alexandre Ghiti wrote:
Replace hardcoded function names in print info with __func__.
Signed-off-by: Alexandre Ghiti
---
drivers/staging/media/cxd2099/cxd2099.c | 6 +++---
1 file changed, 3 insert
for instance on a CSC property representing
>> a CRTC output CSC (just before hitting the connector), which happens
>> to be converting RGB to YCbCr:
>>
>> CRTC -> GAMMA -> RGB_TO_YCBCR_CSC
>>
>> ...the enum value "BT.601 Limited" means that
eople need to stop doing this windowed memory stuff :)
>
Blame 32 bit systems and GPUs with tons of vram :)
I think resizable bars are finally coming in a useful way so this
should go away soon.
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body
On Thu, 29 Sep 2016 21:24:04 +0200
Christoph Hellwig wrote:
> On Thu, Sep 29, 2016 at 01:21:01PM -0600, Alex Williamson wrote:
> > Sorry for the delay, slipped by me. Overall a really nice cleanup.
> > One tiny nit, the commit log mis-names the function as
> > pci_irq_all
ci/vfio_pci_private.h | 1 -
> 2 files changed, 10 insertions(+), 36 deletions(-)
Sorry for the delay, slipped by me. Overall a really nice cleanup.
One tiny nit, the commit log mis-names the function as
pci_irq_allocate_vectors instead of pci_alloc_irq_vectors. With that,
Acked-by: Alex Wil
On Thu, Apr 21, 2016 at 2:12 AM, Antti Palosaari wrote:
> On 04/20/2016 12:13 PM, Alex Rad wrote:
>>
>> On Wed, Apr 20, 2016 at 1:02 AM, Antti Palosaari wrote:
>>>
>>> Hello
>>> I am not happy with that new module parameter as I cannot see real need
>
On Wed, Apr 20, 2016 at 1:02 AM, Antti Palosaari wrote:
> Hello
> I am not happy with that new module parameter as I cannot see real need for
> it. So get rid of it.
My reasoning for this is:
1) We know of just two devices which may have the issue, but there are
probably more. The module paramet
This fixes a checkpatch style error in vpfe_buffer_queue_setup.
Signed-off-by: Alex Dowad
---
drivers/staging/media/davinci_vpfe/vpfe_video.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/davinci_vpfe/vpfe_video.c
b/drivers/staging/media/davinci_vpfe
IGMP and such.
So, I think the question is, what would be the method you'd choose to
combine packets received from dvb0_N interfaces into a single interface?
Can this be done multicast agnostic? Without static routing?
Cheers,
Alex
--
To unsubscribe from this list: send the line "un
Hi there,
on Raspbian, the Debian port for the Raspberry Pi, the needed
"lsdiff" is in the package "patchutils" and
"Proc::ProcessTable" is in the package "libproc-processtable-perl".
Thanks a lot for your good work!
Kind Regards
Alex
--
To u
Hi Mauro,
As discussed at LinuxCon (New Orleans), please invite/add me to the V4L/DVB
mini-summit in Edinburgh. I cannot commit to attending until travel approvals
are in place, so please consider this as tentative.
Regards,
Alex Luccisano
--
To unsubscribe from this list: send the line
y small piece of code.) But
>> that is probably what you are trying to avoid.
>
> I've been trying to get my head around how PRIME relates to DDX
> drivers. As I understand it (which is likely wrong), you have a laptop
> with both an Intel & an nVidia GPU. You have both the i915 & nouveau
> kernel drivers loaded. What I'm not sure about is which GPU's display
> controller is actually hooked up to the physical connector? Perhaps
> there is a MUX like there is on Versatile Express?
>
> What I also don't understand is what DDX driver is loaded? Is it
> xf86-video-intel, xf86-video-nouveau or both? I get the impression
> that there's a "master" DDX which implements 2D operations but can
> import buffers using PRIME from the other driver and draw to them.
> Or is it more that it's able to export rendered buffers to the
> "slave" DRM for scanout? Either way, it's pretty similar to an ARM
> SoC setup which has the GPU and the display as two totally
> independent devices.
>
In the early days, there was a MUX to switch the displays between the
two GPUs, but most modern systems are MUX-less and the dGPU is either
connected to no displays or in some cases the local panel is attached
to the integrated GPU and the external displays are connected to the
dGPU.
In the MUX-less case, the dGPU can be used to render, and then the
result is copied to the integrated GPU for display.
Alex
--
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
t enables auto routing via HDMI. what exactly are you trying to
do? Discrete graphics cards only support audio via HDMI or DP.
Alex
>
> May 9 19:32:37 retraite kernel: [6.660223] snd_hda_intel :01:00.1:
> irq 45 for MSI/MSI-X
> May 9 19:32:37 retraite kernel: [6.660242]
es]
> Digital Stereo (HDMI) on Squeeze, it was HD-Audio Generic Digital Stereo
> (HDMI).
> It works but i'm not able to get analogic output, only HDMI / display port
> that i can't use.
You need to enable the audio parameter in the radeon driver. Boot with:
radeon.aud
n, and outputs a
> video signal in another format? (transcoder?)
In KMS parlance, we have two objects a crtc and an encoder. A crtc
reads data from memory and produces a data stream with display timing.
The encoder then takes that datastream and timing from the crtc and
converts it so
C_TYPE_OTHER) before board type testing "switch". (Perhaps, putting it
to 110i's "case" would be more correct, but it seem to work anyway.)
Signed-off-by: Alex Volkov
---
--- a/drivers/media/video/saa7134/saa7134-input.c 2012-10-17
08:50:15.0 +0600
+++
Driver for mt9v022 camera sensor is fully compatible for mt9v024 camera sensor
with the exception of several registers which have been changed addresses.
mt9v024 also has improved and additional features, but they are currently not
in use.
Signed-off-by: Alex Gershgorin
---
drivers/media/video
Hi Guennadi,
Thank you for your very detailed comment.
> Hi Alex
> Yes, this looks much better to me now. Still, I'd like to ask you to
> make a couple more changes. First - there are different opinions about how
> really important a patch description is, whether there are at
Signed-off-by: Alex Gershgorin
---
drivers/media/video/Kconfig |2 +-
drivers/media/video/mt9v022.c | 45
2 files changed, 37 insertions(+), 10 deletions(-)
Changes for v2:
Fixed comment from Guennadi.
diff --git a/drivers/media/video
From: Alex Gershgorin
This patch check the state of the buffer when calling buf_init() method.
The thread
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/48587
also includes report witch can show the problem. This patch solved the problem.
Both MMAP and USERPTR methods
> Hi Guennadi,
>
> > On Mon, 30 Jul 2012, Alex Gershgorin wrote:
>
> > This patch check the state of the buffer when calling buf_init() method.
> > The thread
> > http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/48587
> > also inc
Hi Guennadi,
>> Thanks for the patch, comments below.
Thanks for you comments.
>> On Mon, 30 Jul 2012, Alex Gershgorin wrote:
> This patch has been successfully tested
>
> Signed-off-by: Alex Gershgorin
> ---
> drivers/media/video/Kconfig |2 +-
> driver
Hi Guennadi,
> On Mon, 30 Jul 2012, Alex Gershgorin wrote:
> This patch check the state of the buffer when calling buf_init() method.
> The thread
> http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/48587
> also includes report witch can show the prob
.
Signed-off-by: Alex Gershgorin
---
drivers/media/video/mx3_camera.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/media/video/mx3_camera.c b/drivers/media/video/mx3_camera.c
index f13643d..950a8fe 100644
--- a/drivers/media/video/mx3_camera.c
+++ b
This patch has been successfully tested
Signed-off-by: Alex Gershgorin
---
drivers/media/video/Kconfig |2 +-
drivers/media/video/mt9v022.c | 28 ++--
2 files changed, 19 insertions(+), 11 deletions(-)
diff --git a/drivers/media/video/Kconfig b/drivers/media
ers myself like it says in the direcitons
> at mythtv.org. This is supposed to be a supported card, does anyone have any
> experience with it?
I've got one and it worked years ago, but I haven't used it since.
IIRC, the initial blackbird support was added using this card, but I'm
no
x-cards.c
that product ids 2710, 2750 and 2751 are recognised by the driver, but
not 2711.
I'm tempted to add it as a EM2800_BOARD_UNKNOWN and see if it works.
Is there some methodology I should follow to get a new webcam to work?
Thanks,
Alex
PS. I'm not subscribed.
--
To unsubsc
it stands. What help is needed for it?
Unfortunately, I don't think there is much AMD can do. We sold our
multimedia DTV division to Broadcom several years ago. IANAL, so I
don't know exactly what rights we retained for the IP. You may need
to talk to Broadcom now.
Alex
>
> Fi
Hi Ritesh,
Please send in the future CC to laurent.pinch...@ideasonboard.com and
linux-media@vger.kernel.org
> Hi Alex,
> I also started working with OMAP35x torpedo kit, I successful compile Linux
> 3.0 and ported on the board.
> Device is booting correctly but probe function
0
ioctl(3, VIDIOC_QBUF or VT_SETACTIVATE, 0x7ece990c) = 0
I do not understand what's the problem, maybe need to implement
FBIO_WAITFORVSYNC ioctl for mx3fb ?
Thanks,
Alex
--
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
it+0x0/0xac) from [<8001e004>]
(sys_exit_group+0x18/0x24)
r4:000a3d78 r3:
[<8001dfec>] (sys_exit_group+0x0/0x24) from [<8000e3e0>]
(ret_fast_syscall+0x0/0x30)
Code: 05852024 e5941268 e5940264 e2842f99 (e581)
ument
---[ end trace 23ac1073b67b7fc0 ]---
Fixing recursive fault but reboo
case that CONFIG_FB_MX3_OVERLAY is not defined, mx3fb is completely
backward compatible.
Blend mode, only global alpha blending has been tested.
Signed-off-by: Guennadi Liakhovetski
Signed-off-by: Alex Gershgorin
---
Applies to v3.4-rc4
Changes since v1:
*Some fixes after review
*Added
Hi Guennadi,
Thanks for your review.
> > Thanks for reviving, fixing and submitting this code!
I think that this code is beneficial :-)
> > On Wed, 18 Apr 2012, Alex Gershgorin wrote:
> This patch is based on the original version submitted by Guennadi
> Liakhovetski,
>
completely
backward compatible.
Blend mode, only global alpha blending has been tested.
Signed-off-by: Alex Gershgorin
Signed-off-by: Guennadi Liakhovetski
---
Applies to v3.4-rc3
---
drivers/video/Kconfig |7 +
drivers/video/mx3fb.c | 318
gt; corresponding info, I could give it a try.
Probably useful to start with the config from a similar card (lots of
vendors use the same reference design) and see how much of it works
then tweak from there until you get it fully working.
Alex
--
To unsubscribe from this list: send the line &quo
sended to Sascha and ARM mailing list another patch
i.MX35-PDK-Add-regulator-support, this also will need be used.
> > Are you getting the camera image with the correct colors?
Now the camera works fine without any problems, except those,
who have already eliminated :-)
Regards,
Alex Gershgo
Hi Sascha,
Thanks for you comments.
On Tue, Mar 20, 2012 at 12:29:52PM +0200, Alex Gershgorin wrote:
> This patch add set_rate and round_rate calls to csi_clk. This is needed
> to give mx3-camera control over master clock rate to camera.
> >The file you are patching is scheduled fo
This patch add set_rate and round_rate calls to csi_clk. This is needed
to give mx3-camera control over master clock rate to camera.
Signed-off-by: Alex Gershgorin
---
arch/arm/mach-imx/clock-imx35.c | 57 +-
1 files changed, 55 insertions(+), 2 deletions
gt; It's scheduled there. I should have responded with an applied message.
>
> Please apply this one too: http://patchwork.ozlabs.org/patch/144942/
>
Regards,
Alex Gershgorin
--
Pengutronix e.K. | |
Industrial Linux
In i.MX35-PDK, OV2640 camera is populated on the
personality board. This camera is registered as a subdevice via soc-camera
interface.
Signed-off-by: Alex Gershgorin
---
arch/arm/mach-imx/mach-mx35_3ds.c | 96 +
1 files changed, 96 insertions(+), 0
Hi Fabio,
On Mon, Mar 12, 2012 at 1:28 PM, Alex wrote:
> In i.MX35-PDK, OV2640 camera is populated on the
> personality board. This camera is registered as a subdevice via soc-camera
> interface.
>
> Signed-off-by: Alex Gershgorin
> >Are you able to get the camera
Hi Sascha,
Thanks for you comments.
> In i.MX35-PDK, OV2640 camera is populated on the
> personality board. This camera is registered as a subdevice via soc-camera
> interface.
>
> Signed-off-by: Alex Gershgorin
> ---
> arch/arm/mach-imx/m
In i.MX35-PDK, OV2640 camera is populated on the
personality board. This camera is registered as a subdevice via soc-camera
interface.
Signed-off-by: Alex Gershgorin
---
arch/arm/mach-imx/mach-mx35_3ds.c | 87 +
1 files changed, 87 insertions(+), 0
camera.
> >Do you have this patch applied?
Yes I need to prepare it.
> >http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=f910fb8fcd1c97788f2291c8646597bcd87ee061
> >Also, try to isolate the display from this issue. Capture the image to
> >a
>On my mx31pdk I get the same dmaengine errors and the ov2640 does work fine.
>I think you can go ahead and try to use the camera on the mx35pdk now.
>You can try:
>gst-launch -v v4l2src device=/dev/video0 !
>video/x-raw-yuv,width=320,height=240,framerate=25/1 ! ffmpegcolorspace
>! fbdevsink
Hi Guennadi,
Thanks for you comments...
>>>Hi Alex
>>>Why is the cc-list mangled again? Why is the V4L list dropped again?
>>>What's so difficult about hitting the "reply-to-all" button?
You are absolutely right, I hope that now the cc-list valid
fine.
>I think you can go ahead and try to use the camera on the mx35pdk now.
>You can try:
>gst-launch -v v4l2src device=/dev/video0 !
>video/x-raw-yuv,width=320,height=240,framerate=25/1 ! ffmpegcolorspace
>! fbdevsink
Thank Fabio I'll try to check it.
Regards
Alex Gershgo
From: Alex Gershgorin
Sent: Tuesday, March 06, 2012 3:22 PM
To: Guennadi Liakhovetski
Cc: linux-ker...@vger.kernel.org; Linux Media Mailing List; Sascha Hauer
Subject: RE: mx3-camera
Thanks Guennadi,
>Hi Alex
>(adding v4l and Sascha to CC)
>
Thanks Guennadi,
>Hi Alex
>(adding v4l and Sascha to CC)
>On Tue, 6 Mar 2012, Alex Gershgorin wrote:
> Hi Guennadi,
>
> I'm working on I.MX35 PDK platform with use 3.3.0-rc6 version of the Linux
> Kernel.
> Here is my Kernel boot message
>
> "Li
Hi,
On 02/26/2012 09:58 PM, Guennadi Liakhovetski wrote:
>>> It might be difficult to completely eliminate the CPU, at the very least
>>> you need to queue and dequeue buffers to and from the V4L driver. To avoid
>>> even that, in principle, you could try to use only one buffer, but I don't
>
-Original Message-
From: Guennadi Liakhovetski [mailto:g.liakhovet...@gmx.de]
Sent: Sunday, February 26, 2012 10:58 PM
To: Alex Gershgorin
Cc: linux-media@vger.kernel.org
Subject: RE: i.mx35 live video
On Sun, 26 Feb 2012, Alex Gershgorin wrote:
> > Thanks Guennadi for your
> Thanks Guennadi for your quick response ,
>
> >Hi Alex
>
> > Hi Guennadi,
> >
> > We would like to use I.MX35 processor in new project.
> > An important element of the project is to obtain life video from the camera
> > and display it on di
Thanks Guennadi for your quick response ,
>Hi Alex
> Hi Guennadi,
>
> We would like to use I.MX35 processor in new project.
> An important element of the project is to obtain life video from the camera
> and display it on display.
> For these purposes, we want to use
Hi Laurent,
On Saturday 10 December 2011 14:36:17 Alex Gershgorin wrote:
> > Hi Sakari,
> >
> > Thank you for your quick response and sorry for stupid question.
> > Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> > because OMAP 3 camera controller depends
Hi Laurent,
On 12/07/2011 02:08 PM, Laurent Pinchart wrote:
Hi Alex,
On Wednesday 07 December 2011 11:48:36 Alex wrote:
On 11/30/2011 04:51 AM, Laurent Pinchart wrote:
On Monday 28 November 2011 22:53:19 Alex wrote:
On 11/28/2011 10:20 PM, Laurent Pinchart wrote:
On Monday 28 November 2011
Hi Alex,
On Saturday 10 December 2011 14:36:17 Alex Gershgorin wrote:
> > Hi Sakari,
> >
> > Thank you for your quick response and sorry for stupid question.
> > Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> > because OMAP 3 camera controller depends
device registered as video7
Now I plan to start using a newer version of the Linux kernel 3.2.0-rc4, but
unfortunately faced with the problem.
That suggest?
Thanks,
Alex Gershgorin --
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message
.
Regards,
Alex Gershgorin
Hi Alex,
Alex Gershgorin wrote:
> Hi All,
>
> I have problem in booting the Kernel.
> Here the problematic part of the boot message.
> As I understand it happens when isp_probe calling and it calls isp->iommu_dev
> = omap_find_iommu_device("isp&q
ppreciate any help.
Thanks
Alex Gershgorin--
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 11/30/2011 04:51 AM, Laurent Pinchart wrote:
Hi Alex,
On Monday 28 November 2011 22:53:19 Alex wrote:
On 11/28/2011 10:20 PM, Laurent Pinchart wrote:
On Monday 28 November 2011 20:14:25 Alex wrote:
On 11/28/2011 10:08 PM, Laurent Pinchart wrote:
On Monday 28 November 2011 19:04:22 Alex
On 11/28/2011 10:20 PM, Laurent Pinchart wrote:
Hi Alex,
On Monday 28 November 2011 20:14:25 Alex wrote:
On 11/28/2011 10:08 PM, Laurent Pinchart wrote:
On Monday 28 November 2011 19:04:22 Alex wrote:
Fortunately my laptop is alive now so I'm sending you lsusb output.
Thanks. Would you
On 11/28/2011 10:08 PM, Laurent Pinchart wrote:
Hi Alex,
On Monday 28 November 2011 19:04:22 Alex wrote:
Hi Laurent,
Fortunately my laptop is alive now so I'm sending you lsusb output.
Thanks. Would you mind re-running lsusb -v -d '04f2:b221' as root ? What
laptop brand/mode
Hi Laurent,
Fortunately my laptop is alive now so I'm sending you lsusb output.
About reverting commit - will try bit later.
Best regards,
Alex
On 11/28/2011 01:35 PM, Laurent Pinchart wrote:
Hi Alex,
On Sunday 27 November 2011 21:01:23 Alex wrote:
Hi guys,
I'm using kernel 3
7;s be supported on all modern KMS drivers (radeon, intel, nouveau)
assuming you have a recent enough userspace to deal with the hotplug
uevents.
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel
igure pipeline with use MC User space API.
Regards,
Alex Gershgorin
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Wednesday, July 27, 2011 11:59 AM
To: James
Cc: Sakari Ailus; linux-media@vger.kernel.org; michael.jo...@matrix-vision.de;
Alex Gersh
Hi Laurent
Good news!
Now registration is successful, many thanks.
Now I can move on to the next stage of work.
Regards,
Alex Gershgorin
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Wednesday, June 29, 2011 6:55 PM
To: Alex Gershgorin
Cc
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Wednesday, June 29, 2011 6:55 PM
To: Alex Gershgorin
Cc: 'Sakari Ailus'; 'Michael Jones'; 'linux-media@vger.kernel.org';
'age...@rambler.ru'
Subject: Re: F
: isp: version 1.1
isp_register_subdev_group: Unable to register subdev
What could be the problem, why sub device can't pass a registration?
Thanks,
Alex Gershgorin
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com] Sent:
Wednesday, May 25, 2011 1:02 P
Hello,
My name is Alex Tucker and I am the engineering manager here at
ViewCast. We have released two new Osprey cards based on the Conexant
CX23888 chipset - which is similar to the CX25878/BT878A chipset that
has some support in the Open Source community. We are interested in
having Linux
Of course, in any case, you'll be the first who will know the results :-)
Regards,
Alex Gershgorin
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Wednesday, May 25, 2011 1:02 PM
To: Alex Gershgorin
Cc: 'Sakari Ailus'; Michae
Zoom
OMAP35xx Torpedo.
Thanks for this patch :-)
Regards,
Alex Gershgorin
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Wednesday, May 25, 2011 10:22 AM
To: Alex Gershgorin
Cc: 'Sakari Ailus'; Michael Jones; 'linux-media@vger.ker
Vertical or Horizontal
synchronization signals, according struct isp_parallel_platform_data, is it not
possible?
struct isp_parallel_platform_data {
unsigned int data_lane_shift:2;
unsigned int clk_pol:1;
unsigned int bridge:4;
};
Regards,
Alex Gershgorin
-Original
problem without writing a
special driver?
Advise in what direction to go in my case?
Regards,
Alex Gershgorin
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Thursday, May 19, 2011 5:27 PM
To: Michael Jones
Cc: Alex Gershgorin; 'linux-
Thanks Laurent,
My video source is not the video camera and performs many other functions.
For this purpose I have RS232 port.
As for the video, it runs continuously and is not subject to control except for
the power supply.
Regards,
Alex Gershgorin
Can the video source be controlled at all
Thanks for your quick response :-)
Unfortunately, my video source has no additional interfaces.
Best Regards,
Alex Gershgorin
Embedded Software Engineer
E-mail: al...@meprolight.com
-Original Message-
From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
Sent: Thursday, May 19, 2011 2:09 PM
enhancements, as we'd throw
>> >> > away the
>> >> > years of testing and the regression count would be way too high.
>> >> >
>> >> I had a look at the DRM EDID code, but for quirks it looks pretty much
>> >> the same.
>
Adding dri-devel.
On Tue, Mar 22, 2011 at 1:32 PM, Mythri P K wrote:
> Adding support for common EDID parsing in kernel.
>
> EDID - Extended display identification data is a data structure provided by
> a digital display to describe its capabilities to a video source, This a
> standard supported
On Wed, Mar 16, 2011 at 1:49 PM, Laurent Pinchart
wrote:
> Hi Alex,
>
> On Wednesday 16 March 2011 17:09:45 Alex Deucher wrote:
>> On Wed, Mar 16, 2011 at 3:37 AM, Li Li wrote:
>> > Sorry but I feel the discussion is a bit off the point. We're not
>> >
strange tiling formats, etc.). You might be able to come up with some
kind of basic framework like TTM, but by the time you add the
necessary quirks for various hw, it may be bigger than you want.
That's why we have GEM and TTM and driver specific memory management
ioctls in the drm.
Alex
&
On Wed, Mar 16, 2011 at 4:52 AM, Laurent Pinchart
wrote:
> Hi Alex,
>
> On Tuesday 15 March 2011 17:47:47 Alex Deucher wrote:
>
> [snip]
>
>> FWIW, I have yet to see any v4l developers ever email the dri mailing
>> list while discussing GEM, TTM, or the DRM, al
tops and crossfire
(multi-gpu) type things. We already share buffers between multiple
userspace acceleration drivers and the drm using the DRI protocol.
>
> I know that STE and ARM has a vision to have a hwmem/ump alike API and
> that Linaro is one place to resolve this. As Jesse Barker
epending on the GPU's capabilities and what the
buffers are used for.
3. unpinned system pages. Depending on the GPU, they have to be
copied to DMAable memory before the GPU can access them.
The DRI protocol (used for communication between GPU acceleration
drivers) doesn'
is my understanding that on
> some platforms (particular those used for set-top boxes) the video buffers are
> on memory that is not accessible from the CPU (rights management related). But
> apparently you still have to be able to refer to it. I may be wrong, it's
> something I was
output device with OpenGL/ES capabilities ? We'll need to think about
> it
> at some point.
> (Laurent)
This is what I've been worried about. v4l grows it's own output and
modesetting API and now we have multiple incompatible stacks for
graphics. Maybe the existing drm
On Wed, Mar 2, 2011 at 4:13 AM, Hans Verkuil wrote:
> Hi Alex,
>
> On Tuesday, March 01, 2011 18:52:28 Alex Deucher wrote:
>> On Tue, Mar 1, 2011 at 4:59 AM, Martin Bugge (marbugge)
>> wrote:
>> > Author: Martin Bugge
>> > Date: Tue, 1 March 2010
>>
rates
> (~400 bits/s).
>
> A CEC device may have any of 15 logical addresses (0 - 14).
> (address 15 is broadcast and some addresses are reserved)
>
It would be nice if this was not tied to v4l as we'll start seeing CEC
support show in GPUs soon as well.
Alex
>
> R
On Wed, Feb 9, 2011 at 7:51 PM, Andy Walls wrote:
> On Wed, 2011-02-09 at 02:12 -0500, Alex Deucher wrote:
>> On Tue, Feb 8, 2011 at 5:47 PM, Andy Walls wrote:
>> > On Tue, 2011-02-08 at 10:28 -0500, Alex Deucher wrote:
>> >> On Tue, Feb 8, 2011 at 4:47 AM, Hans Ve
1 - 100 of 143 matches
Mail list logo