From: Finn Thain <fthain@telegraphics.com.au>
To: Brad Boyer <flar@allandria.com>
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: Tue, 5 Nov 2019 13:33:00 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1.1911051318590.160@nippy.intranet> (raw)
In-Reply-To: <20191105005318.GA29558@allandria.com>
Hi Brad,
On Mon, 4 Nov 2019, Brad Boyer wrote:
>
> I have a couple old macs with IDE. I have a PowerBook 190 and a Performa
> (a 636? - it's buried away so I'm not 100% sure) both with IDE drives.
> I'll try to find time to pull one of them out and see if they still run.
> Can Linux run on a system with a 68LC040 these days? I know there were
> issues with FPU emulation at various points. Both of those would lack
> FPU due to using a 68LC040 chip.
>
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.
But watch out for leaking capacitors and batteries...
--
next prev parent reply other threads:[~2019-11-05 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191001073539.4488-1-geert@linux-m68k.org>
2019-10-07 14:11 ` [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1 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 [this message]
2019-11-05 3:19 ` Brad Boyer
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=alpine.LNX.2.21.1.1911051318590.160@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=flar@allandria.com \
--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 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).