From: Ralf Baechle <ralf@linux-mips.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Bcm47xx: Fix 128MB RAM support
Date: Mon, 22 Feb 2010 21:36:07 +0100 [thread overview]
Message-ID: <20100222203607.GA1548@linux-mips.org> (raw)
In-Reply-To: <4B82E827.8030005@hauke-m.de>
On Mon, Feb 22, 2010 at 09:25:11PM +0100, Hauke Mehrtens wrote:
> > Is this a hardware issue prefetching issue? The kernel should not try
> > CPU prefetch instructions at all on non-coherent CPUs such as the
> > BCM47xx.
>
> This is a hardware issue on the bcm47xx when 128MB ram is present. This
> workaround is out of broadcom's kernel sources and is included in
> OpenWRT for some months. Without this patch the kernel does not even
> print out anything and with this patch it is working.
Thanks!
I was asking to ensure this isn't a workaround for an already solved
kernel software issue. Patch applied,
Ralf
prev parent reply other threads:[~2010-02-22 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 18:51 [PATCH] MIPS: Bcm47xx: Fix 128MB RAM support Hauke Mehrtens
2010-02-22 19:14 ` Ralf Baechle
2010-02-22 20:25 ` Hauke Mehrtens
2010-02-22 20:36 ` Ralf Baechle [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=20100222203607.GA1548@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=hauke@hauke-m.de \
--cc=linux-mips@linux-mips.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