public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] block: remove the paride drivers
Date: Thu, 15 Mar 2018 23:37:18 +0100	[thread overview]
Message-ID: <201803152337.18938.linux@rainbow-software.org> (raw)
In-Reply-To: <201803152304.40423.linux@rainbow-software.org>

On Thursday 15 March 2018 23:04:40 Ondrej Zary wrote:
> On Thursday 15 March 2018 09:04:55 Christoph Hellwig wrote:
> > On Thu, Mar 15, 2018 at 09:04:24AM +0100, Ondrej Zary wrote:
> > > On Thursday 15 March 2018, Christoph Hellwig wrote:
> > > > The paride drivers are some of the cruftiest, grottiest block drivers
> > > > (besides drivers/ide and floppy.c) and have seen one single targeted
> > > > commit since the dawn of git in 2007.  Drop them to make block layer
> > > > improvements easier.
> > >
> > > This will make my parallel port ZIP and LS-120 drives useless :(
> >
> > So you are still using them and the code actually works properly?
>
> I don't use them daily, only occasionally. Last time they worked.
> Checked now and it seems to work:

Forgot that my ZIP drive uses the PPA driver, which seems to work too:

# modprobe ppa
[  816.690602] ppa: Version 2.07 (for Linux 2.4.x)
[  816.762167] ppa: Found device at ID 6, Attempting to use EPP 32 bit
[  816.763037] ppa: Communication established with ID 6 using EPP 32 bit
[  816.807658] scsi host4: Iomega VPI0 (ppa) interface
[  816.926616] scsi 4:0:6:0: Direct-Access     IOMEGA   ZIP 100          D.08 PQ: 0 ANSI: 2
[  816.987969] sd 4:0:6:0: Attached scsi generic sg1 type 0
[  817.054564] sd 4:0:6:0: Power-on or device reset occurred
[  817.158623] sd 4:0:6:0: [sdb] Attached SCSI removable disk
[  817.742723] sd 4:0:6:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[  817.745168] sd 4:0:6:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
[  839.268575] sd 4:0:6:0: [sdb] Spinning up disk...
[  840.320383] ..ready
[  841.596371] sd 4:0:6:0: [sdb] 196608 512-byte logical blocks: (101 MB/96.0 MiB)
[  842.088415]  sdb: sdb4


-- 
Ondrej Zary

      parent reply	other threads:[~2018-03-15 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15  7:52 [PATCH, RFC] block: remove the paride drivers Christoph Hellwig
2018-03-15  8:04 ` Ondrej Zary
2018-03-15  8:04   ` Christoph Hellwig
2018-03-15 22:04     ` Ondrej Zary
2018-03-15 22:17       ` Ondrej Zary
2018-03-15 22:37       ` Ondrej Zary [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=201803152337.18938.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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