Date: Sat, 05 Apr 2003 23:53:11 -0700 From: Scott Long <scott_long@btc.adaptec.com> To: "Marc G. Fournier" <scrappy@hub.org> Cc: "Marc G. Fournier" <marc.fournier@acadiau.ca> Subject: Re: kernel errors in messages about enclosure ... Message-ID: <3E8FCED7.8010500@btc.adaptec.com> In-Reply-To: <20030405005921.G613@atelier.acadiau.ca> References: <20030405005921.G613@atelier.acadiau.ca> <20030405121748.GA36962@hollin.btc.adaptec.com> <20030406013806.A14933@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc G. Fournier wrote: > On Sat, 5 Apr 2003, Scott Long wrote: > > > >I don't speak SES very well, and it's hard to say if the returned data is > >getting magled by the RAID firmware. An interesting test might be to > enable > >the aacp and ses devices (and cam, of course) and see if the ses driver > >attaches to the hardware. > > > 'K, how do you 'enable cam'? Is that just the 'device pass' entry? > > BTW, are there any plans to CAMify the aac driver? Add the following lines to your kernel config: device scbus device ses device aacp For your second question, the answer is 'no'. The aac firmware talks in terms of logical block commands. 'CAMifying' the driver would mean that block requests from the filesystem would be translated into SCSI commands by CAM and then converted back to block commands by the aac driver. Why bother? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E8FCED7.8010500>