[PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
From: Muralidharan Karicheri
This patch makes the following changes:-
1) Modify vpif_subdev_info to add board_info, routing information
and vpif interface configuration. Remove addr since it is
part of board_info
2) Add code to setup channel mode and input decoder path for
vpif capture driver
Also incorporated comments against version v0 of the patch series and
added a spinlock to protect writes to common registers
Reviewed-by: Hans Verkuil
Reviewed-by: Kevin Hilman
Signed-off-by: Muralidharan Karicheri
---
Applies to DaVinci tree
arch/arm/mach-davinci/board-dm646x-evm.c| 227 --
arch/arm/mach-davinci/dm646x.c | 52 ++-
arch/arm/mach-davinci/include/mach/dm646x.h | 49 +-
3 files changed, 298 insertions(+), 30 deletions(-)
diff --git a/arch/arm/mach-davinci/board-dm646x-evm.c
b/arch/arm/mach-davinci/board-dm646x-evm.c
index 8c88fd0..c8c65d8 100644
--- a/arch/arm/mach-davinci/board-dm646x-evm.c
+++ b/arch/arm/mach-davinci/board-dm646x-evm.c
@@ -33,7 +33,7 @@
#include
#include
#include
-
+#include
#include
#include
#include
@@ -63,8 +63,8 @@
#define DM646X_EVM_PHY_MASK(0x2)
#define DM646X_EVM_MDIO_FREQUENCY (220) /* PHY bus frequency */
-#define VIDCLKCTL_OFFSET (0x38)
-#define VSCLKDIS_OFFSET(0x6c)
+#define VIDCLKCTL_OFFSET (DAVINCI_SYSTEM_MODULE_BASE + 0x38)
+#define VSCLKDIS_OFFSET(DAVINCI_SYSTEM_MODULE_BASE + 0x6c)
#define VCH2CLK_MASK (BIT_MASK(10) | BIT_MASK(9) | BIT_MASK(8))
#define VCH2CLK_SYSCLK8(BIT(9))
@@ -75,6 +75,18 @@
#define VIDCH2CLK (BIT(10))
#define VIDCH3CLK (BIT(11))
+#define VIDCH1CLK (BIT(4))
+#define TVP7002_INPUT (BIT(4))
+#define TVP5147_INPUT (~BIT(4))
+#define VPIF_INPUT_ONE_CHANNEL (BIT(5))
+#define VPIF_INPUT_TWO_CHANNEL (~BIT(5))
+#define TVP5147_CH0"tvp514x-0"
+#define TVP5147_CH1"tvp514x-1"
+
+static void __iomem *vpif_vidclkctl_reg;
+static void __iomem *vpif_vsclkdis_reg;
+/* spin lock for updating above registers */
+static spinlock_t vpif_reg_lock;
static struct davinci_uart_config uart_config __initdata = {
.enabled_uarts = (1 << 0),
@@ -348,7 +360,7 @@ static struct i2c_board_info __initdata i2c_info[] = {
I2C_BOARD_INFO("cpld_reg0", 0x3a),
},
{
- I2C_BOARD_INFO("cpld_video", 0x3B),
+ I2C_BOARD_INFO("cpld_video", 0x3b),
},
};
@@ -359,18 +371,20 @@ static struct davinci_i2c_platform_data i2c_pdata = {
static int set_vpif_clock(int mux_mode, int hd)
{
+ unsigned long flags;
+ unsigned int value;
int val = 0;
int err = 0;
- unsigned int value;
- void __iomem *base = IO_ADDRESS(DAVINCI_SYSTEM_MODULE_BASE);
- if (!cpld_client)
+ if (!vpif_vidclkctl_reg || !vpif_vsclkdis_reg || !cpld_client)
return -ENXIO;
/* disable the clock */
- value = __raw_readl(base + VSCLKDIS_OFFSET);
+ spin_lock_irqsave(&vpif_reg_lock, flags);
+ value = __raw_readl(vpif_vsclkdis_reg);
value |= (VIDCH3CLK | VIDCH2CLK);
- __raw_writel(value, base + VSCLKDIS_OFFSET);
+ __raw_writel(value, vpif_vsclkdis_reg);
+ spin_unlock_irqrestore(&vpif_reg_lock, flags);
val = i2c_smbus_read_byte(cpld_client);
if (val < 0)
@@ -385,7 +399,7 @@ static int set_vpif_clock(int mux_mode, int hd)
if (err)
return err;
- value = __raw_readl(base + VIDCLKCTL_OFFSET);
+ value = __raw_readl(vpif_vidclkctl_reg);
value &= ~(VCH2CLK_MASK);
value &= ~(VCH3CLK_MASK);
@@ -394,24 +408,30 @@ static int set_vpif_clock(int mux_mode, int hd)
else
value |= (VCH2CLK_AUXCLK | VCH3CLK_AUXCLK);
- __raw_writel(value, base + VIDCLKCTL_OFFSET);
+ __raw_writel(value, vpif_vidclkctl_reg);
/* enable the clock */
- value = __raw_readl(base + VSCLKDIS_OFFSET);
+ spin_lock_irqsave(&vpif_reg_lock, flags);
+ value = __raw_readl(vpif_vsclkdis_reg);
value &= ~(VIDCH3CLK | VIDCH2CLK);
- __raw_writel(value, base + VSCLKDIS_OFFSET);
+ __raw_writel(value, vpif_vsclkdis_reg);
+ spin_unlock_irqrestore(&vpif_reg_lock, flags);
return 0;
}
-static const struct vpif_subdev_info dm646x_vpif_subdev[] = {
+static struct vpif_subdev_info dm646x_vpif_subdev[] = {
{
- .addr = 0x2A,
.name = "adv7343",
+ .board_info = {
+ I2C_BOARD_INFO("adv7343", 0x2a),
+ },
},
{
- .addr = 0x2C,
.name = "ths7303",
+ .board_info = {
+ I2C_BOARD_INFO("ths7303", 0x2c),
+ },
},
};
@@ -421,7 +441,7 @@
Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
On Friday 14 August 2009 23:01:41 m-kariche...@ti.com wrote: > From: Muralidharan Karicheri > > This patch makes the following changes:- > 1) Modify vpif_subdev_info to add board_info, routing information > and vpif interface configuration. Remove addr since it is > part of board_info > > 2) Add code to setup channel mode and input decoder path for > vpif capture driver > > Also incorporated comments against version v0 of the patch series and > added a spinlock to protect writes to common registers A quick question: against which git tree are these arch changes applied? I've lost track of that :-) Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Hans, They are applied against davinci tree (also mentioned in the patch). General procedure what I follow is to create platform code against davinci tree and v4l patches against v4l-dvb linux-next tree. The architecture part of linux-next is not up to date. Davinci tree is at git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci.git Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com >-Original Message- >From: Hans Verkuil [mailto:hverk...@xs4all.nl] >Sent: Saturday, August 15, 2009 8:10 AM >To: Karicheri, Muralidharan >Cc: linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >On Friday 14 August 2009 23:01:41 m-kariche...@ti.com wrote: >> From: Muralidharan Karicheri >> >> This patch makes the following changes:- >> 1) Modify vpif_subdev_info to add board_info, routing information >> and vpif interface configuration. Remove addr since it is >> part of board_info >> >> 2) Add code to setup channel mode and input decoder path for >> vpif capture driver >> >> Also incorporated comments against version v0 of the patch series and >> added a spinlock to protect writes to common registers > >A quick question: against which git tree are these arch changes applied? >I've lost track of that :-) > >Regards, > > Hans > >-- >Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
On Monday 17 August 2009 16:52:20 Karicheri, Muralidharan wrote: > Hans, > > They are applied against davinci tree (also mentioned in the patch). General > procedure what I follow is to create platform code against davinci tree and > v4l patches against v4l-dvb linux-next tree. The architecture part of > linux-next is not up to date. > > Davinci tree is at > > git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci.git I must have missed the mention of this tree. I have a problem, though, as the current v4l-dvb repository doesn't compile against the linux-davinci git tree. And the only way I can get it to compile is to apply all five patches first. However, the whole tree should still compile after each patch is applied. And that goes wrong with your second patch where the Kconfig and Makefile are modified when the new sources aren't even added yet! What I would like to see is a patch series that starts with one patch that makes the current v4l-dvb tree compile again, then the arch patch is added, then a series of v4l-dvb patches in such an order that everything compiles after each step. Merging this is already complicated enough without breaking compilation in this way. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Hans, Ok. I will rework the patch and send you the same. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com >-Original Message- >From: Hans Verkuil [mailto:hverk...@xs4all.nl] >Sent: Monday, August 17, 2009 2:47 PM >To: Karicheri, Muralidharan >Cc: linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >On Monday 17 August 2009 16:52:20 Karicheri, Muralidharan wrote: >> Hans, >> >> They are applied against davinci tree (also mentioned in the patch). >General procedure what I follow is to create platform code against davinci >tree and v4l patches against v4l-dvb linux-next tree. The architecture part >of linux-next is not up to date. >> >> Davinci tree is at >> >> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci.git > >I must have missed the mention of this tree. > >I have a problem, though, as the current v4l-dvb repository doesn't compile >against the linux-davinci git tree. And the only way I can get it to >compile >is to apply all five patches first. > >However, the whole tree should still compile after each patch is applied. >And >that goes wrong with your second patch where the Kconfig and Makefile are >modified when the new sources aren't even added yet! > >What I would like to see is a patch series that starts with one patch that >makes the current v4l-dvb tree compile again, then the arch patch is added, >then a series of v4l-dvb patches in such an order that everything compiles >after each step. > >Merging this is already complicated enough without breaking compilation in >this way. > >Regards, > > Hans > >-- >Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Hans, Would you like the architecture specific changes against v4l-dvb linux-next tree or linux-davinci ? I will rework both the vpfe and vpif patches as per your comment. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com >-Original Message- >From: Hans Verkuil [mailto:hverk...@xs4all.nl] >Sent: Monday, August 17, 2009 2:47 PM >To: Karicheri, Muralidharan >Cc: linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >On Monday 17 August 2009 16:52:20 Karicheri, Muralidharan wrote: >> Hans, >> >> They are applied against davinci tree (also mentioned in the patch). >General procedure what I follow is to create platform code against davinci >tree and v4l patches against v4l-dvb linux-next tree. The architecture part >of linux-next is not up to date. >> >> Davinci tree is at >> >> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-davinci.git > >I must have missed the mention of this tree. > >I have a problem, though, as the current v4l-dvb repository doesn't compile >against the linux-davinci git tree. And the only way I can get it to >compile >is to apply all five patches first. > >However, the whole tree should still compile after each patch is applied. >And >that goes wrong with your second patch where the Kconfig and Makefile are >modified when the new sources aren't even added yet! > >What I would like to see is a patch series that starts with one patch that >makes the current v4l-dvb tree compile again, then the arch patch is added, >then a series of v4l-dvb patches in such an order that everything compiles >after each step. > >Merging this is already complicated enough without breaking compilation in >this way. > >Regards, > > Hans > >-- >Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
On Monday 17 August 2009 22:10:04 Karicheri, Muralidharan wrote: > Hans, > > Would you like the architecture specific changes against v4l-dvb linux-next > tree or linux-davinci ? I will rework both the vpfe and vpif patches as per > your comment. v4l-dvb linux-next. The current v4l-dvb at least compiles against that one, so that is the most appropriate tree to do the patches against. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Hans, I have re-send vpfe capture patch. I will re-send vpif patches tomorrow. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com >-Original Message- >From: Hans Verkuil [mailto:hverk...@xs4all.nl] >Sent: Monday, August 17, 2009 4:27 PM >To: Karicheri, Muralidharan >Cc: linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >On Monday 17 August 2009 22:10:04 Karicheri, Muralidharan wrote: >> Hans, >> >> Would you like the architecture specific changes against v4l-dvb linux- >next tree or linux-davinci ? I will rework both the vpfe and vpif patches >as per your comment. > >v4l-dvb linux-next. The current v4l-dvb at least compiles against that one, >so >that is the most appropriate tree to do the patches against. > >Regards, > > Hans > >-- >Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
On Tuesday 18 August 2009 01:23:10 Karicheri, Muralidharan wrote: > Hans, > > I have re-send vpfe capture patch. I will re-send vpif patches tomorrow. These patches apply fine. I'll merge them in my v4l-dvb-dm646x tree tonight. Thanks! Hans > > Murali Karicheri > Software Design Engineer > Texas Instruments Inc. > Germantown, MD 20874 > new phone: 301-407-9583 > Old Phone : 301-515-3736 (will be deprecated) > email: m-kariche...@ti.com > > >-Original Message- > >From: Hans Verkuil [mailto:hverk...@xs4all.nl] > >Sent: Monday, August 17, 2009 4:27 PM > >To: Karicheri, Muralidharan > >Cc: linux-me...@vger.kernel.org; davinci-linux-open- > >sou...@linux.davincidsp.com; khil...@deeprootsystems.com > >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif > >capture driver > > > >On Monday 17 August 2009 22:10:04 Karicheri, Muralidharan wrote: > >> Hans, > >> > >> Would you like the architecture specific changes against v4l-dvb linux- > >next tree or linux-davinci ? I will rework both the vpfe and vpif patches > >as per your comment. > > > >v4l-dvb linux-next. The current v4l-dvb at least compiles against that one, > >so > >that is the most appropriate tree to do the patches against. > > > >Regards, > > > > Hans > > > >-- > >Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom > > > > -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
On Tuesday 18 August 2009 08:49:13 Hans Verkuil wrote: > On Tuesday 18 August 2009 01:23:10 Karicheri, Muralidharan wrote: > > Hans, > > > > I have re-send vpfe capture patch. I will re-send vpif patches tomorrow. > > These patches apply fine. I'll merge them in my v4l-dvb-dm646x tree tonight. Oops, wrong tree. It's v4l-dvb-vpif. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Mauro, I need to send a set of patches for adding vpif capture driver. Currently the linux-next doesn't have the last patch from Chaithrika applied for vpif display. Is it possible to apply this asap so that I can create the vpif capture patch today? Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com >-Original Message- >From: Hans Verkuil [mailto:hverk...@xs4all.nl] >Sent: Tuesday, August 18, 2009 2:51 AM >To: Karicheri, Muralidharan >Cc: linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >On Tuesday 18 August 2009 08:49:13 Hans Verkuil wrote: >> On Tuesday 18 August 2009 01:23:10 Karicheri, Muralidharan wrote: >> > Hans, >> > >> > I have re-send vpfe capture patch. I will re-send vpif patches tomorrow. >> >> These patches apply fine. I'll merge them in my v4l-dvb-dm646x tree >tonight. > >Oops, wrong tree. It's v4l-dvb-vpif. > >Regards, > > Hans > >-- >Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Mauro, Here are the patches from Chaithrika that I am referring to. http://www.mail-archive.com/linux-me...@vger.kernel.org/msg08254.html http://www.mail-archive.com/linux-me...@vger.kernel.org/msg07676.html Let me know once they are merged... Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 new phone: 301-407-9583 Old Phone : 301-515-3736 (will be deprecated) email: m-kariche...@ti.com >-Original Message- >From: Mauro Carvalho Chehab [mailto:mche...@infradead.org] >Sent: Tuesday, August 18, 2009 1:28 PM >To: Karicheri, Muralidharan >Cc: Mauro Carvalho Chehab; linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com; Hans Verkuil >Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >Em Tue, 18 Aug 2009 11:06:54 -0500 >"Karicheri, Muralidharan" escreveu: > >> Mauro, >> >> I need to send a set of patches for adding vpif capture driver. Currently >the linux-next doesn't have the last patch from Chaithrika applied for vpif >display. Is it possible to apply this asap so that I can create the vpif >capture patch today? > >Sure. Could you please point me what's the patchwork ID(s)[1] of the patch >you need >me to apply at our development tree and at linux-next? > [1] http://patchwork.kernel.org/project/linux-media/list/ > >Cheers, >Mauro ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver
Mauro, Kevin has approved the architecture part of this patch. When can I expect these to be merged to linux-next? Thanks. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 email: m-kariche...@ti.com >-Original Message- >From: Karicheri, Muralidharan >Sent: Tuesday, August 18, 2009 5:51 PM >To: 'Mauro Carvalho Chehab' >Cc: Mauro Carvalho Chehab; linux-me...@vger.kernel.org; davinci-linux-open- >sou...@linux.davincidsp.com; khil...@deeprootsystems.com; Hans Verkuil >Subject: RE: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >capture driver > >Mauro, > >Here are the patches from Chaithrika that I am referring to. >http://www.mail-archive.com/linux-me...@vger.kernel.org/msg08254.html >http://www.mail-archive.com/linux-me...@vger.kernel.org/msg07676.html > >Let me know once they are merged... > >Murali Karicheri >Software Design Engineer >Texas Instruments Inc. >Germantown, MD 20874 >new phone: 301-407-9583 >Old Phone : 301-515-3736 (will be deprecated) >email: m-kariche...@ti.com > >>-Original Message- >>From: Mauro Carvalho Chehab [mailto:mche...@infradead.org] >>Sent: Tuesday, August 18, 2009 1:28 PM >>To: Karicheri, Muralidharan >>Cc: Mauro Carvalho Chehab; linux-me...@vger.kernel.org; davinci-linux- >open- >>sou...@linux.davincidsp.com; khil...@deeprootsystems.com; Hans Verkuil >>Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif >>capture driver >> >>Em Tue, 18 Aug 2009 11:06:54 -0500 >>"Karicheri, Muralidharan" escreveu: >> >>> Mauro, >>> >>> I need to send a set of patches for adding vpif capture driver. >Currently >>the linux-next doesn't have the last patch from Chaithrika applied for >vpif >>display. Is it possible to apply this asap so that I can create the vpif >>capture patch today? >> >>Sure. Could you please point me what's the patchwork ID(s)[1] of the patch >>you need >>me to apply at our development tree and at linux-next? >> [1] http://patchwork.kernel.org/project/linux-media/list/ >> >>Cheers, >>Mauro ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
