On Thu, Nov 08, 2007 at 11:43:45AM +0900, Tejun Heo wrote:
I believe I have a small PCI card here with an HPT366 chip on it.
Does anyone there want it before I throw it away?
I already have a 372. It should be almost the same, right?
They are not very similar no. HPT37x is a progression
Alan Cox wrote:
On Thu, Nov 08, 2007 at 11:43:45AM +0900, Tejun Heo wrote:
I believe I have a small PCI card here with an HPT366 chip on it.
Does anyone there want it before I throw it away?
I already have a 372. It should be almost the same, right?
They are not very similar no. HPT37x is
Mark Lord wrote:
Bartlomiej Zolnierkiewicz wrote:
* hpt366.c::hpt3xx_intrproc() is the only user of hwif-intrproc
..
Speaking of which..
I believe I have a small PCI card here with an HPT366 chip on it.
Does anyone there want it before I throw it away?
I already have a 372. It should
Bartlomiej Zolnierkiewicz wrote:
* hpt366.c::hpt3xx_intrproc() is the only user of hwif-intrproc
..
Speaking of which..
I believe I have a small PCI card here with an HPT366 chip on it.
Does anyone there want it before I throw it away?
-ml
-
To unsubscribe from this list: send the line
Hello.
Bartlomiej Zolnierkiewicz wrote:
Given that:
* hpt366.c::hpt3xx_intrproc() is the only user of hwif-intrproc
* hpt366.c::hpt3xx_quirkproc() sets drive-quirk_list to 1 for quirky drives
which is a value unique to hpt366 host driver
we can remove hwif-intproc and just check for
Given that:
* hpt366.c::hpt3xx_intrproc() is the only user of hwif-intrproc
* hpt366.c::hpt3xx_quirkproc() sets drive-quirk_list to 1 for quirky drives
which is a value unique to hpt366 host driver
we can remove hwif-intproc and just check for drive-quirk_list == 1
in ide_do_request().
Cc:
