From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Max Staudt <max@enpas.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1
Date: Mon, 4 Nov 2019 19:19:46 -0800 [thread overview]
Message-ID: <20191105031946.GA31507@allandria.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1.1911051318590.160@nippy.intranet>
On Tue, Nov 05, 2019 at 01:33:00PM +1100, Finn Thain wrote:
> All the PB 190 machines that I've come across have a late revision 68LC040
> CPU that is free of errata. Please see,
> http://www.mac.linux-m68k.org/docs/faq.php#sec-4.5
>
> The Performa 636 is highly likely to be affected, but you can run Linux
> from initramfs to avoid page faults in code sections. That would allow you
> to test the IDE driver.
>
> Or you can just replace the CPU with a full 68040, since it is socketed.
I'll try the PB190 first anyway. It should be easier due to not needing
to setup a monitor. I'm not sure if I ever booted Linux on either of
them, since I acquired both about the time I started getting too busy
to spend time on such things. I just found the Performa, and it's actually
a Performa 630CD but I don't see any obvious difference based on the specs.
I just took a look at the macide driver, and it appears to do basically
nothing other than pass a list of addresses into the core ide code. It's
one of the smallest drivers I've ever seen.
> But watch out for leaking capacitors and batteries...
I should pull out every machine in my collection and look for those sorts
of issues. None of them have been checked in at least 5 or 6 years.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2019-11-05 3:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 7:35 [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1 Geert Uytterhoeven
2019-10-01 10:55 ` Max Staudt
2019-10-07 14:11 ` Max Staudt
2019-11-04 11:06 ` Geert Uytterhoeven
2019-11-04 21:15 ` Max Staudt
2019-11-05 0:01 ` Christoph Hellwig
2019-11-05 0:14 ` John Paul Adrian Glaubitz
2019-11-05 0:53 ` Brad Boyer
2019-11-05 2:33 ` Finn Thain
2019-11-05 3:19 ` Brad Boyer [this message]
2019-11-05 4:13 ` Finn Thain
2019-11-05 20:36 ` Brad Boyer
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=20191105031946.GA31507@allandria.com \
--to=flar@allandria.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=max@enpas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.