On Thu, May 22, 2008 at 4:10 AM, mohammed shareef [EMAIL PROTECTED] wrote:
Hello,
i have enabled the SPI and ADS7846 drivers during kernel (2.6.18)
compilation. i could see in the kernel boot log that they are also
initialized.
On Thu, 22 May 2008 12:53:11 +0530, mohammed shareef
[EMAIL PROTECTED] wrote:
hi arun/all,
when i do cat for interrupts i get:
# cat /proc/interrupts
CPU0
19: 0 MPU DMA
20: 0 MPU DMA
21: 0 MPU DMA
22: 0
On Thu, May 22, 2008 at 12:53 PM, mohammed shareef [EMAIL PROTECTED] wrote:
hi arun/all,
when i do cat for interrupts i get:
# cat /proc/interrupts
CPU0
19: 0 MPU DMA
20: 0 MPU DMA
21: 0 MPU DMA
22: 0
Hello,
This patch series adds D2D (die-to-die) clockdomain handling into
OMAP3 ES2+ builds. It seems the D2D clockdomain logic is still
present on the chip and must be manually programmed to allow the
CORE_D2D clockdomain to go inactive.
For this to work, the pm34xx.c code also had to be
* Paul Walmsley [EMAIL PROTECTED] [080521 12:15]:
Hi Tony,
On Wed, 21 May 2008, Tony Lindgren wrote:
* Paul Walmsley [EMAIL PROTECTED] [080520 18:20]:
Modify mach-omap2/irq.c to simplify the IRQ number-to-IRQ register and
IRQ
number-to-register bit calculations.
How
Hi Pierre,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierre
Ossman
Sent: Thursday, May 22, 2008 12:02 AM
To: Chikkature Rajashekar, Madhusudhan
Cc: 'Russell King - ARM Linux'; linux-omap@vger.kernel.org; [EMAIL PROTECTED]
Subject: Re: MMC/SD
* Kyungmin Park [EMAIL PROTECTED] [080520 22:57]:
Fix compiler error at pm-debug
Thanks, pushing today.
Tony
CC arch/arm/mach-omap2/pm-debug.o
In file included from arch/arm/mach-omap2/pm-debug.c:30:
arch/arm/mach-omap2/prm.h: In function `prm_rmw_reg_bits':
On Fri, May 23, 2008 at 01:16:39AM +0530, Syed Mohammed, Khasim wrote:
The obscene amount of noise here seems to be caused by ext2 being
extremely persistent. This is generally a good thing for your data
though. :)
What is missing is a decent way for a block device to tell the upper
Hi,
On Thu, 2008-05-22 at 21:01 +0100, ext Russell King - ARM Linux wrote:
Basically, what I'm trying to say is that ejecting any medium randomly
from the system is _always_ going to result in problems of some nature.
Some of which you can reduce the impact from, others are fairly terminal.