Re: [RFC] Initial attempt to make ARM use LMB
On Sat, Apr 10, 2010 at 09:12:24AM +0530, Rabin Vincent wrote: > On Fri, Apr 09, 2010 at 12:11:05PM +0100, Russell King - ARM Linux wrote: > > Here's a revised version which should resolve the initrd problem. > > It does, after the missing call to lmb_init() is added. Which missing call? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC] Initial attempt to make ARM use LMB
On Sat, Apr 10, 2010 at 08:03:05AM +0100, Russell King - ARM Linux wrote:
> On Sat, Apr 10, 2010 at 09:12:24AM +0530, Rabin Vincent wrote:
> > On Fri, Apr 09, 2010 at 12:11:05PM +0100, Russell King - ARM Linux wrote:
> > > Here's a revised version which should resolve the initrd problem.
> >
> > It does, after the missing call to lmb_init() is added.
>
> Which missing call?
This one:
diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
index bc341c4..f1e0f5d 100644
--- a/arch/arm/mm/init.c
+++ b/arch/arm/mm/init.c
@@ -279,6 +279,7 @@ void __init arm_lmb_init(struct meminfo *mi, struct
machine_desc *mdesc)
{
int i;
+ lmb_init();
for (i = 0; i < mi->nr_banks; i++)
lmb_add(mi->bank[i].start, mi->bank[i].size);
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP35xx Boot failure
Hi, first of all, please read http://elinux.org/Netiquette On Fri, Apr 09, 2010 at 08:33:20AM -0700, Jerry Johns wrote: > Hello all, I've got a custom OMAP3503 board with 256Mbytes of > LPDDR memory (single die, x32-bit) that i've got working with x-loader > and u- boot. However, when i load the Linux kernel (2.6.32 git), it > randomly produces the following errors: > > 1) Hangs midway through the "Uncompressing Linux " stage, and > this is arbitrary and random on different attempts 2) If it ever does > go through, it sometimes displays "invalid compressed format (err = > 2)" or "crc error", "incomplete literal tree" and says "System > halted" 3) If i disable caching in the kernel (in > arch/arm/boot/compressed.S, line 233 "bl cache_on"), it at least > completes the Uncompressing stage fine and proceeds to print "... > done, booting the kernel.", at which point it does not boot (most > likely since i disabled the caching) 4) If i reset the board (not > power-cycle) after the board hang above, and do a crc32 check on the > kernel image in DDR memory (this is possible since DDR2 memory > contents do not get changed after a soft- reset), it matches the CRC32 > that i have calculated manually on the kernel image. This shows that > the main kernel image (from which it is uncompressed) is still > intact. could it be memory timings ?? One thing you might wanna do is enable CONFIG_DEBUG_LL and CONFIG_EARLY_PRINTK and append "debug earlyprintk" to your CMDLINE this might give your more information about the problem. -- balbi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] omap: Add I2C bus 1 initialisation for OMAP2430
>On Tue, Apr 06, 2010 at 08:23:33AM +0200, ext Viral Mehta wrote: >>Initialize isp1301 FS USB transceiver and >>add I2C bus1 initialization code for OMAP2430 >> >>Signed-off-by: Viral Mehta >this should go through linux-omap should be resent to linux-omap in that case ? If so, I will do that. -- Viral This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. __ -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
