mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Pisati <p.pisati@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] m68k: Add 060 PCR info to /proc/cpuinfo
Date: Sun, 22 Nov 2026 11:55:49 +0100	[thread overview]
Message-ID: <20261122105549.84343-1-p.pisati@gmail.com> (raw)
In-Reply-To: <20261119123558.2108296-1-daniel@0x0f.com>

Hi Daniel,

On Thu, Nov 19, 2026 at 09:35:54PM +0900, Daniel Palmer wrote:
> 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.

Tested on v7.4-rc3 plus this series, with a multi-platform config
and with a 060-only one. Both kernels build without
warnings, boot to userspace and run fine.

# cat /proc/cpuinfo
CPU:            68060
MMU:            68060
FPU:            68882
Clocking:       49.1MHz
BogoMips:       98.20
Calibration:    491008 loops
PCR:            0x04300601 (ID 0x0430, revision 6, superscalar)

Tested-by: Paolo Pisati <p.pisati@gmail.com>
-- 
bye,
p.

      parent reply	other threads:[~2026-11-22 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 12:35 Daniel Palmer
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
2026-11-22 10:55 ` Paolo Pisati [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=20261122105549.84343-1-p.pisati@gmail.com \
    --to=p.pisati@gmail.com \
    --cc=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®