Messages in this thread | | | Date | Thu, 14 Jan 1999 18:34:39 -0500 | From | Doug Ledford <> | Subject | Re: Blacklist for DPES-* |
| |
Thomas Bogendoerfer wrote: > > I found following in patch-2.2.0-pre7: > > +{"IBM","DPES-","*", BLIST_NOTQ | BLIST_NOLUN}, > > Vendor: IBM Model: DPES-31080 !t Rev: S31K > Type: Direct-Access ANSI SCSI revision: 02 > Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 > ncr53c810-0-<0,0>: tagged command queue depth set to 8 > > I'm wondering why the disk above works with tagged command queuing since ages. > In the pre-7 patch it was only for the DPES-31080, rev S31Q, but now > it's for every DPES drive (or do I misunderstand something ?). Who thinks > it's a good idea to blacklist every DPES drive ?
I did. I don't know about Gerard's driver, but mine specifically does print out whenever a device that we set up as tagged queueing capable rejects part of our tagged queueing operation. That's what prompted that change. As for the version issue, most drives in a single family respond identically. If Gerard can confirm that your drive was actually using tagged queueing and that the driver didn't silently disable it, then we can change this around.
-- Doug Ledford <dledford@redhat.com> Opinions expressed are my own, but they should be everybody's.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |