From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "armv7: integrate cache maintenance support" breaks km_kirkwood ethernet
Date: Thu, 28 Jul 2011 15:19:41 +0200 [thread overview]
Message-ID: <4E3161ED.5030109@keymile.com> (raw)
Hi Aneesh,
today I did a rebase of my development branch to current u-boot master. And I
saw on our km_kirkwood board that our egiga0 interface isn't working anymore.
The CPU is a:
SoC: Kirkwood 88F6281_A0
After bisecting the current tree I got:
c2dd0d45540397704de9b13287417d21049d34c6 is the first bad commit
commit c2dd0d45540397704de9b13287417d21049d34c6
Author: Aneesh V <aneesh@ti.com>
Date: Thu Jun 16 23:30:49 2011 +0000
armv7: integrate cache maintenance support
And indeed after reverting this commit on current HEAD my board is usable again.
Any ideas how to fix this problem?
Best regards
Holger Brunck
next reply other threads:[~2011-07-28 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 13:19 Holger Brunck [this message]
2011-07-29 12:33 ` [U-Boot] "armv7: integrate cache maintenance support" breaks km_kirkwood ethernet Wolfgang Denk
2011-07-29 12:51 ` Jason Liu
2011-07-29 16:00 ` Aneesh V
2011-07-29 14:22 ` Aneesh V
2011-07-30 20:38 ` Wolfgang Denk
2011-08-07 15:25 ` Jens Scharsig
2011-08-07 15:25 ` Jens Scharsig
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=4E3161ED.5030109@keymile.com \
--to=holger.brunck@keymile.com \
--cc=u-boot@lists.denx.de \
/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