From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Reading twd_base at run-time
Date: Wed, 01 Apr 2015 14:47:41 +0200 [thread overview]
Message-ID: <551BE8ED.40308@free.fr> (raw)
In-Reply-To: <20150401121213.GC24899@n2100.arm.linux.org.uk>
On 01/04/2015 14:12, Russell King - ARM Linux wrote:
> On Wed, Apr 01, 2015 at 02:07:05PM +0200, Mason wrote:
>
> I'm sorry, it's not that I don't believe you, it's that ARM Ltd
> employees already have evidence to the contrary, and they should know
> what's possible, they (as a company) designed the hardware and they're
> the ones who have to deal with queries from _all_ the silicon vendors.
> They get to know what the entire ARM ecosystem is doing, what vendors
> get wrong, etc. They're in a far better position than just one silicon
> vendor to know what's possible and what isn't.
(Disclaimer: I am not a HW engineer.) It seems the above reasoning is
based on a false dichotomy. I assume that the "wiring" of PERIPH_BASE
to CP15 is left up to the implementor. Maybe some implementors just
copy a value, while others wire the actual value?
> So when Mark says something has been seen, I believe him, and that
> trumps what hardware engineers at individual silicon vendors claim.
o_O ?? I have never disputed Marc's evidence.
> And what about the cases where it is possible to probe the hardware on
> some platforms but doing so crashes the kernel on others? I guess you
> don't care about anything but your own platform - that's the kind of
> message you're putting out...
Why would I post patches here if all I cared about was my own platform?
Anyway, I do feel a lot of animosity, and I apologize if some of my
messages have offended you or others here. Perhaps if you could point
out the offending comments, I could adjust in the future?
Regards.
next prev parent reply other threads:[~2015-04-01 12:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 16:16 Reading twd_base at run-time Mason
2015-03-27 16:35 ` Marc Zyngier
2015-03-27 20:33 ` Mason
2015-03-27 20:53 ` Russell King - ARM Linux
2015-04-01 12:07 ` Mason
2015-04-01 12:12 ` Russell King - ARM Linux
2015-04-01 12:47 ` Mason [this message]
2015-04-01 12:28 ` Marc Zyngier
2015-04-01 12:47 ` Mason
2015-04-01 13:01 ` Mason
2015-04-01 13:14 ` Marc Zyngier
2015-04-01 14:39 ` Mason
2015-04-01 14:56 ` Marc Zyngier
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=551BE8ED.40308@free.fr \
--to=slash.tmp@free.fr \
--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).