[PATCH 6/10] ARM: OMAP3: Rename cm_regbits_34xx.h to cm-regbits-34xx.h
Rename cm_regbits_34xx.h to cm-regbits-34xx.h Signed-off-by: Tony Lindgren [EMAIL PROTECTED] --- arch/arm/mach-omap2/clock.c |2 +- arch/arm/mach-omap2/clock34xx.c |2 +- arch/arm/mach-omap2/clock34xx.h |2 +- arch/arm/mach-omap2/cm-regbits-34xx.h | 667 + arch/arm/mach-omap2/cm_regbits_34xx.h | 667 - drivers/usb/host/ehci-omap.h |2 +- 6 files changed, 671 insertions(+), 671 deletions(-) create mode 100644 arch/arm/mach-omap2/cm-regbits-34xx.h delete mode 100644 arch/arm/mach-omap2/cm_regbits_34xx.h diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c index 3f41144..3f107d4 100644 --- a/arch/arm/mach-omap2/clock.c +++ b/arch/arm/mach-omap2/clock.c @@ -43,7 +43,7 @@ #include prm_regbits_24xx.h #include cm.h #include cm-regbits-24xx.h -#include cm_regbits_34xx.h +#include cm-regbits-34xx.h #define MAX_CLOCK_ENABLE_WAIT 10 diff --git a/arch/arm/mach-omap2/clock34xx.c b/arch/arm/mach-omap2/clock34xx.c index 2558a23..616e071 100644 --- a/arch/arm/mach-omap2/clock34xx.c +++ b/arch/arm/mach-omap2/clock34xx.c @@ -35,7 +35,7 @@ #include prm.h #include prm_regbits_34xx.h #include cm.h -#include cm_regbits_34xx.h +#include cm-regbits-34xx.h /* CM_CLKEN_PLL*.EN* bit values */ #define DPLL_LOCKED0x7 diff --git a/arch/arm/mach-omap2/clock34xx.h b/arch/arm/mach-omap2/clock34xx.h index 99cb536..9f61352 100644 --- a/arch/arm/mach-omap2/clock34xx.h +++ b/arch/arm/mach-omap2/clock34xx.h @@ -14,7 +14,7 @@ #include clock.h #include cm.h -#include cm_regbits_34xx.h +#include cm-regbits-34xx.h #include prm.h #include prm_regbits_34xx.h diff --git a/arch/arm/mach-omap2/cm-regbits-34xx.h b/arch/arm/mach-omap2/cm-regbits-34xx.h new file mode 100644 index 000..fcb7c12 --- /dev/null +++ b/arch/arm/mach-omap2/cm-regbits-34xx.h @@ -0,0 +1,667 @@ +#ifndef __ARCH_ARM_MACH_OMAP2_CM_REGBITS_34XX_H +#define __ARCH_ARM_MACH_OMAP2_CM_REGBITS_34XX_H + +/* + * OMAP3430 Clock Management register bits + * + * Copyright (C) 2007-2008 Texas Instruments, Inc. + * Copyright (C) 2007-2008 Nokia Corporation + * + * Written by Paul Walmsley + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ + +#include cm.h + +/* Bits shared between registers */ + +/* CM_FCLKEN1_CORE and CM_ICLKEN1_CORE shared bits */ +#define OMAP3430ES2_EN_MMC3_MASK (1 30) +#define OMAP3430ES2_EN_MMC3_SHIFT 30 +#define OMAP3430_EN_MSPRO (1 23) +#define OMAP3430_EN_MSPRO_SHIFT23 +#define OMAP3430_EN_HDQ(1 22) +#define OMAP3430_EN_HDQ_SHIFT 22 +#define OMAP3430ES1_EN_FSHOSTUSB (1 5) +#define OMAP3430ES1_EN_FSHOSTUSB_SHIFT 5 +#define OMAP3430ES1_EN_D2D (1 3) +#define OMAP3430ES1_EN_D2D_SHIFT 3 +#define OMAP3430_EN_SSI(1 0) +#define OMAP3430_EN_SSI_SHIFT 0 + +/* CM_FCLKEN3_CORE and CM_ICLKEN3_CORE shared bits */ +#define OMAP3430ES2_EN_USBTLL_SHIFT2 +#define OMAP3430ES2_EN_USBTLL_MASK (1 2) + +/* CM_FCLKEN_WKUP and CM_ICLKEN_WKUP shared bits */ +#define OMAP3430_EN_WDT2 (1 5) +#define OMAP3430_EN_WDT2_SHIFT 5 + +/* CM_ICLKEN_CAM, CM_FCLKEN_CAM shared bits */ +#define OMAP3430_EN_CAM(1 0) +#define OMAP3430_EN_CAM_SHIFT 0 + +/* CM_FCLKEN_PER, CM_ICLKEN_PER shared bits */ +#define OMAP3430_EN_WDT3 (1 12) +#define OMAP3430_EN_WDT3_SHIFT 12 + +/* CM_CLKSEL2_EMU, CM_CLKSEL3_EMU shared bits */ +#define OMAP3430_OVERRIDE_ENABLE (1 19) + + +/* Bits specific to each register */ + +/* CM_FCLKEN_IVA2 */ +#define OMAP3430_CM_FCLKEN_IVA2_EN_IVA2(1 0) + +/* CM_CLKEN_PLL_IVA2 */ +#define OMAP3430_IVA2_DPLL_RAMPTIME_SHIFT 8 +#define OMAP3430_IVA2_DPLL_RAMPTIME_MASK (0x3 8) +#define OMAP3430_IVA2_DPLL_FREQSEL_SHIFT 4 +#define OMAP3430_IVA2_DPLL_FREQSEL_MASK(0xf 4) +#define OMAP3430_EN_IVA2_DPLL_DRIFTGUARD_SHIFT 3 +#define OMAP3430_EN_IVA2_DPLL_DRIFTGUARD_MASK (1 3) +#define OMAP3430_EN_IVA2_DPLL_SHIFT0 +#define OMAP3430_EN_IVA2_DPLL_MASK (0x7 0) + +/* CM_IDLEST_IVA2 */ +#define OMAP3430_ST_IVA2 (1 0) + +/* CM_IDLEST_PLL_IVA2 */ +#define OMAP3430_ST_IVA2_CLK (1 0) + +/* CM_AUTOIDLE_PLL_IVA2 */ +#define
[PATCH 8/10] ARM: OMAP2: Rename prm_regbits_24xx.h to prm-regbits-24xx.h
Rename prm_regbits_24xx.h to prm-regbits-24xx.h Signed-off-by: Tony Lindgren [EMAIL PROTECTED] --- arch/arm/mach-omap2/clock.c|2 +- arch/arm/mach-omap2/clock24xx.c|2 +- arch/arm/mach-omap2/clock24xx.h|2 +- arch/arm/mach-omap2/pm.c |2 +- arch/arm/mach-omap2/prcm.c |2 +- arch/arm/mach-omap2/prm-regbits-24xx.h | 279 arch/arm/mach-omap2/prm_regbits_24xx.h | 279 drivers/dsp/dspgateway/dsp.h |2 +- 8 files changed, 285 insertions(+), 285 deletions(-) create mode 100644 arch/arm/mach-omap2/prm-regbits-24xx.h delete mode 100644 arch/arm/mach-omap2/prm_regbits_24xx.h diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c index 3f107d4..5cf88b7 100644 --- a/arch/arm/mach-omap2/clock.c +++ b/arch/arm/mach-omap2/clock.c @@ -40,7 +40,7 @@ #include sdrc.h #include clock.h #include prm.h -#include prm_regbits_24xx.h +#include prm-regbits-24xx.h #include cm.h #include cm-regbits-24xx.h #include cm-regbits-34xx.h diff --git a/arch/arm/mach-omap2/clock24xx.c b/arch/arm/mach-omap2/clock24xx.c index e8d0fe3..35a255d 100644 --- a/arch/arm/mach-omap2/clock24xx.c +++ b/arch/arm/mach-omap2/clock24xx.c @@ -36,7 +36,7 @@ #include clock.h #include clock24xx.h #include prm.h -#include prm_regbits_24xx.h +#include prm-regbits-24xx.h #include cm.h #include cm-regbits-24xx.h diff --git a/arch/arm/mach-omap2/clock24xx.h b/arch/arm/mach-omap2/clock24xx.h index 2b4a6a6..be95bf7 100644 --- a/arch/arm/mach-omap2/clock24xx.h +++ b/arch/arm/mach-omap2/clock24xx.h @@ -25,7 +25,7 @@ #include prm.h #include cm.h -#include prm_regbits_24xx.h +#include prm-regbits-24xx.h #include cm-regbits-24xx.h #include sdrc.h diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c index 095b910..3a455e8 100644 --- a/arch/arm/mach-omap2/pm.c +++ b/arch/arm/mach-omap2/pm.c @@ -47,7 +47,7 @@ #include asm/arch/board.h #include prm.h -#include prm_regbits_24xx.h +#include prm-regbits-24xx.h #include cm.h #include cm-regbits-24xx.h #include sdrc.h diff --git a/arch/arm/mach-omap2/prcm.c b/arch/arm/mach-omap2/prcm.c index 9857ba7..9ff918a 100644 --- a/arch/arm/mach-omap2/prcm.c +++ b/arch/arm/mach-omap2/prcm.c @@ -18,7 +18,7 @@ #include linux/clk.h #include prm.h -#include prm_regbits_24xx.h +#include prm-regbits-24xx.h extern void omap2_clk_prepare_for_reboot(void); diff --git a/arch/arm/mach-omap2/prm-regbits-24xx.h b/arch/arm/mach-omap2/prm-regbits-24xx.h new file mode 100644 index 000..c6d17a3 --- /dev/null +++ b/arch/arm/mach-omap2/prm-regbits-24xx.h @@ -0,0 +1,279 @@ +#ifndef __ARCH_ARM_MACH_OMAP2_PRM_REGBITS_24XX_H +#define __ARCH_ARM_MACH_OMAP2_PRM_REGBITS_24XX_H + +/* + * OMAP24XX Power/Reset Management register bits + * + * Copyright (C) 2007 Texas Instruments, Inc. + * Copyright (C) 2007 Nokia Corporation + * + * Written by Paul Walmsley + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ + +#include prm.h + +/* Bits shared between registers */ + +/* PRCM_IRQSTATUS_MPU, PM_IRQSTATUS_DSP, PRCM_IRQSTATUS_IVA shared bits */ +#define OMAP24XX_VOLTTRANS_ST (1 2) +#define OMAP24XX_WKUP2_ST (1 1) +#define OMAP24XX_WKUP1_ST (1 0) + +/* PRCM_IRQENABLE_MPU, PM_IRQENABLE_DSP, PRCM_IRQENABLE_IVA shared bits */ +#define OMAP24XX_VOLTTRANS_EN (1 2) +#define OMAP24XX_WKUP2_EN (1 1) +#define OMAP24XX_WKUP1_EN (1 0) + +/* PM_WKDEP_GFX, PM_WKDEP_MPU, PM_WKDEP_DSP, PM_WKDEP_MDM shared bits */ +#define OMAP24XX_EN_MPU(1 1) +#define OMAP24XX_EN_CORE (1 0) + +/* + * PM_PWSTCTRL_MPU, PM_PWSTCTRL_GFX, PM_PWSTCTRL_DSP, PM_PWSTCTRL_MDM + * shared bits + */ +#define OMAP24XX_MEMONSTATE_SHIFT 10 +#define OMAP24XX_MEMONSTATE_MASK (0x3 10) +#define OMAP24XX_MEMRETSTATE (1 3) + +/* PM_PWSTCTRL_GFX, PM_PWSTCTRL_DSP, PM_PWSTCTRL_MDM shared bits */ +#define OMAP24XX_FORCESTATE(1 18) + +/* + * PM_PWSTST_CORE, PM_PWSTST_GFX, PM_PWSTST_MPU, PM_PWSTST_DSP, + * PM_PWSTST_MDM shared bits + */ +#define OMAP24XX_CLKACTIVITY (1 19) + +/* PM_PWSTST_MPU, PM_PWSTST_CORE, PM_PWSTST_DSP shared bits */ +#define OMAP24XX_LASTSTATEENTERED_SHIFT4 +#define OMAP24XX_LASTSTATEENTERED_MASK (0x3 4) + +/* PM_PWSTST_MPU and PM_PWSTST_DSP shared bits */ +#define OMAP2430_MEMSTATEST_SHIFT 10 +#define OMAP2430_MEMSTATEST_MASK (0x3 10) + +/* PM_PWSTST_GFX, PM_PWSTST_DSP, PM_PWSTST_MDM shared bits
isp1301 build breakage
CC drivers/i2c/chips/isp1301_omap.o drivers/i2c/chips/isp1301_omap.c: In function 'isp1301_set_peripheral': drivers/i2c/chips/isp1301_omap.c:1360: error: implicit declaration of function 'machine_is_omap_h2' drivers/i2c/chips/isp1301_omap.c:1360: error: implicit declaration of function 'machine_is_omap_h3' make[3]: *** [drivers/i2c/chips/isp1301_omap.o] Error 1 make[2]: *** [drivers/i2c/chips] Error 2 make[1]: *** [drivers/i2c] Error 2 This is on an H4 config, if that matters at all. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: isp1301 build breakage
* David Brownell [EMAIL PROTECTED] [080312 13:28]: CC drivers/i2c/chips/isp1301_omap.o drivers/i2c/chips/isp1301_omap.c: In function 'isp1301_set_peripheral': drivers/i2c/chips/isp1301_omap.c:1360: error: implicit declaration of function 'machine_is_omap_h2' drivers/i2c/chips/isp1301_omap.c:1360: error: implicit declaration of function 'machine_is_omap_h3' make[3]: *** [drivers/i2c/chips/isp1301_omap.o] Error 1 make[2]: *** [drivers/i2c/chips] Error 2 make[1]: *** [drivers/i2c] Error 2 This is on an H4 config, if that matters at all. I've pushed a quick fix to include mach-types.h.. In the long run that should use platform_data for passing any special options.. Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
OMAP5910 I2C problem
Hi! I've experienced problem with OMAP5910 I2C driver in my custom board. It freezes after some working time. When it freezes, register I2C_STAT show that XUDF (or ROVR) bit is set and SCL pin is in low state. I2C_CNT register is not zero too, but buf_len counter is zero. Attempt to use init() function do not help in this situation. Only things I can do with it - set I2C to debug mode and make some SCL clocks by hand. After this I2C state machine can work for some time. When I2C clock is set to 100kHz it happens almost in every transfer - I try to read/write EEPROM. In 20kHz it still can happen too (on heavy load much frequently). It's look like internal I2C state machine is broken. So, for now I replace i2c algorithm with i2c_algo_bit and everything works fine. I'm curious - only I have such a problem with I2C bus in OMAP 5910 or someone else too? May be there is better solution? With regards Oleg Kechin. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] I2C: Fix OMAP I2C status register handling in IRQ processing
The IRQ handler in omap-i2c.c can sometimes clear status bits without
actually processing them. In particular, error status bits will be
ignored if any of the ARDY, RRDY, RDR, XRDY, or XDR bits are
concurrently set.
Signed-off-by: Seth Forshee [EMAIL PROTECTED]
---
More information:
I originally noticed this problem on a custom 2430 board I am working
with. Whenever an i2c chip driver calls i2c_probe() the device would
be found on both i2c busses at each of the possible addresses for the
device. I discovered that NACK was being set in the status register
but omap_i2c_xfer() still returned success because ARDY was also set.
This patch fixes this issue on my board and hasn't caused any problems
(in my admittedly light i2c usage). I don't have immediate access to
an SDP board however, so it has not been tested on that platform.
drivers/i2c/busses/i2c-omap.c | 28 +---
1 files changed, 13 insertions(+), 15 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 4777466..a16d513 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -590,7 +590,7 @@ omap_i2c_isr(int this_irq, void *dev_id)
struct omap_i2c_dev *dev = dev_id;
u16 bits;
u16 stat, w;
- int count = 0;
+ int err, count = 0;
if (dev-idle)
return IRQ_NONE;
@@ -605,10 +605,19 @@ omap_i2c_isr(int this_irq, void *dev_id)
omap_i2c_write_reg(dev, OMAP_I2C_STAT_REG, stat);
- if (stat OMAP_I2C_STAT_ARDY) {
- omap_i2c_complete_cmd(dev, 0);
- continue;
+ err = 0;
+ if (stat OMAP_I2C_STAT_NACK) {
+ err |= OMAP_I2C_STAT_NACK;
+ omap_i2c_write_reg(dev, OMAP_I2C_CON_REG,
+ OMAP_I2C_CON_STP);
}
+ if (stat OMAP_I2C_STAT_AL) {
+ dev_err(dev-dev, Arbitration lost\n);
+ err |= OMAP_I2C_STAT_AL;
+ }
+ if (stat (OMAP_I2C_STAT_ARDY | OMAP_I2C_STAT_NACK |
+ OMAP_I2C_STAT_AL))
+ omap_i2c_complete_cmd(dev, err);
if (stat (OMAP_I2C_STAT_RRDY | OMAP_I2C_STAT_RDR)) {
u8 num_bytes = 1;
if (dev-fifo_size) {
@@ -640,7 +649,6 @@ omap_i2c_isr(int this_irq, void *dev_id)
}
}
omap_i2c_ack_stat(dev, stat (OMAP_I2C_STAT_RRDY |
OMAP_I2C_STAT_RDR));
- continue;
}
if (stat (OMAP_I2C_STAT_XRDY | OMAP_I2C_STAT_XDR)) {
u8 num_bytes = 1;
@@ -674,7 +682,6 @@ omap_i2c_isr(int this_irq, void *dev_id)
omap_i2c_write_reg(dev, OMAP_I2C_DATA_REG, w);
}
omap_i2c_ack_stat(dev, stat (OMAP_I2C_STAT_XRDY |
OMAP_I2C_STAT_XDR));
- continue;
}
if (stat OMAP_I2C_STAT_ROVR) {
dev_err(dev-dev, Receive overrun\n);
@@ -684,15 +691,6 @@ omap_i2c_isr(int this_irq, void *dev_id)
dev_err(dev-dev, Transmit overflow\n);
dev-cmd_err |= OMAP_I2C_STAT_XUDF;
}
- if (stat OMAP_I2C_STAT_NACK) {
- omap_i2c_complete_cmd(dev, OMAP_I2C_STAT_NACK);
- omap_i2c_write_reg(dev, OMAP_I2C_CON_REG,
- OMAP_I2C_CON_STP);
- }
- if (stat OMAP_I2C_STAT_AL) {
- dev_err(dev-dev, Arbitration lost\n);
- omap_i2c_complete_cmd(dev, OMAP_I2C_STAT_AL);
- }
}
return count ? IRQ_HANDLED : IRQ_NONE;
--
1.5.2.5
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] I2C: Fix OMAP I2C status register handling in IRQ processing
On Wed, Mar 12, 2008 at 01:14:32PM -0500, Felipe Balbi wrote: - int count = 0; + int err, count = 0; int err = 0, count = 0; will be better and you avoid that err=0 before using err right below. No, the err = 0 I added is in a while loop. It needs to be reinitialized for each iteration. + if (stat (OMAP_I2C_STAT_ARDY | OMAP_I2C_STAT_NACK | + OMAP_I2C_STAT_AL)) err should already hold them, how about if (stat err) err will not hold ARDY, so it would need to be if (stat (err | OMAP_I2C_STAT_ARDY)) But I don't see the advantage. Comparing the assembly, what I submitted generates one less instruction than the above, so the difference appears to be trivial. Cheers, Seth -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MTD partitions
Thanks, David, I added the MTD partition information to board-($MYBOARD).c, But kernel didn't show any MTD partition information during booting. If I have to create the MTD partitions using MTD commands in u-boot first? My u-boot is old, no MTD support, if that's the case, I'll port the newer u-boot, then try again. Thanks. On Wed, Mar 12, 2008 at 6:16 PM, David Brownell [EMAIL PROTECTED] wrote: On Wednesday 12 March 2008, Tim Chen wrote: What file should I add MTD partitions information to? Files in arch/arm/mach-omap1/ or drivers/mtd/maps? Platform data in .../mach-omap1/board-$(MYBOARD).c should give default partition data to the relevant NAND driver. - Dave -- -- Regards, Tim. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Re: Android on OMAP
Hi, Android is up and running on Mistral's OSK2530 EVM (based on OMAP2430 SoC). We got the HW keypad functional for Android and we are able to execute the the default applications shipped along with the m5-rc14 sdk. The next thing would be to get the touchscreen and networking functional on this platform. Thank you very much for your support and encouragement. Warm Regards, Anil On Fri, Mar 7, 2008 at 7:23 PM, Anil Sasidharan [EMAIL PROTECTED] wrote: Hi Raymond, I remember you having reported an error with regards to vmalloc when binder tries to perform mmap. Could you get rid of this problem? I was able to resolve my board hang issue. The issue was due to some conflict between the device nodes for alarm and eac (audio device). Now I'm able to bring up android without stracing and also the binder module is functional now. However the Android home screen pops up a message com.google.googleapps not responding and the android framework stops responding to the HW keyboard events. All I can see is couple of message for wakeup and sleep from power module. Sometimes when I press the enter key on the HW keyboard, I do see that the binder module tries to do mmap and fails with vmalloc error simliar to what you had observed. The platform on which this is being tried has got 128MB of RAM and the rootfs is currently mounted from an NFS server. cat /proc/meminfo command executed before launching Android shows the following output: MemTotal: 126680 kB MemFree:122616 kB Buffers: 0 kB Cached: 1788 kB SwapCached: 0 kB Active:624 kB Inactive: 1280 kB SwapTotal: 0 kB SwapFree:0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 128 kB Mapped:300 kB Slab: 1224 kB SReclaimable: 408 kB SUnreclaim:816 kB PageTables: 44 kB NFS_Unstable:0 kB Bounce: 0 kB CommitLimit: 63340 kB Committed_AS: 1504 kB VmallocTotal: 122880 kB VmallocUsed: 65864 kB VmallocChunk:49148 kB What may be the reason for this vmalloc failure? Warm Regards, Anil On Mon, Mar 3, 2008 at 6:42 AM, colorant [EMAIL PROTECTED] wrote: 1. If the /dev/binder device node is missing or having wrong minor number, the android display comes up properly. 2. If the /dev/binder device node is created properly by making use of the information from the /proc/misc, then the /system/bin/runtime spits out the following messages and then hangs for ever. binder_open: 276:276 binder_mmap: 276 4000-4040 (4096 K) vma 71 pagep 5f binder_open: 278:278 binder_mmap: 278 42648000-42a48000 (4096 K) vma 71 pagep 5f In fact the whole system hangs :-( Currently my platform on which this whole activity is being carried out has only 64MB RAM and I presume the mmap calls may be failing due to some memory crunch. It would be great if you could share your thoughts on the above given observations. Warm Regards, Anil Hi Anil I guess there still is some thing we don't handle well in the vmalloc related functions. My output messages after the first two binder_mmap is a binder_flush as following: binder_open: 500:500 binder_mmap: 500 40008000-40408000 (4096 K) vma 71 pagep 5f binder_open: 510:510 binder_mmap: 510 4265-42a5 (4096 K) vma 71 pagep 5f binder_flush: 510 woke 3 threads binder_open: 537:537 binder_mmap: 537 4265-42a5 (4096 K) vma 71 pagep 5f And three more mmap later, the main screen is shown. However I also got a mmap fail : binder_open: 552:552 binder_mmap: 552 4265-42a5 (4096 K) vma 71 pagep 5f binder_open: 554:554 binder_mmap: 554 4265-42a5 (4096 K) vma 71 pagep 5f binder_open: 498:507 binder_mmap: 498 40108000-40508000 (4096 K) vma 71 pagep 5f allocation failed: out of vmalloc space - use vmalloc=size to increase size. binder_mmap: 498 40108000-40508000 get_vm_area failed -12 And I remember that I had to modify some vmalloc related functions to make the binder driver working happy with my 2.6.21 kernel. I think there might be something I miss to modify which is changed from 2.6.21 kernel to 2.6.23 kernel but can be compiled without problem. However, since I just want to verify the possiblility of porting the android to my platform and don't want to really make it perfect for now, So I don't want to study further at this point, I will just wait until the whole system's src is available so that the problem hunting job is more easy to do. And , Just my guess, It might be helpful to read the emulator's src code ? Since the goldfish is base on it, and I can
Re: Re: Android on OMAP
Hi, Android is up and running on Mistral's OSK2530 EVM (based on OMAP2430 SoC). We got the HW keypad functional for Android and we are able to execute the the default applications shipped along with the m5-rc14 sdk. The next thing would be to get the touchscreen and networking functional on this platform. Thank you very much for your support and encouragement. Warm Regards, Anil -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
