From: alex@gai.ru (Alexander Sverdlin)
To: linux-arm-kernel@lists.infradead.org
Subject: Is ep93xx support broken in linux-next?
Date: Tue, 26 Oct 2010 18:48:44 +0400 [thread overview]
Message-ID: <1288104524.2098.30.camel@r60e> (raw)
In-Reply-To: <20101026132235.GD15333@gw.healthdatacare.com>
On Tue, 2010-10-26 at 16:22 +0300, Mika Westerberg wrote:
> > > > +ENTRY(fa_flush_icache_all)
> > > > + mov r0, #0
> > > > + mcr p15, 0, ip, c7, c5, 0 @ invalidate I cache
> > >
> > > Obviously the register should be r0 instead of ip.
> >
> > Only one occurrence should be changed?
>
> No, all of them. But with ep93xx you can just change it
> from arm920_flush_icache_all().
It makes linux-next-20101025 work fine for EDB9302-based board.
But there seems to be another issue with linux-next-20101026, some
problem with RedBoot partition handling...
Alexander.
next prev parent reply other threads:[~2010-10-26 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 11:56 Is ep93xx support broken in linux-next? Alexander Sverdlin
2010-10-26 12:50 ` Mika Westerberg
2010-10-26 12:58 ` Mika Westerberg
2010-10-26 13:20 ` Alexander Sverdlin
2010-10-26 13:22 ` Mika Westerberg
2010-10-26 14:48 ` Alexander Sverdlin [this message]
2010-10-27 20:20 ` Russell King - ARM Linux
2010-10-28 7:32 ` Mika Westerberg
2010-10-28 9:22 ` Russell King - ARM Linux
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=1288104524.2098.30.camel@r60e \
--to=alex@gai.ru \
--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