From: Jeff Garzik <jgarzik@pobox.com>
To: akpm@osdl.org
Cc: andystewart@comcast.net,
Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: enable-reads-on-plextor-712-sa-on-26115.patch added to -mm tree
Date: Mon, 23 May 2005 19:09:02 -0400 [thread overview]
Message-ID: <4292628E.4090209@pobox.com> (raw)
In-Reply-To: <200505232245.j4NMjtk4024089@shell0.pdx.osdl.net>
akpm@osdl.org wrote:
> The patch titled
>
> Enable reads on Plextor 712-SA on 2.6.11.5
>
> has been added to the -mm tree. Its filename is
>
> enable-reads-on-plextor-712-sa-on-26115.patch
>
> Patches currently in -mm which might be from andystewart@comcast.net are
>
> enable-reads-on-plextor-712-sa-on-26115.patch
Andrew -- The use of the word 'hack' didn't trigger any response??
By hardcoding so much of the inquiry data, this patch -overwrites- valid
inquiry data provided by the device, with generic data. This patch
makes generic the probe data that the SCSI layer -depends on to be
different-.
Effectively you made one CD-ROM device work, killed all the others, and
enabled an oops generator.
Good show.
Even if this patch worked, you still need to fix the following:
* Patch INQUIRY data -slightly- to fool the SCSI layer into working
correctly. This is what Andy's patch [poorly] attempts to address.
* Handling DRQ interrupts (early patch exists)
* Padding DMA data (50% patch exists)
* Fix error handling (patch exists)
* Fix all FIS-based drivers so that an error doesn't cause an oops
* Implement non-polled REQUEST SENSE error handling for FIS-based drivers
next parent reply other threads:[~2005-05-23 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505232245.j4NMjtk4024089@shell0.pdx.osdl.net>
2005-05-23 23:09 ` Jeff Garzik [this message]
2005-05-24 0:24 ` enable-reads-on-plextor-712-sa-on-26115.patch added to -mm tree Andy Stewart
2005-05-24 0:34 ` Andrew Morton
2005-05-24 0:44 ` Andy Stewart
2005-05-24 3:30 ` Jeff Garzik
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=4292628E.4090209@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=andystewart@comcast.net \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).