Hi Koen,
ext Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 30 mei 2008, om 16:12 heeft Kalle Jokiniemi het volgende geschreven:
- Changed register accesses to use __raw_readl(), __raw_writel() and
prm_rmw_reg_bits() functions instread of REG_X = REG_Y type accesses.
Hi,
I have OMAP3530 EVM version _ES 2.1_ from Mistral Solutions.
Can I use http://linux.omap.com/pub/kernel/3530evm/ kernel on it as is?
Thanks,
Prashant K
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Prashant K
Sent: Monday, June 02, 2008 12:29 PM
To: Syed Mohammed, Khasim
Cc: linux-omap@vger.kernel.org
Subject: OMAP3530 EVM Sources are on linux.omap.com
Hi,
I have OMAP3530 EVM version _ES 2.1_
Hi,
This patch currently depends on at least one of the PM workaround
patches from Jouni Hogander. Namely this one:
[PATCH 07/10] 34XX: PM: Workaround to check whether any fck is active
before entering sleep
Sorry I think I forgot to mention this in the patch note. Should we
change the patch in
- Changed register accesses to use prm_{read,write}_mod_reg and
prm_{set,clear,rmw}_mod_reg_bits() functions instread of
REG_X = REG_Y type accesses.
- Changed direct register clock enables/disables to clockframework calls.
- replaced cpu-related #ifdefs with if (cpu_is_()) calls.
-
Added new register and bit definitions to enable Smartreflex driver integration.
Also PRM_VC_SMPS_SA bit definitions' naming was changed to match the naming of
other similar bit definitions.
Signed-off-by: Kalle Jokiniemi [EMAIL PROTECTED]
---
arch/arm/mach-omap2/prm-regbits-34xx.h | 27
The following patch set integrates TI's SmartReflex driver. SmartReflex is a
module that adjusts OMAP3 VDD1 and VDD2 operating voltages around the nominal
values of current operating point depending on silicon characteristics and
operating conditions.
The driver creates two sysfs entries into
Here is an updated version of the SmartReflex driver.
Patches 1 and 2 are same as before, but patch 3 has some new things:
- Changed the register accessing to use the prm_xxx_mod_reg{_bits}()
functions.
- Created a Kconfig entry for SmartReflex in System type-TI OMAP
Implementations menu.
Where can i get the development version of zlib? but its is not
discussed in the tutorial.
On Sun, Jun 1, 2008 at 2:59 PM, Felipe Balbi [EMAIL PROTECTED] wrote:
On Sun, 1 Jun 2008 11:55:11 +0530, mohammed shareef [EMAIL PROTECTED]
wrote:
Hi Felipe,
what is zlib-dev?
as per the tutorials
On Mon, 2 Jun 2008 14:36:06 +0530, mohammed shareef [EMAIL PROTECTED]
wrote:
Where can i get the development version of zlib? but its is not
discussed in the tutorial.
$ apt-cache search zlib dev ;-)
Are you using maemo sdk? If they don't have zlib1g-dev you're gonna have
to rebuild the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 2 jun 2008, om 13:29 heeft Kalle Jokiniemi het volgende geschreven:
Here is an updated version of the SmartReflex driver.
Patches 1 and 2 are same as before, but patch 3 has some new things:
- Changed the register accessing to use the
Hi,
i want to access the omap5912 GPIO pins from user space... like
reading the pin or writing to it from a user space program. is it
possible?
thanx and regards,
Shareef
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More
* [EMAIL PROTECTED] [EMAIL PROTECTED] [080602 01:09]:
Hi,
This patch currently depends on at least one of the PM workaround
patches from Jouni Hogander. Namely this one:
[PATCH 07/10] 34XX: PM: Workaround to check whether any fck is active
before entering sleep
Sorry I think I forgot
On Mon, Jun 02, 2008 at 10:28:02PM +0530, mohammed shareef wrote:
Hi,
i want to access the omap5912 GPIO pins from user space... like
reading the pin or writing to it from a user space program. is it
possible?
Maybe you can use gpio-switch for reading. But for writing, then you
would have
On Mon, Jun 02, 2008 at 11:13:48PM +0530, mohammed shareef wrote:
Hi,
i tried to re-compile my kernel by adding a few features and then
transfered the new image using u-boot. Unfortunately am getting the
following error:
## Booting image at 0010 ...
Bad Magic Number
OMAP5912 OSK #
Hi folks,
I am trying to enable the whole musb HS DMA code on Blackfin. But
found the is no place to clean the DMA interrupt flag in musbhsdma.c.
As a result, the irq always happens with the same DMA irq source. I
add some code to clear the DMA interrupt. Did I miss something here?
After
16 matches
Mail list logo