2011/8/5 Grazvydas Ignotas nota...@gmail.com:
On Thu, Aug 4, 2011 at 1:55 PM, Arno Steffen
arno.stef...@googlemail.com wrote:
While migrating from .33 to .37 kernel I found, that HW-ECC is used by
default.
I found that this is set in omap2.c:
pdata-ecc_opt
While migrating from .33 to .37 kernel I found, that HW-ECC is used by default.
I found that this is set in omap2.c:
pdata-ecc_opt = OMAP_ECC_HAMMING_CODE_HW;
Unfortunatly setting it back to
pdata-ecc_opt = OMAP_ECC_HAMMING_CODE_DEFAULT;
doesn't prevent me from
2011/7/29 Arno Steffen arno.stef...@googlemail.com:
2011/7/29 Tapani Utriainen tap...@technexion.com:
On Thu, 28 Jul 2011 16:18:51 +0200
Arno Steffen arno.stef...@googlemail.com wrote:
That has been good points. I've tried both, but with no result so far.
Try appending earlyprintk
2011/7/29 Tapani Utriainen tap...@technexion.com:
On Thu, 28 Jul 2011 16:18:51 +0200
Arno Steffen arno.stef...@googlemail.com wrote:
That has been good points. I've tried both, but with no result so far.
Try appending earlyprintk=${console} to your bootargs (where ${console}
is your
Maybe you are so kind to give me a hint:
Try to migrate from Kernel 33 to 37. Currently I don't see any message after
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
From what I understand kernel starts with start_kernel()).
What is best way to find out which
rootfstype=jffs2
bootargs_fs1=mem=128M console=ttyO2,115200 noinitrd
root=/dev/mtdblock6 rootfstype=jffs2 debug earlyprintk
- Arno
2011/7/28 Felipe Balbi ba...@ti.com:
On Thu, Jul 28, 2011 at 03:15:20PM +0200, Arno Steffen wrote:
Maybe you are so kind to give me a hint:
Try to migrate from Kernel 33
2011/7/28 Sricharan R r.sricha...@ti.com:
-Original Message-
From: Arno Steffen [mailto:arno.stef...@googlemail.com]
Sent: Thursday, July 28, 2011 9:13 PM
To: Sricharan R
Subject: Re: [Q] No message from Kernel (Howto start debug?)
2011/7/28 Arno Steffen arno.stef...@googlemail.com:
2011
Currently I am using 2.6.33 on an OMAP3. I would change from a 600MHz
Omap35xx to a pincompatible 1GHz AM37xx. Where is to change the clock
frequencies/dividers?
Is it done in x-loader, uboot or in kernel itself (and if so where?).
Are there other Software-issued to take care in this migration?
Signed-off-by: Arno Steffen arno.stef...@googlemail.com
---
arch/arm/mach-omap2/control.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/control.h b/arch/arm/mach-omap2/control.h
index b6c6b7c..5325297 100644
--- a/arch/arm/mach-omap2/control.h
+++ b
There is a copy/paste bug in arch/arm/plat-omaop/include/control:
Please replace:
#define OMAP3_IVA_MASK (1 OMAP3_SGX_SHIFT)
by:
#define OMAP3_IVA_MASK (1 OMAP3_IVA_SHIFT)
Best regards
Arno
--
To unsubscribe from this list: send the line unsubscribe
The setting NAND_NO_SUBPAGE_WRITE in omap_nand_platform_data is not used.
I am using SLC NAND - MT29F1G16ABC , which seems not to support subpages.
I can observe that kernel allows sub-page-writes.
I tried to find out what is happend with the options, but after a
while I get lost in numerous
Adding debug to bootargs
( Kernel command line: mem=128M console=ttyS2,115200n8 noinitrd
root=/dev/mtdblock6 rw rootfstype=jffs2 debug
ip=192.168.90.101:192.168.90.230:192.168.90.1:255.255.255.0::eth0:on
mac=00:19:6f:cc:cc:dd )
doesn't change the output. Do I need a recompile with some kernel
I do have some messages while booting a 2.6.33 kernel:
What does this mean? How can I get rid of it?
What is omap3_clk_lock_dpll5() doing and what if I comment it out? I
guess it make some sense ;)
Clocking rate (Crystal/Core/MPU): 12.0/332/550 MHz
[ cut here ]
WARNING:
Reprogramming SDRC clock to 26600 Hz
dpll3_m2_clk rate change failed: -22
Why I cant't let it run only on 322 MHz?
For this I could found an answer.
There is no entry for this frequency in
omap_sdrc_params mt46h32m32lf6_sdrc_params
(in arch/arm/mach-omap2/sdram-micron )
--
To
2010/7/16 Gadiyar, Anand gadi...@ti.com:
Arno Steffen wrote:
I do have some messages while booting a 2.6.33 kernel:
What does this mean? How can I get rid of it?
What is omap3_clk_lock_dpll5() doing and what if I comment it out? I
guess it make some sense ;)
Not sure why you have
While doing powercycles with an OMAP3 board I got several strange
effects on my board.
So even when mounting the root-partiton as read only ( ... noinitrd
root=/dev/mtdblock6 ro rootfstype=jffs2 ... ) I 've got sometimes (1
in a 100 trials) a bunch of message while mounting:
Just tested the kernel 2.6.33 on a EVM board and missed the flash
partitions. Is this intended?
--
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
Tested 2.6.33 kernel with the EVM board (uboot2010-03rc2).
What I observed is, that MAC address shown and used in linux while
booting, is completly different from that one in uboot.
Do I have to handover the MAC as a commandline parameter? If so, what
are the magic params?
Regards
Arno
--
To
2010/2/8 Paul Walmsley p...@pwsan.com:
On Mon, 8 Feb 2010, Arno Steffen wrote:
Thanks Paul for your help.
Switch on the #define DEBUG in this both files skip almost all
kernel boot messages before this warning and gives just this: !?!
You probably need to enable CONFIG_DEBUG_LL to see all
, Arno Steffen wrote:
I am trying to migrate from kernel 28 to 32 on TI OMA3. Our board is
derived from EVM board.
...
Also I do get this warning now while boot:
Hierarchical RCU implementation.
NR_IRQS:368
Clocking rate (Crystal/Core/MPU): 12.0/332/500 MHz
I don't have an 3530 EVM here
I am trying to migrate from kernel 28 to 32 on TI OMA3. Our board is
derived from EVM board.
In new kernel I can't see the partitions in flash, and found no file
to set them.
Also I do get this warning now while boot:
Hierarchical RCU implementation.
NR_IRQS:368
Clocking rate
21 matches
Mail list logo
