From owner-freebsd-scsi Sun Dec 24 13:10:38 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA23066 for freebsd-scsi-outgoing; Sun, 24 Dec 1995 13:10:38 -0800 (PST) Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA23059 for ; Sun, 24 Dec 1995 13:10:33 -0800 (PST) Received: (from rmallory@localhost) by wiley.csusb.edu (8.6.11/8.6.11) id NAA21225; Sun, 24 Dec 1995 13:15:02 -0800 From: Rob Mallory Message-Id: <199512242115.NAA21225@wiley.csusb.edu> Subject: Re: ncr[01] conflicts(SUMMARY) To: rmallory@wiley.csusb.edu (Rob Mallory) Date: Sun, 24 Dec 1995 13:15:02 -0800 (PST) Cc: se@zpr.uni-koeln.de, scsi@FreeBSD.org In-Reply-To: <199512202046.MAA19149@wiley.csusb.edu> from "Rob Mallory" at Dec 20, 95 12:46:51 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk > > > > > } Subject: Re: ncr[01] conflicts..? > > Here is a summary of how I got the tyan-1365(ncr825) and a GA ncr810 working on an asus p55tp4xe: 1. remove the rom from the 825. 2. put the 825 in the pci slot closest to the simms. 3. put the 810 in the media-bus slot on the other side. 4. set the "1'st/2'nd" jumper on the 810 to 2'nd 5. put boot drives on 810 It looks so simple, but took a month of fiddiling to get the right combo. Its amazing how a day or two off from work can bring new blood into the brain 8) I might mention that I was also trying to get slowaris2.5 fcs/sdk and freebsd boot from the same disk. Solaris does some really strange geometry translation, and likes to round cilinder boundaries. ...details on that solution available on request.. ps: you preaty much need a pentium-pro to run bloataris at the same comfort level as freebsd on a p100. Thanks for being patient.. Rob Mallory [rmallory@csusb.edu] From owner-freebsd-scsi Wed Dec 27 10:32:31 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA07010 for freebsd-scsi-outgoing; Wed, 27 Dec 1995 10:32:31 -0800 (PST) Received: from spanky.ov.com (spanky.pls.ov.com [198.153.190.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA07003 for ; Wed, 27 Dec 1995 10:32:26 -0800 (PST) Received: from sammy.pls.ov.com by spanky.ov.com with SMTP on Wed, 27 Dec 1995 10:32:15 -0800 Received: from bart.engr.master by sammy.pls.ov.com (5.0/SMI-SVR4) id AA25419; Wed, 27 Dec 1995 10:30:37 -0800 Received: by bart.engr.master (SMI-8.6/SMI-SVR4) id KAA02880; Wed, 27 Dec 1995 10:29:52 -0800 Date: Wed, 27 Dec 1995 10:29:52 -0800 From: radha@sammy.pls.ov.com (Radha) Message-Id: <199512271829.KAA02880@bart.engr.master> To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Md5: v3KwM2wAXukVDFsmHPPzqA== Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk subscribe radha@ov.com end From owner-freebsd-scsi Thu Dec 28 02:55:12 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA27646 for freebsd-scsi-outgoing; Thu, 28 Dec 1995 02:55:12 -0800 (PST) Received: from ncc-1701-d.starfleet.gov (root@ix-sb1-12.ix.netcom.com [204.32.201.44]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA27603 Thu, 28 Dec 1995 02:54:13 -0800 (PST) Received: (from d_burr@localhost) by ncc-1701-d.starfleet.gov (8.6.11/8.6.9) id CAA26981; Thu, 28 Dec 1995 02:57:21 -0800 Date: Thu, 28 Dec 1995 02:57:20 -0800 (PST) From: Donald Burr X-Sender: d_burr@ncc-1701-d To: FreeBSD Questions cc: FreeBSD SCSI Subject: VLB controllers: benefits? which one to buy? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk A friend of mine posed a question to me, which, quite frankly, I don't know the answer to. He currently has a 486DX2/66 with 16 MB of memory. The motherboard is ISA + VLB. His primary hard drive is a IBM 0662 (1 GB FAST SCSI-2 drive), and his controller is an Adaptec AHA-1542CP (same as the 1542CF, but with Plug and Play support). He runs both Windows 95 and FreeBSD 2.1-RELEASE. He was wondering if there was any real difference in performance between his ISA board (1542CP) and a VLB-based SCSI controller. Will it be faster, or is there not really a noticable difference? I remember back when I had IDE drives, when I switched from a 16-bit ISA to a 32-bit VLB IDE controller, I was not impressed with the (small) speed difference it gave me. But maybe SCSI is different? I don't really know, so I couldn't really answer his question myself. He also would like to know, out of curiosity, what VLB SCSI controllers would be the best to buy, and how much to expect to pay for one. Obviously it would have to be compatible with FreeBSD and Win95. He's not planning on getting a Pentium or PCI or whatnot any time soon, or else he said he'd probably get one of those NCR chips that everyone's talking about. Thanks for the assistance! Donald Burr [d_burr@ix.netcom.com], PO Box 91212, Santa Barbara CA 93190-1212 TEL (805)564-1871 / FAX 564-2315 / WWW http://www.geopages.com/WallStreet/2072 PGP Public Key available by request (send e-mail) or on Public Key Servers. ** Uphold your right to privacy - Use PGP. ** From owner-freebsd-scsi Thu Dec 28 04:36:56 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA02251 for freebsd-scsi-outgoing; Thu, 28 Dec 1995 04:36:56 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA02242 Thu, 28 Dec 1995 04:36:52 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id XAA02854; Thu, 28 Dec 1995 23:14:18 +1030 From: Michael Smith Message-Id: <199512281244.XAA02854@genesis.atrad.adelaide.edu.au> Subject: Re: VLB controllers: benefits? which one to buy? To: d_burr@ix.netcom.com (Donald Burr) Date: Thu, 28 Dec 1995 23:14:18 +1030 (CST) Cc: freebsd-questions@FreeBSD.org, freebsd-scsi@FreeBSD.org In-Reply-To: from "Donald Burr" at Dec 28, 95 02:57:20 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk Donald Burr stands accused of saying: > > He was wondering if there was any real difference in performance between > his ISA board (1542CP) and a VLB-based SCSI controller. Will it be > faster, or is there not really a noticable difference? Shitloads. > I remember back when I had IDE drives, when I switched from a 16-bit ISA > to a 32-bit VLB IDE controller, I was not impressed with the (small) > speed difference it gave me. But maybe SCSI is different? I don't > really know, so I couldn't really answer his question myself. The difference is very significant 8) > He also would like to know, out of curiosity, what VLB SCSI controllers > would be the best to buy, and how much to expect to pay for one. > Obviously it would have to be compatible with FreeBSD and Win95. The Adaptec 2842, Ultrastor 34F or Buslogic BT445 are the three worth considering. It's hard to compare them performance-wise; I'd just go for whichever he can get cheapest. > Donald Burr [d_burr@ix.netcom.com], PO Box 91212, Santa Barbara CA 93190-1212 -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[ From owner-freebsd-scsi Fri Dec 29 07:39:34 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA26092 for freebsd-scsi-outgoing; Fri, 29 Dec 1995 07:39:34 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA26078 for ; Fri, 29 Dec 1995 07:39:27 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA00600; Fri, 29 Dec 1995 16:39:17 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id QAA24764; Fri, 29 Dec 1995 16:39:15 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id QAA28321; Fri, 29 Dec 1995 16:31:37 +0100 (MET) From: J Wunsch Message-Id: <199512291531.QAA28321@uriah.heep.sax.de> Subject: Re: xcdplayer and SCSI Problem with Sony CDU-76S To: stu@solaris.com (Stu Phillips) Date: Fri, 29 Dec 1995 16:31:36 +0100 (MET) Cc: freebsd-bugs@freefall.freebsd.org, freebsd-scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512280221.SAA00201@solaris.cisco.com> from "Stu Phillips" at Dec 27, 95 06:21:01 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Stu Phillips wrote: > > cd0(bt0:4:0): ILLEGAL REQUEST asc:26,0 Invalid field in parameter list > The archives on freebsd.org suggested that this was due to SONY not following > the SCSI-II specs for CDROM audio - must confess, I found this hard to > accept especially since a generic SCSI CD player under Windows played CDs > just fine. > According to the SCSI-II spec (BTW, there is a great on-line copy of this > spec available at URL: http://abekas.com:8080/SCSI2/), in section 8.3.3, it > says that the medium field of the mode parameter header *may* be RESERVED > by some device types. > > The SONY CDU-076S returns this field as 0x03 on a MODE_SENSE but complains > if it is set to anything other than 0x00 on a MODE_SELECT. I still think Sony is in violation of the standard here. Below are the references i found in the SCSI-2 standard for it: First, the generic documentation says: "7.3.3. Mode Parameters ... Medium types are unique for each device type. Refer to the mode parameters section of the specific device type for definition of these values. Some device types reserve this field." Ok, not ``some devices'', but ``some device types''. That makes it pretty clear that either a device type reserves this field, or it doesn't. Anyway, it's IMHO _not_ up to a particular vendor (i.e., the sentence ain't ``Some implemenation may reserve this field.'') So, let's see what the CD-ROM device-type specification says: ... "13.3.3. Mode Parameters The medium-type code field is contained in the mode parameter header (see Table 7-61 and 7-62). Table 13-30 defines the medium type values for CD-ROM devices. Table 13-30: CD-ROM Medium Type Codes =================================================== Code Value Medium Type ------------ ------------------------------------- 00h Default (only one type supported) 01h 120 mm CD-ROM data only 02h 120 mm CD-DA audio only 03h 120 mm CD-ROM data and audio combined 04h Reserved 05h 80 mm CD-ROM data only 06h 80 mm CD-DA audio only 07h 80 mm CD-ROM data and audio combined 08h - 7Fh Reserved 80h - FFh Vendor unique ===================================================" I.e., it doesn't say that this is an optional parameter or something else. It seems logical that any device should accept the value for a MODE SELECT that it's just been responding by a MODE SENSE. The behaviour of the Sony is at least, ähem, strange. Anyway, i think your proposed change to use a medium type of 0 seems to be usable as a workaround for me, it doesn't contradict the sense of the current code (since the current algorithm was to use all parameters as reported by the drive, and only modify some distinct parameters at will). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Fri Dec 29 12:33:57 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA12036 for freebsd-scsi-outgoing; Fri, 29 Dec 1995 12:33:57 -0800 (PST) Received: from violet.berkeley.edu (violet.Berkeley.EDU [128.32.155.22]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA12030 for ; Fri, 29 Dec 1995 12:33:55 -0800 (PST) Received: by violet.berkeley.edu (8.7.1/1.33r) id MAA10781; Fri, 29 Dec 1995 12:33:54 -0800 Date: Fri, 29 Dec 1995 12:33:54 -0800 From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Message-Id: <199512292033.MAA10781@violet.berkeley.edu> To: freebsd-scsi@freebsd.org Subject: Leonard N. Zubkoff SCSI comments Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk Path: agate!overload.lbl.gov!lll-winken.llnl.gov!nntp.coast.net!news.sprintlink.net!news.clark.net!rahul.net!a2i!dandelion.com!not-for-mail From: "Leonard N. Zubkoff" Newsgroups: comp.unix.bsd.freebsd.misc,comp.periphs.scsi Subject: Re: SCSI-2 Bus Hangs Date: 29 Dec 1995 00:58:59 -0800 Organization: Dandelion Digital Lines: 28 Sender: lnz@dandelion.com Message-ID: <4c0akj$gi3@kelewan.dandelion.com> References: <4bju5p$ihj@wilma.widomaker.com> <4bp3bp$7cc@scratchy.mosquito.com> <1995Dec26.123518.1@spcvxb.spc.edu> <4brb07$b4q@uriah.heep.sax.de> <4bsu5j$eca@kelewan.dandelion.com> <4btpuu$555@uriah.heep.sax.de> NNTP-Posting-Host: dandelion.com NNTP-Posting-User: root In-reply-to: j@uriah.heep.sax.de's message of 28 Dec 1995 10:02:06 GMT Xref: agate comp.unix.bsd.freebsd.misc:13774 comp.periphs.scsi:54187 In article <4btpuu$555@uriah.heep.sax.de> j@uriah.heep.sax.de (J Wunsch) writes: "Leonard N. Zubkoff" writes: > FreeBSD drivers do this already since day 1. > Would you kindly point me to the code where the Bus Device Reset or SCSI > Bus Reset is initiated in FreeBSD? Sorry, i should have looked before. Actually, the timeout code is there, but not all adapter drivers do bus resets. I've seen it myself for the NCR driver. For the Adaptec 154X driver, this is the event chain that finally causes a timeout: Ahhh, I understand now. In the FreeBSD drivers everything is keyed off the timeout routine, and the driver is expected to abort the command the first time through, and graduate to a Bus Device Reset or SCSI Bus Reset as necessary. The BusLogic driver in bt.c doesn't implement any error recovery other than aborting a command, which is why I didn't find this. Perusing aic7xxx.c I see how this is handled. Thanks for the pointer. For reference, in Linux the driver provides two separate routines, one to handle aborting a command and the other to handle resets. In each case, the driver tells the mid level code what it actually did and the mid level code then takes appropriate action. If an abort also times out, then the reset code is invoked. Leonard From owner-freebsd-scsi Fri Dec 29 22:41:12 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA03054 for freebsd-scsi-outgoing; Fri, 29 Dec 1995 22:41:12 -0800 (PST) Received: from solaris.cisco.com (solaris.cisco.com [198.92.113.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA03048 for ; Fri, 29 Dec 1995 22:41:09 -0800 (PST) Received: (from stu@localhost) by solaris.cisco.com (8.6.12/8.6.9) id WAA03820; Fri, 29 Dec 1995 22:40:05 -0800 Date: Fri, 29 Dec 1995 22:40:05 -0800 From: Stu Phillips Message-Id: <199512300640.WAA03820@solaris.cisco.com> To: joerg_wunsch@uriah.heep.sax.de CC: freebsd-bugs@freefall.freebsd.org, freebsd-scsi@freebsd.org In-reply-to: <199512291531.QAA28321@uriah.heep.sax.de> (message from J Wunsch on Fri, 29 Dec 1995 16:31:36 +0100 (MET)) Subject: Re: xcdplayer and SCSI Problem with Sony CDU-76S Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk From: J Wunsch Date: Fri, 29 Dec 1995 16:31:36 +0100 (MET) Cc: freebsd-bugs@freefall.freebsd.org, freebsd-scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit I still think Sony is in violation of the standard here. Below are the references i found in the SCSI-2 standard for it: First, the generic documentation says: "7.3.3. Mode Parameters ... Medium types are unique for each device type. Refer to the mode parameters section of the specific device type for definition of these values. Some device types reserve this field." Ok, not ``some devices'', but ``some device types''. That makes it pretty clear that either a device type reserves this field, or it doesn't. Anyway, it's IMHO _not_ up to a particular vendor (i.e., the sentence ain't ``Some implemenation may reserve this field.'') So, let's see what the CD-ROM device-type specification says: ... "13.3.3. Mode Parameters The medium-type code field is contained in the mode parameter header (see Table 7-61 and 7-62). Table 13-30 defines the medium type values for CD-ROM devices. Table 13-30: CD-ROM Medium Type Codes =================================================== Code Value Medium Type ------------ ------------------------------------- 00h Default (only one type supported) 01h 120 mm CD-ROM data only 02h 120 mm CD-DA audio only 03h 120 mm CD-ROM data and audio combined 04h Reserved 05h 80 mm CD-ROM data only 06h 80 mm CD-DA audio only 07h 80 mm CD-ROM data and audio combined 08h - 7Fh Reserved 80h - FFh Vendor unique ===================================================" I.e., it doesn't say that this is an optional parameter or something else. It seems logical that any device should accept the value for a MODE SELECT that it's just been responding by a MODE SENSE. The behaviour of the Sony is at least, ähem, strange. Anyway, i think your proposed change to use a medium type of 0 seems to be usable as a workaround for me, it doesn't contradict the sense of the current code (since the current algorithm was to use all parameters as reported by the drive, and only modify some distinct parameters at will). Fully agree with you that it is STRANGE! However, think on this... the parameters in the audio page are specific to AUDIO capabilities - ie the SOTC is purely applicable to audio and irrelevant to data. I wonder wether setting the medium type to 0x02 would be accepted - I'll try it tomorrow. Not trying to defend SONY, however you must admit that its very wierd that the Windows application I tried (CorelScsi CDPlayer) works without any problems! Are you able to try this code change out on other CD drives ? If so and it works, are you able to commit the change ? Thanks! Stu From owner-freebsd-scsi Sat Dec 30 00:57:01 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA07788 for freebsd-scsi-outgoing; Sat, 30 Dec 1995 00:57:01 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA07782 for ; Sat, 30 Dec 1995 00:56:57 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA16998; Sat, 30 Dec 1995 09:56:56 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA03049; Sat, 30 Dec 1995 09:56:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA25319; Sat, 30 Dec 1995 09:55:35 +0100 (MET) From: J Wunsch Message-Id: <199512300855.JAA25319@uriah.heep.sax.de> Subject: Re: xcdplayer and SCSI Problem with Sony CDU-76S To: stu@solaris.com (Stu Phillips) Date: Sat, 30 Dec 1995 09:55:34 +0100 (MET) Cc: freebsd-bugs@freefall.freebsd.org, freebsd-scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512300640.WAA03820@solaris.cisco.com> from "Stu Phillips" at Dec 29, 95 10:40:05 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Stu Phillips wrote: > > Fully agree with you that it is STRANGE! However, think on this... the > parameters in the audio page are specific to AUDIO capabilities - ie the > SOTC is purely applicable to audio and irrelevant to data. I wonder > wether setting the medium type to 0x02 would be accepted - I'll try it > tomorrow. So perhaps they should also _return_ 0x02 in the MODE SENSE of the audio page? :) > Not trying to defend SONY, however you must admit that its very wierd > that the Windows application I tried (CorelScsi CDPlayer) works without > any problems! Of course, using 0 (current parameters) should always work. > Are you able to try this code change out on other CD drives ? If so and > it works, are you able to commit the change ? I will try it for my Toshiba, and yes, i'm going to commit the change if it's found to work. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Dec 30 05:52:03 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA18606 for freebsd-scsi-outgoing; Sat, 30 Dec 1995 05:52:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA18583 for ; Sat, 30 Dec 1995 05:51:57 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id OAA20740; Sat, 30 Dec 1995 14:51:53 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id OAA04396; Sat, 30 Dec 1995 14:51:52 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id OAA00360; Sat, 30 Dec 1995 14:28:48 +0100 (MET) From: J Wunsch Message-Id: <199512301328.OAA00360@uriah.heep.sax.de> Subject: Re: xcdplayer and SCSI Problem with Sony CDU-76S To: stu@solaris.com (Stu Phillips) Date: Sat, 30 Dec 1995 14:28:47 +0100 (MET) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-bugs@freefall.freebsd.org, freebsd-scsi@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199512300640.WAA03820@solaris.cisco.com> from "Stu Phillips" at Dec 29, 95 10:40:05 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Stu Phillips wrote: > > Are you able to try this code change out on other CD drives ? If so and > it works, are you able to commit the change ? It works on my Toshiba drive, and i think it's a safe change anyway, so i'm going to commit it. ¡muchas gracias! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Dec 30 08:50:04 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA24563 for freebsd-scsi-outgoing; Sat, 30 Dec 1995 08:50:04 -0800 (PST) Received: from solaris.cisco.com (solaris.cisco.com [198.92.113.34]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA24531 for ; Sat, 30 Dec 1995 08:49:58 -0800 (PST) Received: (from stu@localhost) by solaris.cisco.com (8.6.12/8.6.9) id IAA06073; Sat, 30 Dec 1995 08:48:58 -0800 Date: Sat, 30 Dec 1995 08:48:58 -0800 From: Stu Phillips Message-Id: <199512301648.IAA06073@solaris.cisco.com> To: joerg_wunsch@uriah.heep.sax.de CC: joerg_wunsch@uriah.heep.sax.de, freebsd-bugs@freefall.freebsd.org, freebsd-scsi@freebsd.org In-reply-to: <199512301328.OAA00360@uriah.heep.sax.de> (message from J Wunsch on Sat, 30 Dec 1995 14:28:47 +0100 (MET)) Subject: Re: xcdplayer and SCSI Problem with Sony CDU-76S Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk It works on my Toshiba drive, and i think it's a safe change anyway, so i'm going to commit it. muchas gracias! -- cheers, J"org You are most welcome! Its my one visible bug fix for the year :-) I'm the Vice-President of Central Engineering (Software mostly) at Cisco in my day job.... Nice to know there is still life in the horse yet! I'm still a died in the wool techno-geek so I hack on shareware and FreeBSD in my spare (!) time! Thanks for trying out the change and delighted to hear it works! Stu