On Sun, Feb 20, 2005 at 10:47:09PM -0800, Matthew Dharm wrote:
On Sun, Feb 20, 2005 at 10:44:21PM -0500, Alan Stern wrote:
Matt, it looks like the best way to solve this problem is to go back to
the old strategy of always setting the SCSI revision to 2 (no matter what
it might actually
Add some new IPR adapters and remove one. These ids have already been
entered into http://pciids.sourceforge.net.
Signed-off-by: Brian King [EMAIL PROTECTED]
---
linux-2.6.11-rc4-bk9-bjking1/drivers/pci/pci.ids |7 +--
linux-2.6.11-rc4-bk9-bjking1/include/linux/pci_ids.h |1 +
If a device disappears across an adapter reset, ipr schedules the device to be
removed from scsi core. Any ops sent to that device prior to its actual removal
end up getting sent to the adapter using a now invalid adapter resource handle.
Usually, the adapter will just fail the command and the
The ipr family of adapters is capable of handling data transfer sizes of
16777215 bytes. Logical disk array devices under ipr are capable of only
256k transfer lengths. Patch sets max_sectors of the adapter to 32767 and
overrides max_sectors for the logical disk array devices in the
Since the ipr adapter initialization is performed by waiting for
an interrupt to occur and this is the first interrupt ever received
from the adapter, and the timeout for this interrupt is 5 minutes,
failed ipr adapters can halt the boot process for a long time.
In certain environments, it makes
Use new change_queue_type API.
Signed-off-by: Brian King [EMAIL PROTECTED]
---
linux-2.6.11-rc4-bk9-bjking1/drivers/scsi/ipr.c | 42
1 files changed, 42 insertions(+)
diff -puN drivers/scsi/ipr.c~ipr_change_queue_type drivers/scsi/ipr.c
---
Remove driver specific tcq_enable attribute now that change_queue_type
API has made it redundant.
Signed-off-by: Brian King [EMAIL PROTECTED]
---
linux-2.6.11-rc4-bk9-bjking1/drivers/scsi/ipr.c | 76
1 files changed, 76 deletions(-)
diff -puN
Various fixes to make sparse happy
Signed-off-by: Brian King [EMAIL PROTECTED]
---
linux-2.6.11-rc4-bk9-bjking1/drivers/scsi/ipr.c | 30 +++-
1 files changed, 14 insertions(+), 16 deletions(-)
diff -puN drivers/scsi/ipr.c~ipr_sparse_fixes drivers/scsi/ipr.c
---
Bump the driver version to 2.0.13
Signed-off-by: Brian King [EMAIL PROTECTED]
---
linux-2.6.11-rc4-bk9-bjking1/drivers/scsi/ipr.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -puN drivers/scsi/ipr.h~ipr_driver_version_2_0_13 drivers/scsi/ipr.h
---
Hi.
nsp32 and nsp_cs SCSI host adapter driver is now updated.
You can get newest version from here.
http://www.netlab.is.tsukuba.ac.jp/~yokota/archive/nsp_cs+nsp32-20050222.tar.gz
--
YOKOTA Hiroshi
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message
On Tue, 2005-02-22 at 06:26 +0900, YOKOTA Hiroshi wrote:
Hi.
nsp32 and nsp_cs SCSI host adapter driver is now updated.
You can get newest version from here.
http://www.netlab.is.tsukuba.ac.jp/~yokota/archive/nsp_cs+nsp32-20050222.tar.gz
Hi,
could you please be so kind as to also
On Sun, 20 Feb 2005, Matthew Dharm wrote:
Matt, it looks like the best way to solve this problem is to go back to
the old strategy of always setting the SCSI revision to 2 (no matter what
it might actually be), at least for Direct Access devices. That would
suppress the REPORT_LUNS
On Sun, 6 Feb 2005, Guennadi Liakhovetski wrote:
Two weeks since I posted this patch - ping...
...and another two weeks since you, Jamie, replied to me privately. Just
wanted to say, it would be good to get this bug fixed for the post-2.6.11
SCSI patch.
Regards
Guennadi
On Sun, 23 Jan
Following discussions which resulted from the:
[RFC] target code updates to support scanned targets
http://marc.theaimsgroup.com/?l=linux-scsim=110850749515984w=2
thread, the overall consensus seems to be that transport-classes
should support a 'true-hotplug' mechanism of device discovery and
On Mon, Feb 21, 2005 at 04:09:37PM -0800, Andrew Vasquez wrote:
* must be done from process context -- depending on transport type,
discovery can occur from a non-process context
* potentially _long_ scan times -- even if discovery is done from a
'sleeping' capable context, halting a LLDD
I'd like to propose the addition of a per-Scsi_Host work-queue to
manage these scanning as well as any other (relevant)
lower-level-driver differed requests.
Why not use the per-host error handler thread for this?
brings a deadlock condition to mind - where the error thread is needed
Jamie, mail to you bounced:
-- Forwarded message --
Date: 21 Feb 2005 22:28:46 -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: failure notice
Hi. This is the qmail-send program at mail.gmx.net.
I'm afraid I wasn't able to deliver your message to the following
--- linux-2.6.10/Documentation/scsi/nsp32.txt 1970-01-01 09:00:00.0
+0900
+++ linux-2.6.10-nsp/Documentation/scsi/nsp32.txt 2003-11-12
21:42:54.0 +0900
@@ -0,0 +1,90 @@
+ NinjaSCSI-32Bi/UDE CardBus/PCI card driver for Linux
+
+
+1. What's this?
+
+ This is Workbit
--- linux-2.6.10/Documentation/scsi/nsp_cs.txt 1970-01-01 09:00:00.0
+0900
+++ linux-2.6.10-nsp/Documentation/scsi/nsp_cs.txt 2005-02-22
08:44:10.0 +0900
@@ -0,0 +1,126 @@
+
+ WorkBiT NinjaSCSI-3/32Bi driver for Linux
+
+1. Comment
+ This is Workbit
--- linux-2.6.10/drivers/scsi/Kconfig 2005-02-22 08:23:09.0 +0900
+++ linux-2.6.10-nsp/drivers/scsi/Kconfig 2005-02-22 08:37:48.0
+0900
@@ -1474,6 +1474,22 @@
SCSI host adapter. Please read the SCSI-HOWTO, available from
--- linux-2.6.10/drivers/scsi/nsp32_debug.c 2004-10-19 06:55:06.0
+0900
+++ linux-2.6.10-nsp/drivers/scsi/nsp32_debug.c 2004-11-15 05:01:22.0
+0900
@@ -83,24 +83,24 @@
}
}
-static void print_commandk (unsigned char *command)
+static void print_commandk (const
--- linux-2.6.10/drivers/scsi/nsp32_io.h2004-10-19 06:55:28.0
+0900
+++ linux-2.6.10-nsp/drivers/scsi/nsp32_io.h2004-07-27 00:21:25.0
+0900
@@ -9,40 +9,40 @@
#ifndef _NSP32_IO_H
#define _NSP32_IO_H
-static inline void nsp32_write1(unsigned int base,
+inline
--- linux-2.6.10/drivers/scsi/pcmcia/nsp_debug.c2004-10-19
06:53:51.0 +0900
+++ linux-2.6.10-nsp/drivers/scsi/pcmcia/nsp_debug.c2004-11-20
17:17:42.0 +0900
@@ -1,12 +1,12 @@
/*
Debug
--- linux-2.6.10/drivers/scsi/pcmcia/nsp_io.h 2004-10-19 06:55:36.0
+0900
+++ linux-2.6.10-nsp/drivers/scsi/pcmcia/nsp_io.h 2004-07-27
00:24:21.0 +0900
@@ -1,40 +1,39 @@
-/*
+/***
NinjaSCSI I/O
--- linux-2.6.10/drivers/scsi/pcmcia/nsp_message.c 2004-10-19
06:53:46.0 +0900
+++ linux-2.6.10-nsp/drivers/scsi/pcmcia/nsp_message.c 2004-08-15
09:23:57.0 +0900
@@ -1,19 +1,129 @@
/*==
NinjaSCSI-3
On Mon, Feb 21 2005, Greg Stark wrote:
Jens Axboe [EMAIL PROTECTED] writes:
For the longest time, only the old PATA drivers supported barrier writes
with journalled file systems.
What about for fsync(2)? One of the most frequent sources of data loss on the
postgres mailing list has
26 matches
Mail list logo