From: Joshua Juran <jjuran@gmail.com>
To: Brad Boyer <flar@allandria.com>
Cc: Riccardo <riccardo@kaffe.org>,
Laurent Vivier <Laurent@lvivier.info>,
geert@linux-m68k.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] Add SWIM floppy support for m68k Macs.
Date: Tue, 4 Nov 2008 23:37:09 -0800 [thread overview]
Message-ID: <F4658C02-D1D5-44E5-BF17-671AE770CD71@gmail.com> (raw)
In-Reply-To: <20081104200600.GA32663@cynthia.pants.nu>
On Nov 4, 2008, at 12:06 PM, Brad Boyer wrote:
> On Tue, Nov 04, 2008 at 07:34:41PM +0100, Riccardo wrote:
>> I have a mac II, but I upgraded the SWIM chip, IIRC. I think I
>> upgraded
>> only one of the two drives to high density, but that shouldn't affect
>> you I suppose, since the problem would be the chip. I'll look in my
>> spare parts bin.
>
> I'm curious about how the chip update appears on the II. Does this
> system
> now show up as a IIx? My understanding is that the upgrade kit
> included
> a new set of ROM chips that include the same bits as the ones from
> the IIx.
> Hopefully there's a logical way to detect this upgrade, but it
> would be
> interesting to know if the update changes the gestalt ID.
You would detect an upgraded ROM by reading the ROM, I imagine. In
Genie, it's at /sys/mac/rom.
By the way, does anyone know how to calculate a ROM checksum, or will
I have to reverse-engineer CopyROM or somesuch?
Josh
next prev parent reply other threads:[~2008-11-05 7:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 9:43 [PATCH] Add SWIM floppy support for m68k Macs Laurent
2008-11-01 18:10 ` Brad Boyer
2008-11-02 0:29 ` Finn Thain
2008-11-02 5:23 ` Brad Boyer
2008-11-02 12:02 ` Laurent Vivier
2008-11-04 18:34 ` Riccardo
2008-11-04 20:06 ` Brad Boyer
2008-11-05 0:58 ` Riccardo
2008-11-05 2:28 ` Brad Boyer
2008-11-05 21:43 ` Riccardo
2008-11-06 4:18 ` Brad Boyer
2008-11-05 6:58 ` Finn Thain
2008-11-05 21:45 ` Riccardo
2008-11-05 7:37 ` Joshua Juran [this message]
2008-11-05 10:31 ` Finn Thain
2008-11-05 12:20 ` Joshua Juran
2008-11-05 13:10 ` Finn Thain
2008-11-05 14:32 ` Laurent Vivier
2008-11-06 4:09 ` Brad Boyer
2008-11-02 6:00 ` Finn Thain
2008-11-02 11:59 ` Laurent Vivier
2008-11-02 8:54 ` Geert Uytterhoeven
2008-11-02 11:21 ` Laurent Vivier
2008-11-02 21:28 ` Brad Boyer
2008-11-03 0:14 ` Finn Thain
2008-11-03 18:58 ` Laurent Vivier
2008-11-09 16:16 ` Geert Uytterhoeven
2008-11-09 21:47 ` Laurent Vivier
2008-11-09 23:05 ` Michael Schmitz
2008-11-10 0:15 ` Finn Thain
2008-11-11 8:52 ` Geert Uytterhoeven
2008-11-11 9:43 ` Finn Thain
2008-11-11 10:21 ` Geert Uytterhoeven
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=F4658C02-D1D5-44E5-BF17-671AE770CD71@gmail.com \
--to=jjuran@gmail.com \
--cc=Laurent@lvivier.info \
--cc=flar@allandria.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=riccardo@kaffe.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