From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 03/12] arm: boot: update old ARM ID
Date: Fri, 29 Jan 2010 06:36:11 -0800 [thread overview]
Message-ID: <1264775771.5109.44.camel@desktop> (raw)
In-Reply-To: <20100129141647.GB16712@n2100.arm.linux.org.uk>
On Fri, 2010-01-29 at 14:16 +0000, Russell King - ARM Linux wrote:
> On Thu, Jan 28, 2010 at 02:59:28PM -0800, Daniel Walker wrote:
> > >From Steve Muckle's original patch,
> >
> > The mask and ID pattern for older ARM IDs in the kernel
> > decompressor matches the CPU ID for Scorpion, causing the
> > v7 caching routines not to be run and kernel decompression
> > to take significantly longer.
>
> This pathc is actually only half the job - there's other stuff in the
> kernel which would need updating in the same way. I have a fuller
> patch for this which I'll be queuing up for the next merge window
> later today.
Great.. I'll drop this one.
Daniel
prev parent reply other threads:[~2010-01-29 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 22:59 [RFC PATCH 03/12] arm: boot: update old ARM ID Daniel Walker
2010-01-29 14:16 ` Russell King - ARM Linux
2010-01-29 14:36 ` Daniel Walker [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=1264775771.5109.44.camel@desktop \
--to=dwalker@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).