From owner-freebsd-scsi Mon Jan 21 10:56: 0 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from catalepsy.pdl.cmu.edu (CATALEPSY.PDL.CMU.EDU [128.2.134.92]) by hub.freebsd.org (Postfix) with ESMTP id 04C2437B404 for ; Mon, 21 Jan 2002 10:55:47 -0800 (PST) Received: (from bucy@localhost) by catalepsy.pdl.cmu.edu (8.11.4/8.11.4) id g0LIthN16714 for freebsd-scsi@freebsd.org; Mon, 21 Jan 2002 13:55:43 -0500 Date: Mon, 21 Jan 2002 13:55:43 -0500 From: "John S. Bucy" To: freebsd-scsi@freebsd.org Subject: target mode passthrough Message-ID: <20020121135542.C23025@catalepsy.pdl.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org A number of research projects at the Parallel Data Lab at CMU are making increasing use of target-mode scsi in FreeBSD to enable storage-systems research. We have found that hacking support for more and more scsi commands in the existing target mode driver to be a real pain. What I'd like to do is write a "target mode passthrough" driver that would allow all SCBs to be handled by a userland process rather than in the kernel. I would like to hear from people what they think the Right Way(tm) to do this might be and what sorts of limitations I can expect to see. In particular: 1. Should I try to incorporate this into existing CAM APIs or do something else? 2. Can we support tagged queueing? 3. Will disconnecting on every command while its queued to userspace cause problems either locally or with the initiator? 4. What degree of control over disconnection do the HBA drivers support? thanks john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 22 7:13:13 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id E3B8637B432 for ; Tue, 22 Jan 2002 07:12:55 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g0MFCt961133 for scsi@freebsd.org; Tue, 22 Jan 2002 10:12:55 -0500 (EST) (envelope-from mwlucas) Date: Tue, 22 Jan 2002 10:12:55 -0500 From: Michael Lucas To: scsi@freebsd.org Subject: FAQ fact-checking Message-ID: <20020122101255.A61116@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Folks, This is straight from the FAQ/Handbook. I suspect that the kernel option described is wrong. The quote marks lead me to suspect that this is quite old, though. -- Sometimes, a SCSI CDROM may be missed because it didn't have enough time to answer the bus reset. If you have a SCSI CDROM please add the following option to your kernel configuration and rebuild your kernel. options "SCSI_DELAY=15" -- I suspect think it should be: options SCSI_DELAY=15000 as per GENERIC. Or am I just a loser? Thanks, Michael -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 22 8:22:27 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B875537B400 for ; Tue, 22 Jan 2002 08:22:21 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g0MGMFs67724; Tue, 22 Jan 2002 09:22:15 -0700 (MST) (envelope-from ken) Date: Tue, 22 Jan 2002 09:22:15 -0700 From: "Kenneth D. Merry" To: Michael Lucas Cc: scsi@FreeBSD.ORG Subject: Re: FAQ fact-checking Message-ID: <20020122092215.A67669@panzer.kdm.org> References: <20020122101255.A61116@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20020122101255.A61116@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Jan 22, 2002 at 10:12:55AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jan 22, 2002 at 10:12:55 -0500, Michael Lucas wrote: > > Folks, > > This is straight from the FAQ/Handbook. I suspect that the kernel > option described is wrong. The quote marks lead me to suspect that > this is quite old, though. > > -- > Sometimes, a SCSI CDROM may be missed because it didn't have enough > time to answer the bus reset. If you have a SCSI CDROM please add the > following option to your kernel configuration and rebuild your kernel. > > options "SCSI_DELAY=15" > -- > > I suspect think it should be: > > options SCSI_DELAY=15000 > > as per GENERIC. Or am I just a loser? That is correct. The value was changed from seconds to milliseconds in the CAM transition. A kernel with SCSI_DELAY set less than 100 will not compile. That will catch most users who think the value is in seconds. (If SCSI_DELAY is set to 0, we default to the minimum value of 100ms.) It isn't just CDROM drives, but any SCSI device that takes a while to recover/reinitialize after a bus reset. With most modern SCSI devices you can get away with the default 2 second delay, but we put 15 seconds in GENERIC to cover most any peripheral a user might attach to his system. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 22 9:40:48 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from deevil.homeunix.org (adsl-21-142-138.mia.bellsouth.net [66.21.142.138]) by hub.freebsd.org (Postfix) with SMTP id B360F37B405 for ; Tue, 22 Jan 2002 09:40:43 -0800 (PST) Received: (qmail 13862 invoked by uid 1001); 22 Jan 2002 17:40:24 -0000 Date: Tue, 22 Jan 2002 12:40:19 -0500 From: Ken Ebling To: freebsd-scsi@freebsd.org Subject: Re: FAQ fact-checking Message-ID: <20020122124017.A13844@deevil.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jan 22, 2002 at 10:12:55 -0500, Michael Lucas wrote: > > Folks, > > This is straight from the FAQ/Handbook. I suspect that the kernel > option described is wrong. The quote marks lead me to suspect that > this is quite old, though. > > -- > Sometimes, a SCSI CDROM may be missed because it didn't have enough > time to answer the bus reset. If you have a SCSI CDROM please add the > following option to your kernel configuration and rebuild your kernel. > > options "SCSI_DELAY=15" > -- > > I suspect think it should be: > > options SCSI_DELAY=15000 > > as per GENERIC. Or am I just a loser? On Tue, Jan 22, 2002 at 10:12:55 -0500, Michael Lucas wrote: > > Folks, > > This is straight from the FAQ/Handbook. I suspect that the kernel > option described is wrong. The quote marks lead me to suspect that > this is quite old, though. > > -- > Sometimes, a SCSI CDROM may be missed because it didn't have enough > time to answer the bus reset. If you have a SCSI CDROM please add the > following option to your kernel configuration and rebuild your kernel. > > options "SCSI_DELAY=15" > -- > > I suspect think it should be: > > options SCSI_DELAY=15000 > > as per GENERIC. Or am I just a loser? Wow! Michael Lucas asking a question about FreeBSD?! I thought you knew everything! :) I absolutely love all your "Big Scary Daemnons" articles. Keep up the good work. Ken Ebling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 23 10:11:47 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 96EB037B400 for ; Wed, 23 Jan 2002 10:11:42 -0800 (PST) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id KAA17997 for ; Wed, 23 Jan 2002 10:11:37 -0800 (PST) Message-Id: <200201231811.KAA17997@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: freebsd-scsi@freebsd.org Subject: Adaptec 29160 woes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Jan 2002 10:11:36 -0800 From: Dave Hayes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org FreeBSD 4.4-RELEASE trying to use two: ahc0: port 0xb800-0xb8ff mem 0xf2800000-0xf2800fff irq 9 at device 10.0 on pci2 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xb400-0xb4ff mem 0xf2000000-0xf2000fff irq 9 at device 11.0 on pci2 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs With the first controller supporting 2 IBM disks, and the second supporting 4 IBM disks, like so: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da5 at ahc1 bus 0 target 3 lun 0 da5: Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da5: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) I get SCSI parity errors trying to disklabel the last drive on the 2nd card (da5). When I do something "clever" like moving that da5 to the end of the first controller (ahc0), the machine fails to boot off of da0. Suspecting the disk, I checked and scanned da5 by the BIOS verify utility. It's perfectly fine. Interestingly enough, the following: dd if=/dev/zero of=/dev/rda5s1 produces no errors. The version of adaptec BIOS I am using is 3.10.0. Anyone have any clues as to what is going on...before I completely replace these controller cards? ;) ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< A consensus means that everyone agrees to say collectively what no one believes individually. - Abba Eban To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 23 11:26:10 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id B015837B404 for ; Wed, 23 Jan 2002 11:26:05 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g0NJQ1u77579; Wed, 23 Jan 2002 12:26:01 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200201231926.g0NJQ1u77579@aslan.scsiguy.com> To: "John S. Bucy" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: target mode passthrough In-Reply-To: Your message of "Mon, 21 Jan 2002 13:55:43 EST." <20020121135542.C23025@catalepsy.pdl.cmu.edu> Date: Wed, 23 Jan 2002 12:26:01 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > >A number of research projects at the Parallel Data Lab at CMU are >making increasing use of target-mode scsi in FreeBSD to enable >storage-systems research. We have found that hacking support for more >and more scsi commands in the existing target mode driver to be a real >pain. Well, that driver is really only a model. As it stands, most new commands should just fall out into the exception handler to be handled by the userland daemon anyway. >What I'd like to do is write a "target mode passthrough" driver that >would allow all SCBs to be handled by a userland process rather than >in the kernel. I would like to hear from people what they think the >Right Way(tm) to do this might be and what sorts of limitations I can >expect to see. In particular: > >1. Should I try to incorporate this into existing CAM APIs or do > something else? No CAM APIs need to change. All of the CCB types should remain the same, etc. You just need to change the policy of the existing target mode driver to not bother to handle reads, writes, and inquiry request specially in the kernel. If this became the default "sample implementation", I'd be fine with that. >2. Can we support tagged queueing? Sure. It may already work in the -stable aic7xxx driver, but if not, it's only because I haven't pushed my latest driver into the FreeBSD tree yet. I would expect the qlogic driver to just work already. >3. Will disconnecting on every command while its queued to userspace >cause problems either locally or with the initiator? This really only applies to parallel SCSI. The target can only disconnect is the initiator has given it the privledge to disconnect. Although there will be increased latency due to going all the way to userland to handle a request, this shouldn't be too big a deal if you are using tags and have a sufficient number of tags outstanding. >4. What degree of control over disconnection do the HBA drivers >support? It's been a while, but I believe you can specify during your enable-lun call whether disconnection should be performed by the target (with the caveat about privledge noted above). I can't say which drivers honor this though. On the initiator side, you can use camcontrol to enable or disable disconnection. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 23 11:31:21 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 21B7337B402 for ; Wed, 23 Jan 2002 11:31:15 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g0NJV8u77642; Wed, 23 Jan 2002 12:31:08 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200201231931.g0NJV8u77642@aslan.scsiguy.com> To: Dave Hayes Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 29160 woes In-Reply-To: Your message of "Wed, 23 Jan 2002 10:11:36 PST." <200201231811.KAA17997@hokkshideh.jetcafe.org> Date: Wed, 23 Jan 2002 12:31:08 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >I get SCSI parity errors trying to disklabel the last drive on the >2nd card (da5). These are actually CRC errors. >Suspecting the disk, I checked and scanned da5 by the BIOS verify >utility. It's perfectly fine. The Adaptec BIOS may have negotiated down to a speed that allowed the verify to proceed. FreeBSD's SCSI layer doesn't have any speed fallback support yet. The BIOS won't tell you if it has done this. >Interestingly enough, the following: > > dd if=/dev/zero of=/dev/rda5s1 It is the target's responsibility to check the CRC or parity during a write. This just means that the target is able to read what we are writing to it okay, but we are not always able to read what the target is writing to us. >Anyone have any clues as to what is going on...before I completely >replace these controller cards? ;) I doubt it is the controller. I would suspect the drive has a bad connector. Do you get the same behavior if you force narrow-async on this drive via SCSI-Select? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 23 12: 0: 0 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 2F6DA37B402 for ; Wed, 23 Jan 2002 11:59:57 -0800 (PST) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id LAA20192; Wed, 23 Jan 2002 11:59:54 -0800 (PST) Message-Id: <200201231959.LAA20192@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 29160 woes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Jan 2002 11:59:54 -0800 From: Dave Hayes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Justin T Gibbs writes: >> Suspecting the disk, I checked and scanned da5 by the BIOS verify >> utility. It's perfectly fine. > The Adaptec BIOS may have negotiated down to a speed that allowed > the verify to proceed. FreeBSD's SCSI layer doesn't have any speed > fallback support yet. The BIOS won't tell you if it has done this. Joy. Thanks for enlightening me on this, now I know not to use this to verify hardware integrity. >> dd if=/dev/zero of=/dev/rda5s1 > It is the target's responsibility to check the CRC or parity during > a write. This just means that the target is able to read what we > are writing to it okay, but we are not always able to read what the > target is writing to us. Hmm, so would the inverse test (i.e. dd if=/dev/rda5s1 of=/dev/null) be a better indicator of problems? > I doubt it is the controller. I would suspect the drive has a > bad connector. Do you get the same behavior if you force > narrow-async on this drive via SCSI-Select? If that means set "Enable wide negotiation" to "NO", then I just tried that (only on the suspect disk at the end of the chain) and I still get aborted commands trying to re-install the OS. I think I agree about your suspect though, the drives are mounted in those removable bays. The drive was replaced to see if that was the problem, but the bay was not. Back to the hardware bench for me. Thanks. ;) ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< In order to be utterly happy the only thing necessary is to refrain from comparing this moment with other moments in the past, which I often did not fully enjoy because I was comparing them with other moments of the future. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 24 4:50:21 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163]) by hub.freebsd.org (Postfix) with ESMTP id B886D37B429 for ; Thu, 24 Jan 2002 04:50:03 -0800 (PST) Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227]) by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id NAA16778; Thu, 24 Jan 2002 13:49:55 +0100 (MET) Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56]) by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id NAA14974; Thu, 24 Jan 2002 13:49:54 +0100 (MET) Received: by MCHH246E with Internet Mail Service (5.5.2653.19) id ; Thu, 24 Jan 2002 13:49:52 +0100 Message-ID: <67E0BE167008D31185F60008C7289DA0E13113@MCHH218E> From: Reifenberger Michael EXT To: "'Jan.Stocker@t-online.de'" , Antelecom - NOC Cc: freebsd-scsi@FreeBSD.ORG Subject: AW: SCSI-emulation? Date: Thu, 24 Jan 2002 13:49:26 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, since the changes seem to be well separated would it be possible to = -commit them to -current? Bye/2 ------ Michael Reifenberger - IT, UNIX, R/3-Basis Work: Michael.Reifenberger@plaut.de Proj: = Michael.Reifenberger.gp@icn.siemens.de Pers: Michael@Reifenberger.com Webspace: http://www.reifenberger.com -----Urspr=FCngliche Nachricht----- Von: Jan.Stocker@t-online.de [mailto:Jan.Stocker@t-online.de] Gesendet: Montag, 14. Januar 2002 21:37 An: Antelecom - NOC Cc: freebsd-scsi@FreeBSD.ORG Betreff: Re: SCSI-emulation? Take a look at: http://www.cuivre.fr.eu.org/~thomas/atapicam/ Jan On Mon, 2002-01-14 at 21:06, Antelecom - NOC wrote: > Hi List, >=20 > i just got a NEC NR7800B cd-rw drive (IDE) that I am trying to use = under > FreeBSD 4.4. My question is how to enable scsi emulation for this = drive... > ideally i would like to be able to use XCDRoast or BurnIT. >=20 > Thank You in Advance, > Shaun >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 24 5:15:34 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from nmh.informatik.uni-bremen.de (nmh.informatik.uni-bremen.de [134.102.224.3]) by hub.freebsd.org (Postfix) with ESMTP id DF35837B402 for ; Thu, 24 Jan 2002 05:15:29 -0800 (PST) Received: from s61.informatik.uni-bremen.de (s61.informatik.uni-bremen.de [134.102.201.21]) by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g0ODFQ427753; Thu, 24 Jan 2002 14:15:26 +0100 (MET) Received: (from jstocker@localhost) by s61.informatik.uni-bremen.de (8.10.2+Sun/8.8.7) id g0ODFQJ00705; Thu, 24 Jan 2002 14:15:26 +0100 (MET) Date: Thu, 24 Jan 2002 14:15:26 +0100 (MET) From: Jan Stocker To: Reifenberger Michael EXT Cc: "'Jan.Stocker@t-online.de'" , Antelecom - NOC , freebsd-scsi@FreeBSD.ORG Subject: Re: AW: SCSI-emulation? In-Reply-To: <67E0BE167008D31185F60008C7289DA0E13113@MCHH218E> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Its no problem, its running on my current at home. I may send you the patch= for current. Jan --=20 "Chain letters," said the Tyrant. "The Chain Letter to the Ephebians. Forget Your Gods. Be Subjugated. Learn to Fear. Do not break the chain -- the last people who did woke up one morning to find fifty thousand armed men on their lawn." -- (Terry Pratchett, Small Gods) On Thu, 24 Jan 2002, Reifenberger Michael EXT wrote: > Hi, > since the changes seem to be well separated would it be possible to -comm= it them to -current? >=20 > Bye/2 > ------ > Michael Reifenberger - IT, UNIX, R/3-Basis > Work: Michael.Reifenberger@plaut.de Proj: Michael.Reifenberger.gp@icn.= siemens.de > Pers: Michael@Reifenberger.com Webspace: http://www.reifenberger.com >=20 >=20 > -----Urspr=FCngliche Nachricht----- > Von: Jan.Stocker@t-online.de [mailto:Jan.Stocker@t-online.de] > Gesendet: Montag, 14. Januar 2002 21:37 > An: Antelecom - NOC > Cc: freebsd-scsi@FreeBSD.ORG > Betreff: Re: SCSI-emulation? >=20 >=20 > Take a look at: >=20 > http://www.cuivre.fr.eu.org/~thomas/atapicam/ >=20 > Jan >=20 > On Mon, 2002-01-14 at 21:06, Antelecom - NOC wrote: > > Hi List, > >=20 > > =09i just got a NEC NR7800B cd-rw drive (IDE) that I am trying to use u= nder > > FreeBSD 4.4. My question is how to enable scsi emulation for this driv= e... > > ideally i would like to be able to use XCDRoast or BurnIT. > >=20 > > Thank You in Advance, > > Shaun > >=20 > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 25 10: 9: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from catalepsy.pdl.cmu.edu (CATALEPSY.PDL.CMU.EDU [128.2.134.92]) by hub.freebsd.org (Postfix) with ESMTP id A3EA937B41B for ; Fri, 25 Jan 2002 10:09:03 -0800 (PST) Received: (from bucy@localhost) by catalepsy.pdl.cmu.edu (8.11.4/8.11.4) id g0PI91F27148 for freebsd-scsi@freebsd.org; Fri, 25 Jan 2002 13:09:01 -0500 Date: Fri, 25 Jan 2002 13:09:01 -0500 From: "John S. Bucy" To: freebsd-scsi@freebsd.org Subject: Re: target mode passthrough Message-ID: <20020125130900.G23025@catalepsy.pdl.cmu.edu> References: <20020121135542.C23025@catalepsy.pdl.cmu.edu> <200201231926.g0NJQ1u77579@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200201231926.g0NJQ1u77579@aslan.scsiguy.com>; from gibbs@scsiguy.com on Wed, Jan 23, 2002 at 12:26:01PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Another question: I'm not sure how to deal with replies that involve a data phase. The existing pt driver did the bus transfers with read and write on the target device but this gets trickier with tagged queueing since you have to match up the reads and writes with (multiple) outstanding SCBs. I guess one solution would be to add an ioctl so you could tell the kernel driver which tag you were about to handle ... but this seems like a kludge. Since the cam and the device drivers seem to want the data in a buf, returning the bus-transfer data through the ioctl doesn't seem like the right answer either. Ideas? john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message