From: William Lee Irwin III <wli@holomorphy.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: davem@redhat.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: PATCH for Sun4c clones with an 82077 FDC
Date: Tue, 26 Oct 2004 19:27:27 -0700 [thread overview]
Message-ID: <20041027022727.GQ15367@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10410270242340.26459-100000@mtfhpc.demon.co.uk>
On Wed, Oct 27, 2004 at 03:03:34AM +0100, Mark Fortescue wrote:
> I have been having trouble working out why my sun4c sparc clone could not
> find the floppy drive. I was being blind as floppy.h assumes that all
> sun4c machines only have an 82072 FDC. This asumption is not valid for
> some clones (OPUS Personal Mainframe 5000 sun4c sparc1 clone for one).
> The patch below checks to see if it is an 82072 using a simple test before
> assuming that we have an 82072. It works on my clone but it needs to be
> checked on a sun4c system with an 82072 FDC.
> Can someone with a sun4c system that has an 82072 check it to see if it
> works for them. The extra two printk messages are more for diagnostics
> when the patch is being tested (via prom console). If it does not break
> 82072 sun4c systems then the two diagnostic messages can be removed. If it
> does break the 82072 sun4c systems, then a more complicated test is
> needed that does not.
Okay, can this be done without media? I have the sun4c's, but not floppy
media. I suppose I could obtain some for the occasion.
-- wli
next prev parent reply other threads:[~2004-10-27 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 2:03 Mark Fortescue
2004-10-27 2:27 ` William Lee Irwin III [this message]
2004-10-27 12:06 ` Mark Fortescue
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=20041027022727.GQ15367@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@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
Powered by JetHome