From: Robert Hancock <hancockrwd@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org,
Roland Hughes <roland@logikalsolutions.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Question about LS120 floppies
Date: Sun, 02 Aug 2009 20:42:43 -0600 [thread overview]
Message-ID: <4A764EA3.5050708@gmail.com> (raw)
In-Reply-To: <4A761EED.4030606@lwfinger.net>
On 08/02/2009 05:19 PM, Larry Finger wrote:
> Robert Hancock wrote:
>> Yes, definitely a lot of uninformed speculation on that thread. The
>> floppy driver has nothing to do with any IDE/ATA drive like this, and if
>> OpenSUSE is using libata drivers then attempting to load the IDE floppy
>> driver is also useless.
>>
>> It would be useful if the reporter could verify that the drive is at all
>> functional with that media under any OS. That "Cannot read medium -
>> unknown format" is being reported by the drive itself in response to a
>> "read capacity" request, not the driver. So unless there's some magic
>> that the driver needs to do to get the drive to recognize the disc, it
>> seems like a hardware problem.
>
> Since the last posting on this thread, I have acquired the hardware
> from Roland Hughes. He reports that it worked with Ubuntu Hardy,
> FreeDOS and Windows XP. I am assuming that the hardware is OK, but it
> certainly is strange. I don't know the details for all commands, but
> the command to get the capacity is 0x23 rather than the standard 0x25.
>
> Will it be possible to make such strange hardware work under libata?
> Is there a document that shows how to implement quirky devices? I
> found the scsi_static_device_list[] entries, but also saw the
> admonition not to add to that list.
Well, it looks like there is some specific code for this drive in
drivers/ide/ide-floppy.c that uses READ FORMAT CAPACITIES, which "allows
the Host to request a list of the possible format capacities
for an installed writable media" instead of READ CAPACITY. The code in
the sd driver (which gets used under libata) doesn't do that. However
from my reading of the MMC spec (which is where READ FORMAT CAPACITIES
is defined), it seems like READ CAPACITY should still work. (But then I
wouldn't be surprised if the manufacturer used the SCSI/MMC standards as
toilet paper..)
Supposedly LS-120 disks are pre-formatted, so the "cannot read medium -
unknown format" error is rather bizarre. It would definitely be useful
to verify that this drive is at all functional under an older distro
using the IDE drivers, or WinXP before spending too much time on it..
prev parent reply other threads:[~2009-08-03 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 20:30 Question about LS120 floppies Larry Finger
2009-07-02 5:22 ` Robert Hancock
2009-07-02 14:01 ` Larry Finger
2009-07-02 17:12 ` Alan Cox
2009-07-02 23:54 ` Robert Hancock
2009-07-03 0:20 ` Larry Finger
2009-08-02 23:19 ` Larry Finger
2009-08-03 2:42 ` Robert Hancock [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=4A764EA3.5050708@gmail.com \
--to=hancockrwd@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=roland@logikalsolutions.com \
/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;
as well as URLs for NNTP newsgroup(s).