On 11/05/11 14:55, Premi, Sanjeev wrote:
Current checks for cpu type were too restrictive leading
to failures for other silicons in same family.
The problem was found while testing audio playback on
AM37x and AM35x processors. But should exist on OMAP36xx
as well.
Signed-off-by: Sanjeev
Current checks for cpu type were too restrictive leading
to failures for other silicons in same family.
The problem was found while testing audio playback on
AM37x and AM35x processors. But should exist on OMAP36xx
as well.
Signed-off-by: Sanjeev Premi pr...@ti.com
cc: Mark Brown
On Wednesday 11 May 2011 16:55:35 Premi, Sanjeev wrote:
Current checks for cpu type were too restrictive leading
to failures for other silicons in same family.
The problem was found while testing audio playback on
AM37x and AM35x processors. But should exist on OMAP36xx
as well.
On Wed, 11 May 2011 19:25:35 +0530
Sanjeev Premi pr...@ti.com wrote:
Current checks for cpu type were too restrictive leading
to failures for other silicons in same family.
The problem was found while testing audio playback on
AM37x and AM35x processors. But should exist on OMAP36xx
as
On Wed, May 11, 2011 at 07:25:35PM +0530, Sanjeev Premi wrote:
Current checks for cpu type were too restrictive leading
to failures for other silicons in same family.
The problem was found while testing audio playback on
AM37x and AM35x processors. But should exist on OMAP36xx
as well.
On 05/11/11 06:55, Sanjeev Premi wrote:
Current checks for cpu type were too restrictive leading
to failures for other silicons in same family.
The problem was found while testing audio playback on
AM37x and AM35x processors. But should exist on OMAP36xx
as well.
Signed-off-by: Sanjeev
From: Steve Calfee [stevecal...@gmail.com]
Sent: Wednesday, May 11, 2011 11:46 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org; Girdwood, Liam
Subject: Re: [alsa-devel] [PATCH] ASoC: omap-mcbsp: Remove restrictive checks
for cpu type
[snip]...[snip]
Hi,
I removed all
