On Fri, Aug 19, 2005 at 09:22:45AM -0400, James Bottomley wrote:
> On Fri, 2005-08-19 at 15:24 +0530, Suparna Bhattacharya wrote:
> > sda:
>
> Well, this line is identifying the root cause. It says that the
> partition code came up with no partitions for this device. Do any of
> your other devi
Hello,
your patch works!
first a box booting from a gdth:
a01:~# lsscsi
[0:0:0:0]diskICP Host Drive #00/dev/sda
[0:2:6:0]process SUPERGEM318 0 -
[1:0:0:10] diskIFT A16F-R1211 334B /dev/sdb
[1:0:0:12] diskIFT A16F-R1
Hi,
this re-enables the megaraid legacy driver (drivers/scsi/megaraid.c) which
is still completely in the kernel but is missing from drivers/scsi/Kconfig.
Some devices are NOT supported by the newgen megaraid driver (e.g. the HP
Netserver LH 3000 embedded Netraid) and the old driver still works fi
On Wed, 2005-08-24 at 14:13 -0700, Andrew Vasquez wrote:
> Not sure how we want to fix it, perhaps for backwards compatibility,
> increment present regardless of the value of proc_info.
>
> Something like this, perhaps (untested)?
Thanks for the patch, Andrew.
It certainly appears to work (the
On Wed, Aug 24, 2005 at 02:13:48PM -0700, Andrew Vasquez wrote:
> /proc support has been stripped from the qla2xxx driver. So,
> hostt->present is never incremented:
>
> void scsi_proc_hostdir_add(struct scsi_host_template *sht)
> {
> if (!sht->proc_info)
>
On Thu, 2005-08-25 at 17:09 +0100, Christoph Hellwig wrote:
> And while we're at it we should add deprecation warnings for most of
> the crufy ioctls in scsi_ioctl.c..
>
Pardon my ignorance, but to which ioctls are you referring? Are
practically all the ioctls now just junk, or is there a list so
Luben Tuikov wanted...
to move _away_ from HCIL. So that addressing of devices in SCSI Core
is _completely_ independent of addressing at the protocol layer.
I second that.
--
Stefan Richter
-=-=-=-= =--- ==--=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscri
Stefan Richter wrote:
Luben Tuikov wanted...
to move _away_ from HCIL. So that addressing of devices in SCSI Core
is _completely_ independent of addressing at the protocol layer.
I second that.
A move away from forced HCIL addressing would be a good thing.
However, its impossible to com
Begin forwarded message:
Date: Tue, 23 Aug 2005 12:53:38 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 5117] New: Panic when accessing scsi-tapedrives with
4G-remap
http://bugzilla.kernel.org/show_bug.cgi?id=5117
Summary: Panic when accessing scsi
I've been asked to pass this on for some kind of clarification.
We have management apps requiring specific information from the Smart
Array controller. We're trying to use sysfs to accomplish the task. An
example of what we need to do is below. I'm sure some of you will
recognize this as CSMI.
The
On Thu, 2005-08-25 at 13:52 -0500, Miller, Mike (OS Dev) wrote:
> I've been asked to pass this on for some kind of clarification.
> We have management apps requiring specific information from the Smart
> Array controller. We're trying to use sysfs to accomplish the task. An
> example of what we ne
> > typedef struct _CSMI_SAS_IDENTIFY {
> >__u8 bDeviceType;
> >__u8 bRestricted;
> >__u8 bInitiatorPortProtocol;
> >__u8 bTargetPortProtocol;
> >__u8 bRestricted2[8];
> >__u8 bSASAddress[8];
> >__u8 bPhyIdentifier;
> >__u8 bSignalClass;
> >__u8 bReserve
On 08/25/2005 08:24:17 PM, Andrew Morton wrote:
Subject: [Bugme-new] [Bug 5117] New: Panic when accessing scsi-tapedrives
with 4G-remap
http://bugzilla.kernel.org/show_bug.cgi?id=5117
Summary: Panic when accessing scsi-tapedrives with 4G-remap
Kernel Version: 2.6.12.5
C
Hello, fellow SCSI/ATA developers.
This is the first draft of SCSI EH document. This document tries to
describe how SCSI EH works and what choirs should be done to maintain
SCSI midlayer integrity. It's intended that this document can be used
as reference for implementing either fine-grained E
14 matches
Mail list logo
