From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Add support for Excito Bubba B3
Date: Sat, 11 Jan 2014 15:59:00 +0000 [thread overview]
Message-ID: <20140111155900.GL15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140110192032.GQ19878@titan.lakedaemon.net>
On Fri, Jan 10, 2014 at 02:20:32PM -0500, Jason Cooper wrote:
> I'm of the opinion that the kernel shouldn't assume the state of the
> system when it begins execution.
Rubbish. The kernel's requirements are well documented, and have been for
years. The reason we've documented it is because it _matters_, and it's
hard to sort out this crap before the kernel starts.
Think about it - think about how many different L2 caches there are out
there.
Think about how difficult it is to locate the L2 cache controller when
you don't know what platform you're running on.
Think about how difficult it is to disable the L2 cache.
Think about how difficult it is to flush the L2 cache, when you don't
know what sort it is, where it's located, or what instructions to use
to do that.
The kernel cares about its boot environment beacuse of these issues.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-11 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 16:12 [PATCH] ARM: Kirkwood: Add support for Excito Bubba B3 Andrew Lunn
2013-12-28 17:01 ` Jason Cooper
2013-12-28 20:59 ` Andrew Lunn
2013-12-28 21:25 ` Jason Cooper
2014-01-02 19:49 ` Jason Gunthorpe
2014-01-02 22:36 ` Ian Campbell
2014-01-02 23:08 ` Jason Gunthorpe
2014-01-03 0:44 ` Andrew Lunn
2014-01-10 19:20 ` Jason Cooper
2014-01-10 19:44 ` Jason Gunthorpe
2014-01-10 19:54 ` Jason Cooper
2014-01-10 23:02 ` Andrew Lunn
2014-01-11 0:19 ` Jason Gunthorpe
2014-01-11 15:59 ` Russell King - ARM Linux [this message]
2014-01-13 14:44 ` Jason Cooper
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=20140111155900.GL15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).