From: Riccardo <riccardo@kaffe.org>
To: Brad Boyer <flar@allandria.com>
Cc: 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: Wed, 5 Nov 2008 01:58:48 +0100 [thread overview]
Message-ID: <E7AD906F-AAD4-11DD-9F63-00050249ADE1@kaffe.org> (raw)
In-Reply-To: <20081104200600.GA32663@cynthia.pants.nu>
On Tuesday, November 4, 2008, at 09: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.
Under Mac 7.1 it gets definitively recognized as Mac II. I definitively
have a SWIM, since one of my two floppies reads HD disks, I checked
Penguin says my gestalt is 6, Mac II
A clue for the MacII is the 68020 CPU + FPU + MMU, AFAIK the only apple
machine with these specs.
I tried to boot a current 2.6.18 kernel just for fun, it goes past the
letter screen and dumps stack after recognizing the TOBY frame buffer
card and attempting to init it.
Riccardo
PS: I didn't use this mac since many months, it first stasrted up, but
then refusedfurther boots with the sad mac sound and no video output.
REmoving components trying to isolate the problem didn't help. When I
put al back together with no luck, a last attempt made it boot. Any
ideas? I see no visible damage on the motherboard, the batteries still
have some juice left...
next prev parent reply other threads:[~2008-11-05 0:59 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 [this message]
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
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=E7AD906F-AAD4-11DD-9F63-00050249ADE1@kaffe.org \
--to=riccardo@kaffe.org \
--cc=Laurent@lvivier.info \
--cc=flar@allandria.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.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