From: bill_carson@126.com (rocky)
To: linux-arm-kernel@lists.infradead.org
Subject: Query about arch/arm/boot/compressed/Makefile.debug
Date: Thu, 3 Jun 2010 13:55:42 +0800 (CST) [thread overview]
Message-ID: <13ff02f.5b3c.128fc611d48.Coremail.bill_carson@126.com> (raw)
In-Reply-To: <AANLkTinEA_7sFG9WqzETirCY76XIIeicKe3Cw9eQvYwx@mail.gmail.com>
Hi, Eric
>Conduct?a?strict?memory?checking?and?check?the?cache?enabling?code,?normally
>that's?where?the?problem?is.?The?decompressor?itself,?should?be?less?problematic
>since?it's?working?elsewhere?on?most?other?platforms.
All ARM1176 based SoC share the same cache enable/disable API which defined in arch/arm/boot/compressed/head.S, ARM1176 falls into ARMv7 .
Actually, our DDR run at 800MHz, I'm trying to tune it a little bit lower at 533MHz to see what happened.
thanks for your kind tips.
rocky
?2010-06-03?13:47:00?"Eric?Miao"?<eric.y.miao@gmail.com>????>On?Thu,?Jun?3,?2010?at?1:39?PM,?rocky?<bill_carson@126.com>?wrote:>>?Hi,?all>>?I'm?porting?Linux?to?a?ARM1176?based?SOC,?sometimes?after?running?make?zImage,>>?I?got?CRC?error?when?uncompressing?the?kernel?all?the?time.>>Conduct?a?strict?memory?checking?and?check?the?cache?enabling?code,?normally>that's?where?the?problem?is.?The?decompressor?itself,?should?be?less?problematic>since?it's?working?elsewhere?on?most?other?platforms.>>>>>?no?idea?why?this?should?happened,?i?want?to?use?misc.c?with?STANDALONE_DEBUG?mode,>>?so?how?should?i?use?this?debug?mode?>>>>>>?thanks>>?BR>>?rocky>>>>>>>>?_______________________________________________>>?linux-arm-kernel?mailing?list>>?linux-arm-kernel at lists.infradead.org>>?http://lists.infradead.org/mailman/listinfo/linux-arm-kernel>>
prev parent reply other threads:[~2010-06-03 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 5:39 Query about arch/arm/boot/compressed/Makefile.debug rocky
2010-06-03 5:47 ` Eric Miao
2010-06-03 5:55 ` rocky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13ff02f.5b3c.128fc611d48.Coremail.bill_carson@126.com \
--to=bill_carson@126.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox