-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Shilimkar, Santosh
Sent: Thursday, September 09, 2010 4:53 PM
To: linux-omap@vger.kernel.org
Cc: t...@atomide.com; khil...@deeprootsystems.com; Shilimkar, Santosh
-Original Message-
[..snip..]
The series is boot tested tested on 4430 SDP, Blaze with
omap_4430sdp_defconfig with file over NFS and MMC.
Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3
SDPs. Same observation with Panda
With
-Original Message-
From: Ghorai, Sukumar
Sent: Friday, September 10, 2010 4:00 PM
To: Shilimkar, Santosh; Kevin Hilman
Cc: linux-omap@vger.kernel.org; t...@atomide.com
Subject: RE: [PATCH 0/7] omap4: Fixes, hacks for es2.0
-Original Message-
[..snip..]
The
Hi,
On Thu, Sep 09, 2010 at 12:28:27PM -0500, venki kaps wrote:
one thing i have not understood, why it requires to power down when
the device is booted without
a USB cable?
why would the phy be powered up for no use ?
After booting, just attach/detach the usb cable, then i have not seen
Hi,
On Thu, Sep 09, 2010 at 08:24:12AM -0500, Shilimkar, Santosh wrote:
Updated version attached.
attaching is generally not a good idea, but if you do so, at least use
.diff as extension (or .patch or .txt) so that most mutt users will see
it dumped onto the messaged.
I think that if you
-Original Message-
From: Balbi, Felipe
Sent: Friday, September 10, 2010 6:04 PM
To: Shilimkar, Santosh
Cc: linux-omap@vger.kernel.org; Cousson, Benoit; t...@atomide.com;
khil...@deeprootsystems.com; Balbi, Felipe
Subject: Re: [PATCH 2/7] omap4: Temporary fix silicon version
On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar s-gho...@ti.com wrote:
-Original Message-
[..snip..]
The series is boot tested tested on 4430 SDP, Blaze with
omap_4430sdp_defconfig with file over NFS and MMC.
Also boot tested omap3_defconfig with ramdisk on OMAP4
-Original Message-
From: Ricardo Salveti [mailto:rsalv...@rsalveti.net]
Sent: Friday, September 10, 2010 8:34 PM
To: Ghorai, Sukumar
Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org;
t...@atomide.com
Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
On Fri,
-Original Message-
From: Ricardo Salveti [mailto:rsalv...@rsalveti.net]
Sent: Friday, September 10, 2010 8:34 PM
To: Ghorai, Sukumar
Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org;
t...@atomide.com
Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0
On Fri,
Hi Felipe,
On Wed, Aug 18, 2010 at 10:19:16AM +0300, Felipe Balbi wrote:
hi,
On Wed, Aug 18, 2010 at 08:19:34AM +0200, Balbi Felipe (Nokia-MS/Helsinki)
wrote:
From: Felipe Balbi felipe.ba...@nokia.com
Some modules already need to talk to at least PROTECT_KEY
register, while at that,
On Friday 10 September 2010 12:25:40 am Michael Williamson wrote:
Hi Cyril,
On 09/09/2010 03:51 PM, Cyril Chemparathy wrote:
Hi Mike,
[...]
The hang is in wait_for_user_access() in the davinci_mdio_read() call.
Looks like the state machine got put back into IDLE somewhere between
On Fri, Sep 10, 2010 at 12:09 PM, Ghorai, Sukumar s-gho...@ti.com wrote:
-Original Message-
On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar s-gho...@ti.com wrote:
-Original Message-
[..snip..]
The series is boot tested tested on 4430 SDP, Blaze with
Hello,
I've tested the current linux-omap Git tree and Kevin's pm-core branch
on a BeagleBoard using the omap3_defconfig, and when trying a suspend
to RAM, I get a Class driver suspend failed for cpu0 :
# echo mem /sys/power/state
[ 93.395050] PM: Syncing filesystems ... done.
[ 93.410827]
Hi,
On Fri, Sep 10, 2010 at 10:48:14AM -0500, Thomas Petazzoni wrote:
I also have a problem with USB support, both on linux-omap and Kevin's
pm-core branch. My USB Ethernet adapter, supported by the asix driver,
isn't detected anymore. With a pm git tree of a couple of weeks ago, it
was
Hi,
I'm trying to implement LCD brightness control for the Gumstix Overo (TI
OMAP 3503) + Palo43 module. GPIO 144 which can also support PWM signal
generation is, connected to the LCD's display on/off signal.
Could someone point me to an example board-configuration file that I can use,
Hi,
you should break your lines at 80-chars
On Fri, Sep 10, 2010 at 12:43:48PM -0500, Elvis Dowson wrote:
Could someone point me to an example board-configuration file that I
can use, to similarly configure the board-overo.c file, to configure
GPIO144 to PWM mode, to enable brightness control
On Fri, 10 Sep 2010 20:00:53 +0300
Felipe Balbi ba...@ti.com wrote:
On Fri, Sep 10, 2010 at 10:48:14AM -0500, Thomas Petazzoni wrote:
I also have a problem with USB support, both on linux-omap and
Kevin's pm-core branch. My USB Ethernet adapter, supported by the
asix driver, isn't detected
With the current, linux-omap:master branch
(8475b9e5077d9e9b4ba7a92afd4c5c7d65564c09), I get the following errors
on a overo system when erasing flash:
r...@ts3:~# flash_eraseall -j /dev/mtd4
Erasing 128 Kibyte @ 8c4 -- 56 % complete. Cleanmarker written at 8c2.
flash_eraseall: /dev/mtd4:
Thomas Petazzoni thomas.petazz...@free-electrons.com writes:
Hello,
I've tested the current linux-omap Git tree and Kevin's pm-core branch
on a BeagleBoard using the omap3_defconfig, and when trying a suspend
to RAM, I get a Class driver suspend failed for cpu0 :
# echo mem
With CONFIG_MTD_NAND_OMAP_PREFETCH_DMA, there is a compile
error that this patch fixes.
Signed-off-by: Cliff Brake cbr...@bec-systems.com
---
drivers/mtd/nand/omap2.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
Grant Likely grant.lik...@secretlab.ca writes:
On Thu, Aug 19, 2010 at 05:56:43PM -0700, Kevin Hilman wrote:
Grant Likely grant.lik...@secretlab.ca writes:
On Fri, Aug 13, 2010 at 8:05 AM, Charulatha V ch...@ti.com wrote:
This patch series implements McSPI Module in HWMOD FW way
and use
Hi Mike,
I have merged your latest two emails and responded to both here.
[...]
Your patch doesn't work with my board. It does attempt to reset the bus on
the read call,
but following wait_for_user_access() calls are timing out and the _read() and
_write() calls punt.
I bumped up the
This set consists of the following patches:
1/6 SoC Camera: add driver for OMAP1 camera interface
2/6 OMAP1: Add support for SoC camera interface
3/6 SoC Camera: add driver for OV6650 sensor
4/6 SoC Camera: add support for g_parm / s_parm operations
5/6 OMAP1: Amstrad Delta:
This patch adds support for SoC camera interface to OMAP1 devices.
Created and tested against linux-2.6.36-rc3 on Amstrad Delta.
For successfull compilation, requires a header file provided by PATCH 1/6 from
this series, SoC Camera: add driver for OMAP1 camera interface.
Signed-off-by: Janusz
This patch adds configuration data and initialization code required for camera
support to the Amstrad Delta board.
Three devices are declared: SoC camera, OMAP1 camera interface and OV6650
sensor.
Default 12MHz clock has been selected for driving the sensor. Pixel clock has
been limited to
This patch extends the Amstrad Delta camera support with LEDS trigger that can
be used for automatic control of the on-board camera LED. The led turns on
automatically on camera device open and turns off on camera device close.
Created and tested against linux-2.6.36-rc3.
Works on top of patch
This patch adds support for SoC camera interface to OMAP1 devices.
Created and tested against linux-2.6.36-rc3 on Amstrad Delta.
For successfull compilation, requires a header file provided by PATCH 1/6 from
this series, SoC Camera: add driver for OMAP1 camera interface.
Signed-off-by: Janusz
27 matches
Mail list logo
