From: Daniel Palmer <daniel@0x0f.com>
To: geert@linux-m68k.org, gerg@linux-m68k.org,
linux-m68k@lists.linux-m68k.org
Cc: linux-kernel@vger.kernel.org, Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH 0/4] m68k: Add 060 PCR info to /proc/cpuinfo
Date: Thu, 19 Nov 2026 21:35:54 +0900 [thread overview]
Message-ID: <20261119123558.2108296-1-daniel@0x0f.com> (raw)
Apparently the rev6 060 can overclock to ~100MHz
but mine seems to only manage ~60MHz (I wonder if some part
of it that other OSes don't use doesn't actually like
overclocking...).
I started to wonder if I actually had a rev6 and noticed
you can't see this info from /proc/cpuinfo right now.
So I added it. The only messy part I think is the FPU
asm changes to stop m68060.h from breaking the build.
Daniel Palmer (4):
m68k: Add and use wrapper for FPU inline asm
m68k: Add and use defines for 68060 PCR register
m68k: Add helpers to read and write the 68060's PCR
m68k: show the 68060's PCR in /proc/cpuinfo
arch/m68k/atari/config.c | 7 ++--
arch/m68k/include/asm/fpu.h | 6 ++++
arch/m68k/include/asm/m68060.h | 34 ++++++++++++++++++
arch/m68k/kernel/head.S | 3 +-
arch/m68k/kernel/process.c | 19 +++++-----
arch/m68k/kernel/setup_mm.c | 23 +++++++++----
arch/m68k/kernel/signal.c | 63 ++++++++--------------------------
7 files changed, 85 insertions(+), 70 deletions(-)
create mode 100644 arch/m68k/include/asm/m68060.h
--
2.55.0
next reply other threads:[~2026-11-19 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 12:35 Daniel Palmer [this message]
2026-11-19 12:35 ` [PATCH 1/4] m68k: Add and use wrapper for FPU inline asm Daniel Palmer
2026-11-19 12:35 ` [PATCH 2/4] m68k: Add and use defines for 68060 PCR register Daniel Palmer
2026-11-19 12:35 ` [PATCH 3/4] m68k: Add helpers to read and write the 68060's PCR Daniel Palmer
2026-11-19 12:35 ` [PATCH 4/4] m68k: show the 68060's PCR in /proc/cpuinfo Daniel Palmer
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=20261119123558.2108296-1-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®