public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Riccardo <riccardo@kaffe.org>
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 20:18:44 -0800	[thread overview]
Message-ID: <20081106041844.GB17813@cynthia.pants.nu> (raw)
In-Reply-To: <D804E89A-AB82-11DD-9A74-00050249ADE1@kaffe.org>

On Wed, Nov 05, 2008 at 10:43:54PM +0100, Riccardo wrote:
> true. But if the gestalt remains 6 even with a HD drive chip, how can 
> you detect it?
> 
> 
> - original IWM 800k drives
> - SWIM with 800k drives or mixed drives
> - SWIM with only 1.4k drives
> 
> I'm in the second situation, btw.

We can definitely detect the difference between the second and third
options, since the SWIM chip can detect the type of each drive that
is connected. The driver detects the media type, but I don't recall
if it explicitly checked the drive type. The swim_iop driver did
that (and not much else) so the chip has the capability.

Telling which chip is installed may be the hardest part, although
the SWIM chip has a compatibility mode. As mentioned in another
email, there is a procedure to change the mode the chip is in. If
this method does something predictable on the IWM chip that doesn't
put the chip into a bad state, then we can probably detect which
chip is actually installed reliably. It might be interesting to
disassemble the drivers in the updated ROM to see if it can cope
with the IWM chip for people that tried the new ROM with the old
floppy controller.

	Brad Boyer
	flar@allandria.com


  reply	other threads:[~2008-11-06  4:19 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 [this message]
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=20081106041844.GB17813@cynthia.pants.nu \
    --to=flar@allandria.com \
    --cc=Laurent@lvivier.info \
    --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