All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "David A. Gatwood" <marsmail@globegate.utm.edu>
To: Paul.Mackerras@cs.anu.edu.au
Cc: brad@pht.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: floppy driver bug: write-protect
Date: Fri, 15 Jan 1999 12:34:56 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.3.96.990115122915.25116B-100000@globegate.utm.edu> (raw)
In-Reply-To: <199901150331.OAA01845@tango.anu.edu.au>


On Fri, 15 Jan 1999, Paul Mackerras wrote:

> OK, I need to check the write-protect status in the floppy_write
> routine in swim3.c.
> 
> I have recently looked at the floppy driver source code in MkLinux,
> which looks like it is derived from macos sources.  It looks like
> there are a few tweaks which I need to do to the Linux/PPC driver.

MkLinux's driver is based on a Copland driver with a Mach Driver
interwoven and some shim code.  Needs massive cleanup, but basically works
as long as you don't have more than one floppy drive.  Also a little
trouble with writing large chunks of data (not sure why).

Thanks for the info on how the write protect is supposed to work.  I put
some checks for write protect on write, but making the mount fail is a
much more logical solution.


Later,
David

David A. Gatwood                         Visit globegate's internet
dgatwood@globegate.utm.edu                  talker, Deep Space 36
http://globegate.utm.edu                telnet globegate.utm.edu:9624

-----BEGIN GEEK CODE BLOCK-----
Version 3.1
GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++ ++>$ UBLAS*++ ++>$
P+?>$ L++ +>$ !E--- W++ +>$ N++(++ +)>++ +$ !o? K-? !w--- !O
M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t++ +>$ 5+>++ ++$ !X- !R tv+>$
b++>$ !DI !D- G++(++ +)>$ e>++ ++ h--! r--- !y-
------END GEEK CODE BLOCK------


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

      reply	other threads:[~1999-01-15 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-16  1:27 floppy driver bug: write-protect Brad Midgley
1999-01-15  2:18 ` David A. Gatwood
1999-01-15  3:30 ` Brad Midgley
1999-01-15  3:31 ` Paul Mackerras
1999-01-15 18:34   ` David A. Gatwood [this message]

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=Pine.LNX.3.96.990115122915.25116B-100000@globegate.utm.edu \
    --to=marsmail@globegate.utm.edu \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=brad@pht.com \
    --cc=linuxppc-dev@lists.linuxppc.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.