Messages in this thread |  | | | From | "Miller, Mike (OS Dev)" <> | | Date | Thu, 7 Aug 2008 19:04:54 +0000 | | Subject | RE: HP (Compaq) Smart Array 5xxx controller SCSI driver |
| |
> -----Original Message----- > From: FUJITA Tomonori [mailto:fujita.tomonori@lab.ntt.co.jp] > Sent: Thursday, July 24, 2008 10:07 AM > To: Miller, Mike (OS Dev) > Cc: fujita.tomonori@lab.ntt.co.jp; > scameron@beardog.cca.cpqcorp.net; > linux-kernel@vger.kernel.org; linux-scsi@vger.kernel.org > Subject: RE: HP (Compaq) Smart Array 5xxx controller SCSI driver > > On Thu, 24 Jul 2008 15:00:00 +0000 > "Miller, Mike (OS Dev)" <Mike.Miller@hp.com> wrote: > > > > > > > As for the patches I mentioned which were previously > ignored for > > > > improving how the current cciss SCSI code handled hot > plogging, if > > > > you're curious about that, check here: > > > > > > > > http://marc.info/?l=linux-scsi&m=120213565000426&w=4 > > > > > > > > A change like that becomes more important if logical drives are > > > > exposed through the scsi layer. > > > > > > We need to think about the best way to map (expose) logical and > > > physical drivers to SCSI luns. As I wrote before, I'm > interested in > > > how HP SCSI driver does. > > > > We don't neccesarily want or need to expose the physical > disks. The only exception is disks that are not part of a > logical volume. If the disks are part of a logical volume but > exposed the user may shoot themselves in the foot by > destroying the firmware metadata. > > Oops, sorry, I meant physical tape drives. >
Tomo, I patched your driver into the 2.6.27-rc1 kernel. After compiling the driver I get:
[root@testmonkey linux-2.6]# insmod drivers/scsi/ciss.ko insmod: error inserting 'drivers/scsi/ciss.ko': -1 Invalid module format
[root@testmonkey linux-2.6]# gcc --version gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)
[root@testmonkey linux-2.6]# uname -r 2.6.26
I built inside the tree. Any thoughts?
-- mikem
|  |