From owner-freebsd-hardware Sun Apr 26 18:04:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15203 for freebsd-hardware-outgoing; Sun, 26 Apr 1998 17:57:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smarty.telcel.net.ve (t-mon.t-net.net.ve [206.48.41.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14733 for ; Sun, 26 Apr 1998 17:52:21 -0700 (PDT) (envelope-from rinunez@telcel.net.ve) Received: from telcel.telcel.net.ve ([206.49.129.118]) by smarty.telcel.net.ve (Post.Office MTA v3.1 release 0154 ID# 557-42303U60000L60000S0) with ESMTP id AAA10275 for ; Sun, 26 Apr 1998 20:45:58 -0400 From: "=?ISO-8859-1?Q?Ricardo_Manuel_N=FA=F1ez_Chirino?=" To: "FreeBSD Hardware" Subject: Parallel Port Zip FreeBSD Drive Date: Sun, 26 Apr 1998 20:52:45 -0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <19980427004556.AAA10275@telcel.telcel.net.ve> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Gentlemen, I was installing Mr. Nicolas Souchu´s Parallel Port Zip FreeBSD Drive... I have FreeBSD 2.2.1, 32 MB RAM, Pentium-S 133 MHz. I was doing what the README file says, but I´m having some problems in the installation: > - Copy the ppbus directory to /sys/dev/ No problem. I copied exactly to /sys/dev/ppbus/ > - Copy the files in the isa directory to /sys/i386/isa No problem > - Edit /sys/conf/files, and add: (...) OK. No problem > - Edit /sys/i386/conf/files.i386, and add (...) OK. No problem >- An example of the /sys/i386/conf/MACHINE file: > > controller scbus0 # SCSI stuff > device sd0 > > controller ppbus0 # ppbus stuff > controller vpo0 at ppbus0 # Iomega ZIP support > device nlpt0 at ppbus0 # printer support > device ppi0 at ppbus0 # ppbus interface > #device plip0 at ppbus0 # PLIP support > > controller ppc0 at isa? port? irq 7 vector ppcintr > > #controller ppa0 at isa? port 0x378 # Obsolete > #device lpt0 at isa? port? tty # Obsolete Here´s my first doubt... Is he saying that I should add these lines to my "RINUNEZ" file to rebuild my kernel inmediately after this step??? I named my kernel file selfishly "RINUNEZ" . What I really did was just make the "MACHINE" file and go on with the other steps. >- Add the following line to /sys/i386/i386/userconfig.c: > {"ppc", "Parallel port chipset", 0, CLS_COMMS}, I noticed that´s a C file, but that line is not a legal statement in C language... Is it all right??? > - add the special device nodes to /dev: > > mknod /dev/ppi0 c 82 0 > mknod /dev/ppi1 c 82 1 ... OK. >Modules >------- > > ppimod directory contains the Makefile of /sys/dev/ppbus/ppi.c module. I run "make" over the ppbimod directory, but it doesn´t work. I append the output (stderr and stdout at the end of this note). >Boot flags >---------- > bits 0,1,2,3: > chipset's mode (see ppbconf.h) > bit 4: > 0 -> EPP 1.9 protocol > 1 -> EPP 1.7 protocol > bit 5: > 0 -> consider interrupts > 1 -> ignore interrupts I have no idea what this part means. Yours faithfully and thank you very much, Ricardo Nunez rinunez@telcel.net.ve P.S.: The output of make: Warning: Object directory not changed from original /usr/home/rinunez/discozip/ppbus-dist.971125/ppimod cc -O -nostdinc -I/sys -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/home/rinunez/discozip/ppbus-dist.971125/ppimod/../../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -c /sys/dev/ppbus/ppi.c *** Error code 1 Stop. function `ppi_mod': /sys/dev/ppbus/ppi.c:242: `_module' undeclared (first use this function) /sys/dev/ppbus/ppi.c:242: (Each undeclared identifier is reported only once /sys/dev/ppbus/ppi.c:242: for each function it appears in.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 26 19:02:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21116 for freebsd-hardware-outgoing; Sun, 26 Apr 1998 19:00:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cain.gsoft.com.au (italia.lnk.telstra.net [139.130.136.161] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21003; Sun, 26 Apr 1998 18:59:43 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA19236; Mon, 27 Apr 1998 11:25:39 +0930 (CST) Message-Id: <199804270155.LAA19236@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: Bruce Evans , dburr@POBoxes.com, hardware@FreeBSD.ORG, stable@FreeBSD.ORG, Studded@san.rr.com Subject: Re: best wdc0 flags ? In-reply-to: Your message of "Fri, 24 Apr 1998 18:08:35 MST." <199804250108.SAA02337@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Apr 1998 11:25:39 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Ok. Do we have general consensus then that the defaults should be: > > - 32-bit transfers. > - multi-block 4, if supported by the drive. > ??? Well, I have this and it works fine.. I have a old 540mB Caviar which worked fine with this setup (up until Friday when I got a new drive..) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 26 20:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28200 for freebsd-hardware-outgoing; Sun, 26 Apr 1998 20:18:10 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from trantor.galaxia.com (terminus.galaxia.com [204.255.210.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27936 for ; Sun, 26 Apr 1998 20:16:40 -0700 (PDT) (envelope-from dave@galaxia.com) Received: from localhost (dave@localhost) by trantor.galaxia.com (8.8.7/8.8.7) with SMTP id XAA10164 for ; Sun, 26 Apr 1998 23:16:28 -0400 (EDT) (envelope-from dave@galaxia.com) Date: Sun, 26 Apr 1998 23:16:26 -0400 (EDT) From: "David H. Brierley" To: freebsd-hardware@FreeBSD.ORG Subject: SupraExpress 336i pnp modem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope this is the right list for this. It seems like a hardware related question to me. Someone gave me a SupraExpress 336i PnP modem and I was hoping to maybe be able to use it in my FreeBSD box. Does anyone know if this thing can be used successfully in FreeBSD or is this something along the lines of the dreaded "winmodem" cards? I am currently running FreeBSD 2.2.5 on the machine but am willing to upgrade if required. I did not receive any software of any kind with the card, so if there is some kind of program to disable the PnP features I would need to either have some kind soul send me a copy or point me to somewhere I can download it from. Thank in advance, -- David H. Brierley dave@galaxia.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 02:20:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26293 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 02:20:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mph124b.rh.psu.edu (MPH124B.rh.psu.edu [128.118.126.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26283 for ; Mon, 27 Apr 1998 02:20:44 -0700 (PDT) (envelope-from gsutter@pobox.com) From: gsutter@pobox.com Received: from localhost (gsutter@localhost) by mph124b.rh.psu.edu (8.8.7/8.8.8) with SMTP id FAA26940 for ; Mon, 27 Apr 1998 05:20:42 -0400 (EDT) (envelope-from gsutter@pobox.com) Date: Mon, 27 Apr 1998 05:20:38 -0400 (EDT) X-Sender: gsutter@mph124b.rh.psu.edu To: freebsd-hardware@FreeBSD.ORG Subject: Re: SupraExpress 336i pnp modem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 26 Apr 1998, David H. Brierley wrote: >Someone gave me a SupraExpress 336i PnP modem and I was hoping to >maybe be able to use it in my FreeBSD box. Does anyone know if >this thing can be used successfully in FreeBSD or is this something >along the lines of the dreaded "winmodem" cards? I am currently >running FreeBSD 2.2.5 on the machine but am willing to upgrade if >required. I did not receive any software of any kind with the >card, so if there is some kind of program to disable the PnP features >I would need to either have some kind soul send me a copy or point >me to somewhere I can download it from. The Supra Express are indeed winmodems, I'm sorry to say. You can download DoS/windoze software at , but I don't know if there is a PnP-disabler included. GReg -- Gregory S. Sutter "How do I read this file?" mailto:gsutter@pobox.com "You uudecode it." http://www.pobox.com/~gsutter/ "I I I decode it?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 07:05:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17295 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 07:05:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17278 for ; Mon, 27 Apr 1998 07:05:15 -0700 (PDT) (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id JAA21442; Mon, 27 Apr 1998 09:04:45 -0500 (CDT) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199804271404.JAA21442@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: gsutter@pobox.com cc: freebsd-hardware@FreeBSD.ORG From: Glenn Johnson Subject: Re: SupraExpress 336i pnp modem In-reply-to: Your message of "Mon, 27 Apr 1998 05:20:38 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Apr 1998 09:04:44 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 26 Apr 1998, David H. Brierley wrote: > > >Someone gave me a SupraExpress 336i PnP modem and I was hoping to > >maybe be able to use it in my FreeBSD box. Does anyone know if > >this thing can be used successfully in FreeBSD or is this something > >along the lines of the dreaded "winmodem" cards? I am currently > >running FreeBSD 2.2.5 on the machine but am willing to upgrade if > >required. I did not receive any software of any kind with the > >card, so if there is some kind of program to disable the PnP features > >I would need to either have some kind soul send me a copy or point > >me to somewhere I can download it from. > > The Supra Express are indeed winmodems, I'm sorry to say. You can > download DoS/windoze software at , but I don't > know if there is a PnP-disabler included. > > GReg I have a SupraExpress 336i PnP modem on my home FreeBSD machine. It was bought about a year ago and it is most definitely *NOT* a winmodem. Have they changed this? As far as I know you can't disable PnP because that is how you set the port and IRQ. This is not a problem however unless you have to change the settings, in which case you can use the DOS utility or use the PnP features of FreeBSD 2.2.6 (don't ask me how though, I've never done it). If your BIOS is a PnP bios it might tell you what the settings are at boot time (mine does this) and you can just plug these into FreeBSD at the boot -c screen. My settings for instance are sio2 (COM3 in DOS-speak) and IRQ 11. These were the out-of-the-box settings of the modem (your's may be differnet) and they work fine for me. IMHO this is an excellent modem, unless they have changed the design since I bought mine. In short, this modem does work well with FreeBSD. Let me know if you need further assistance. -- Glenn Johnson Technician USDA-ARS-SRRC Phone: (504) 286-4252 1100 Robert E. Lee Boulevard FAX: (504) 286-4217 New Orleans, LA 70124 e-mail: gjohnson@nola.srrc.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 09:25:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14572 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 09:25:42 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14547; Mon, 27 Apr 1998 09:25:31 -0700 (PDT) (envelope-from dirk.vangulik@jrc.it) Received: from elec.isei.jrc.it (elec.jrc.it [139.191.71.132]) by mrelay.jrc.it (LMC5688) with SMTP id SAA18897; Mon, 27 Apr 1998 18:25:26 +0200 (MET DST) Received: from elect6 by elec.isei.jrc.it (4.1/EI-3.0m) id AA21928; Mon, 27 Apr 98 18:25:34 +0200 Posted-Date: Mon, 27 Apr 1998 18:21:49 +0200 (MET DST) Date: Mon, 27 Apr 1998 18:21:49 +0200 (MET DST) From: Dirk-Willem van Gulik X-Sender: dirkx@elect6 Reply-To: Dirk-Willem van Gulik To: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Cc: dirk.vangulik@jrc.it Subject: VAIO 505 and FreeBSD 2.2.5/PAO In-Reply-To: <199804271605.JAA10308@hub.freebsd.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to all who have helped me in the last few days; and to make up for all your time I wasted; I've put all your tips and tricks onto http://www.webweaving.org/vaio/ which is a rough and ready guide to getting FreeBSD-2.2.x, PAO and X11 to work on a VAIO-505 (when you have just the Japanese manuals to guide you...:-) Tx! Dw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 09:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18346 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 09:40:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18051 for ; Mon, 27 Apr 1998 09:39:01 -0700 (PDT) (envelope-from uzsv2k@IBM.rhrz.uni-bonn.de) Received: from uni-bonn.de (131.220.225.105,1033) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Mon, 27 Apr 98 18:38:54 MEZ Message-ID: <3544A9B5.79F9EB28@uni-bonn.de> Date: Mon, 27 Apr 1998 17:52:21 +0200 From: Philipp Reichmuth X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: TCP/IP over SCSI? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Could one, in theory, implement a driver that talks TCP/IP over SCSI? Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 12:02:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14740 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 12:02:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14727 for ; Mon, 27 Apr 1998 12:02:47 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA11576; Mon, 27 Apr 1998 11:55:57 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd011574; Mon Apr 27 18:55:57 1998 Message-ID: <3544D375.59E2B600@whistle.com> Date: Mon, 27 Apr 1998 11:50:30 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Philipp Reichmuth CC: hardware@FreeBSD.ORG Subject: Re: TCP/IP over SCSI? References: <3544A9B5.79F9EB28@uni-bonn.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Philipp Reichmuth wrote: > > Could one, in theory, implement a driver that talks TCP/IP over SCSI? > > Philipp > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message. yes you could (it's been discussed a lot) but it's not really a good match and you'd have to have an adapter that supports 'target mode' correctly. most of them don't as it's rarely used. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 12:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18855 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 12:26:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18777 for ; Mon, 27 Apr 1998 12:25:43 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA15085; Mon, 27 Apr 1998 21:25:17 +0200 (CEST) To: Philipp Reichmuth cc: hardware@FreeBSD.ORG Subject: Re: TCP/IP over SCSI? In-reply-to: Your message of "Mon, 27 Apr 1998 17:52:21 +0200." <3544A9B5.79F9EB28@uni-bonn.de> Date: Mon, 27 Apr 1998 21:25:17 +0200 Message-ID: <15083.893705117@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3544A9B5.79F9EB28@uni-bonn.de>, Philipp Reichmuth writes: >Could one, in theory, implement a driver that talks TCP/IP over SCSI? Yes, see RFC2143 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 12:48:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22880 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 12:48:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (root@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22854 for ; Mon, 27 Apr 1998 12:48:08 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id MAA00254; Mon, 27 Apr 1998 12:47:35 -0700 Message-ID: <3544E0D7.5912577D@feral.com> Date: Mon, 27 Apr 1998 12:47:35 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: Philipp Reichmuth CC: hardware@FreeBSD.ORG Subject: Re: TCP/IP over SCSI? References: <3544A9B5.79F9EB28@uni-bonn.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Could one, in theory, implement a driver that talks TCP/IP over SCSI? Of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 14:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13796 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 14:32:33 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13777 for ; Mon, 27 Apr 1998 14:32:11 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0.Beta6/frmug-2.3/nospam) with UUCP id XAA12935 for hardware@FreeBSD.ORG; Mon, 27 Apr 1998 23:31:38 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id WAA05952; Mon, 27 Apr 1998 22:39:57 +0200 (CEST) (envelope-from roberto) Message-ID: <19980427223957.A5886@keltia.freenix.fr> Date: Mon, 27 Apr 1998 22:39:57 +0200 From: Ollivier Robert To: hardware@FreeBSD.ORG Subject: Re: TCP/IP over SCSI? Mail-Followup-To: hardware@FreeBSD.ORG References: <3544A9B5.79F9EB28@uni-bonn.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <3544A9B5.79F9EB28@uni-bonn.de>; from Philipp Reichmuth on Mon, Apr 27, 1998 at 05:52:21PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4245 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Philipp Reichmuth: > Could one, in theory, implement a driver that talks TCP/IP over SCSI? There is an RFC for that. Don't remember the # though. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #8: Tue Apr 21 02:45:53 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 27 15:47:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00454 for freebsd-hardware-outgoing; Mon, 27 Apr 1998 15:47:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mph124b.rh.psu.edu (MPH124B.rh.psu.edu [128.118.126.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00372 for ; Mon, 27 Apr 1998 15:47:40 -0700 (PDT) (envelope-from gsutter@pobox.com) From: gsutter@pobox.com Received: from localhost (gsutter@localhost) by mph124b.rh.psu.edu (8.8.7/8.8.8) with SMTP id SAA29613; Mon, 27 Apr 1998 18:47:16 -0400 (EDT) (envelope-from gsutter@pobox.com) Date: Mon, 27 Apr 1998 18:47:14 -0400 (EDT) X-Sender: gsutter@mph124b.rh.psu.edu To: Glenn Johnson cc: freebsd-hardware@FreeBSD.ORG Subject: Re: SupraExpress 336i pnp modem In-Reply-To: <199804271404.JAA21442@symbion.srrc.usda.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 27 Apr 1998, Glenn Johnson wrote: >> On Sun, 26 Apr 1998, David H. Brierley wrote: >> >Someone gave me a SupraExpress 336i PnP modem and I was hoping to >> >maybe be able to use it in my FreeBSD box. Does anyone know if >> >this thing can be used successfully in FreeBSD or is this something >> >along the lines of the dreaded "winmodem" cards? I am currently >> The Supra Express are indeed winmodems, I'm sorry to say. You can >> download DoS/windoze software at , but I don't >> know if there is a PnP-disabler included. >I have a SupraExpress 336i PnP modem on my home FreeBSD machine. It was >bought about a year ago and it is most definitely *NOT* a winmodem. Hmm, mine was a 288i that was upgraded to a 336i; it was a winmodem. Maybe the models aren't internally consistent; I can hardly see them making the original 288is as winmodems and then having the 336is as full-fledged modems. At any rate, to the original poster, I'd advise checking the chipset (and maybe calling Supra / Diamond and asking) to see if your modem is a winmodem. Regards, GReg -- Gregory S. Sutter "How do I read this file?" mailto:gsutter@pobox.com "You uudecode it." http://www.pobox.com/~gsutter/ "I I I decode it?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 28 02:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04432 for freebsd-hardware-outgoing; Tue, 28 Apr 1998 02:29:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04395 for ; Tue, 28 Apr 1998 02:28:51 -0700 (PDT) (envelope-from schofiel@xs4all.nl) Received: from diamond.xs4all.nl (enterprise.xs4all.nl [194.109.14.215]) by smtp1.xs4all.nl (8.8.8/8.8.8) with SMTP id LAA27608 for ; Tue, 28 Apr 1998 11:28:49 +0200 (MET DST) Message-Id: <3.0.5.32.19980428113336.007a1470@mail.xs4all.nl> X-Sender: schofiel@mail.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 28 Apr 1998 11:33:36 +0200 To: freebsd-hardware@FreeBSD.ORG From: Rob Schofield Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > Philipp Reichmuth wrote: > > > > Could one, in theory, implement a driver that talks TCP/IP over SCSI? > > > > Philipp > > > yes you could (it's been discussed a lot) > but it's not really a good match and you'd ^^^^^^^^^^ Surely this is: Ethernet is a bursty, bandwidth hogger with short "connection" times, unsuited to the SCSI model of bus operation? You need to read the RFC for TCP/IP over SCSI transport, which covers this. > have to have an adapter that supports 'target mode' correctly. NO, sorry, but the adaptors usually *do*, as it's built into the chipsets (otherwise how would your SCSI disks work as targets? ;^). As usual, it's the **host software** that doesn't. Even then, if you are using the ASPI generalisation layer provided/sold by Adaptec, a lot of what you need for target mode is in there. Don't generalise, please. Rob Schofield To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 28 07:24:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01920 for freebsd-hardware-outgoing; Tue, 28 Apr 1998 07:24:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01906 for ; Tue, 28 Apr 1998 07:24:04 -0700 (PDT) (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id JAA01801; Tue, 28 Apr 1998 09:23:47 -0500 (CDT) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199804281423.JAA01801@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: gsutter@pobox.com cc: freebsd-hardware@FreeBSD.ORG, dave@galaxia.com From: Glenn Johnson Subject: Re: SupraExpress 336i pnp modem In-reply-to: Your message of "Mon, 27 Apr 1998 18:47:14 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Apr 1998 09:23:47 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Mon, 27 Apr 1998, Glenn Johnson wrote: > > >I have a SupraExpress 336i PnP modem on my home FreeBSD machine. It was > >bought about a year ago and it is most definitely *NOT* a winmodem. > > Hmm, mine was a 288i that was upgraded to a 336i; it was a winmodem. > Maybe the models aren't internally consistent; I can hardly see them > making the original 288is as winmodems and then having the 336is as > full-fledged modems. > This is very interesting. Perhaps Diamond saw the error of their ways. Hmm, wasn't Supra an independant company that was bought by Diamond? I wonder if that is a factor. -- Glenn Johnson Technician USDA-ARS-SRRC Phone: (504) 286-4252 1100 Robert E. Lee Boulevard FAX: (504) 286-4217 New Orleans, LA 70124 e-mail: gjohnson@nola.srrc.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 28 14:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09352 for freebsd-hardware-outgoing; Tue, 28 Apr 1998 14:19:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09097 for ; Tue, 28 Apr 1998 14:17:56 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA22816; Tue, 28 Apr 1998 14:13:07 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd022807; Tue Apr 28 21:13:04 1998 Message-ID: <35464515.41C67EA6@whistle.com> Date: Tue, 28 Apr 1998 14:07:33 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Rob Schofield CC: freebsd-hardware@FreeBSD.ORG Subject: Re: References: <3.0.5.32.19980428113336.007a1470@mail.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rob Schofield wrote: > NO, sorry, but the adaptors usually *do*, as it's built into the > chipsets (otherwise how would your SCSI disks work as targets? ;^) I did not say 'devices', I said "adapters".. Host adapters is what I obviously meant, and the host adpters and their drivers don't support it, so we'd have to add that support.. When I wrote the SCSI subsystem (yes I know how it works) I tried to leave 'hooks' for target mode, but none of the adapters supported it so the drivers couldn't do it. the 1542 managed to HALF support it for a while. ok? >. As > usual, it's the **host software** that doesn't. Even then, if you are using > the ASPI generalisation layer provided/sold by Adaptec, a lot of what you > need for target mode is in there. we are NOT using it as they won't give source.. and 'MOST' is not enough. They were totally unable to get target mode working correctly on their 154x series and I have no reason to believe that they have spent more energy on new series. > > Don't generalise, please. ok the adapter drivers don't usually support it, but in addition those cards that are "intelligent" usually fail to support it correctly in their firmware as well. The firmware on most cards is usually UNTESTED in target mode. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 28 15:14:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21846 for freebsd-hardware-outgoing; Tue, 28 Apr 1998 15:14:36 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21824 for ; Tue, 28 Apr 1998 15:14:22 -0700 (PDT) (envelope-from luomat@luomat.peak.org) Received: (from luomat@localhost) by luomat.peak.org (8.8.8/8.8.8) id SAA27631 for freebsd-hardware@FreeBSD.ORG; Tue, 28 Apr 1998 18:14:08 -0400 (EDT) Message-Id: <199804282214.SAA27631@luomat.peak.org> Content-Type: text/plain MIME-Version: 1.0 From: Timothy J Luoma Date: Tue, 28 Apr 98 18:14:04 -0400 To: freebsd-hardware@FreeBSD.ORG Subject: FBSD on 386 acting as a router? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just found out that they are giving away old 386's at my school tomorrow. I don't know anything about them, other than that they are 386's (and have a monitor/keyboard/hard drive). a) how likely is it that I could actually get this machine to install FreeBSD? b) could it handle being a router/firewall to a two-machine lan (behind a cable modem)? If this were a 486 I'd be relatively comfortable of my chances..... TjL ps -- how much HD space do I need for a basic system (commandline, no X stuff) to handle NATD? Thanks for any help at all.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 28 17:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21104 for freebsd-hardware-outgoing; Tue, 28 Apr 1998 17:34:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bytetech.com (bytetech.com [204.186.19.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21092 for ; Tue, 28 Apr 1998 17:34:27 -0700 (PDT) (envelope-from gene@bytetech.com) Received: from localhost (gene@localhost) by bytetech.com (8.8.3/8.8.3) with SMTP id UAA04078 for ; Tue, 28 Apr 1998 20:34:31 -0400 (EDT) Date: Tue, 28 Apr 1998 20:34:31 -0400 (EDT) From: Eugene L Ehrhart Reply-To: Eugene L Ehrhart To: "'hardware@freebsd.org'" Subject: scsi tape drives Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Does anyone have a Seagate Tapestor tape drive model# STT2 z8000n-r running sucessfully on FreeBSD ver. 2.1.6?? Thanks Gene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 28 18:48:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05971 for freebsd-hardware-outgoing; Tue, 28 Apr 1998 18:48:04 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05829 for ; Tue, 28 Apr 1998 18:47:40 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA02064; Tue, 28 Apr 1998 18:39:21 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002062; Wed Apr 29 01:39:15 1998 Message-ID: <3546837A.1CFBAE39@whistle.com> Date: Tue, 28 Apr 1998 18:33:46 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Timothy J Luoma CC: freebsd-hardware@FreeBSD.ORG Subject: Re: FBSD on 386 acting as a router? References: <199804282214.SAA27631@luomat.peak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Timothy J Luoma wrote: > > I just found out that they are giving away old 386's at my school tomorrow. > > I don't know anything about them, other than that they are 386's (and have a > monitor/keyboard/hard drive). > > a) how likely is it that I could actually get this machine to install FreeBSD? > > b) could it handle being a router/firewall to a two-machine lan (behind a > cable modem)? > > If this were a 486 I'd be relatively comfortable of my chances..... > > TjL > > ps -- how much HD space do I need for a basic system (commandline, no X > stuff) to handle NATD? > > Thanks for any help at all.... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message It'l work fine. you can even get one with no hard drive and it will work fine the 'picoBSD' project has a single floppy see http://www.freebsd.org/~abial/ you'll need 8MB of RAM and 2 ethernet cards ($40 each these days) it may even be possible to make it work with LESS ram than that. you may even be able to boot it off the network with NO floppy and less ram if you can get your hands on the right enet cards and a eprom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 01:59:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00295 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 01:59:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from blik1.samara.su (blik1.samara.su [194.58.210.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00286 for ; Wed, 29 Apr 1998 01:59:07 -0700 (PDT) (envelope-from ip@blik1.samara.su) Received: (from ip@localhost) by blik1.samara.su (8.8.7/8.8.7) id NAA17654 for freebsd-hardware@freebsd.org; Wed, 29 Apr 1998 13:59:27 +0500 (KSD) (envelope-from ip) Date: Wed, 29 Apr 98 13:59:27 +0500 From: ip@blik1.samara.su (ip) To: freebsd-hardware@FreeBSD.ORG Message-ID: References: <199804290455.VAA15795@hub.freebsd.org> Subject: Re:driver for Dialogic bords X-Mailer: BML [UNIX Beauty Mail v.1.39] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Where I can find drivers and libraries for Dialogic boards (under freebsd) ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 04:18:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01441 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 04:18:48 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.artcom.de ([192.76.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01426 for ; Wed, 29 Apr 1998 04:18:44 -0700 (PDT) (envelope-from hans@artcom.de) Received: by mail.artcom.de id m0yUUsX-000008C; Wed, 29 Apr 1998 13:18:21 +0200 (MEST) Message-Id: Date: Wed, 29 Apr 1998 13:18:21 +0200 (MEST) From: hans@artcom.de (Hans Huebner) To: luomat+Lists/FreeBSD/Hardware@luomat.peak.org Subject: Re: FBSD on 386 acting as a router? Newsgroups: artcom.mailing-list.freebsd.hardware In-Reply-To: <199804282214.SAA27631@luomat.peak.org> Organization: Art+Com GmbH, Berlin, Germany Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199804282214.SAA27631@luomat.peak.org> you write: >I just found out that they are giving away old 386's at my school tomorrow. >I don't know anything about them, other than that they are 386's (and have a >monitor/keyboard/hard drive). >a) how likely is it that I could actually get this machine to install FreeBSD? This depends on the amount of RAM the machines have. With 4 MB, you'll need a custom kernel. Apart from that, there should be no problem - I booted 2.2.6-R on a 386sx yesterday, and it behaved as expected (i.e. SLOW). >b) could it handle being a router/firewall to a two-machine lan (behind a >cable modem)? Yes. >ps -- how much HD space do I need for a basic system (commandline, no X >stuff) to handle NATD? None. It will even work with PicoBSD (which boots from a single 1.44 MB floppy). See http://www.freebsd.org/~abial/ -Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 07:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08718 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 07:15:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08693 for ; Wed, 29 Apr 1998 07:15:06 -0700 (PDT) (envelope-from nash@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (nash@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id JAA21967; Wed, 29 Apr 1998 09:15:06 -0500 (CDT) Received: from localhost (nash@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id JAA12967; Wed, 29 Apr 1998 09:15:05 -0500 (CDT) Date: Wed, 29 Apr 1998 09:15:05 -0500 (CDT) From: Alex Nash To: ip cc: freebsd-hardware@FreeBSD.ORG Subject: Re:driver for Dialogic bords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Apr 1998, ip wrote: > Where I can find drivers and libraries for Dialogic boards (under freebsd) ? You can't. Dialogic isn't interested in "supporting free software." We've already attempted to get documentation out of them to write out own drivers, but they're not interested. You might try doing the same -- the more they get requests, the more likely they are to do something. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 07:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10703 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 07:21:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10695 for ; Wed, 29 Apr 1998 07:21:52 -0700 (PDT) (envelope-from schofiel@xs4all.nl) Received: from diamond.xs4all.nl (enterprise.xs4all.nl [194.109.14.215]) by smtp1.xs4all.nl (8.8.8/8.8.8) with SMTP id QAA13622 for ; Wed, 29 Apr 1998 16:21:51 +0200 (MET DST) Message-ID: <3547389F.121E@xs4all.nl> Date: Wed, 29 Apr 1998 16:26:39 +0200 From: Rob Schofield Reply-To: schofiel@xs4all.nl X-Mailer: Mozilla 3.04Gold (Win95; I) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Ooops - sorry Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian, I suspect I may well have grievously offended you. If this is the case, I apologise, as it was not the intention to do so (late at night, half-busy with work). I hope you can forgive me - certainly cheesed up everything else in that letter! As regards my comments on SCSI: >Rob Schofield wrote: >> NO, sorry, but the adaptors usually *do*, as it's built into the >> chipsets (otherwise how would your SCSI disks work as targets? ;^) > >I did not say 'devices', I said "adapters".. And, if you look carefully, neither did I; Adaptec (before and after they bought the rest of the market) have always been in the background business of selling SCSI controller chip sets to the world, so that 3rd parties can go ahead and manufacture disk controllers, for example. Think of IBM, SEAGATE, etc. plus anyone else wanting a highly integrated SCSI-subsytem on a chip. *In a second line of business*, they also manufacture host adaptors for PCs and other bus-based computers. This is probably far more visible to the buying public. NCR did the opposite, ie. sell chipsets visibly. Under Adaptec, they now sell boards too, which are just re-branded. The chipsets Adaptec sell/use have got the capability to operate either as SCSI Host or SCSI Target, and carry out a lot of the bus bit bashing previously done in software using a hardware state machine. The mode is not hard-coded by a jumper, but determined by the software driving the chip. This you will know from writing a SCSI subsystem; I have a dead Seagate and an HP drive in front of me with ADAPTEC writ large across many of the chips on the PCB of the disk controller. > Host adapters is what I > obviously meant, Yes, I agree, but I equally obviously badly wrote the reply assuming you would catch onto what I meant - that the chipsets can operate as targets as well as hosts, in fact they *have to*. > and the host adpters and their drivers don't > support it, so we'd have to add that support.. Ah, now I can correct you here; I have successfully worked on two PC-based projects where a 1510 and a 1740 were used in target mode, so the *hardware at least* does. Whether, as you rightly say, the PC- based BIOS provided with these cards actually implements this mode or not (and for any other SCSI device class other than Disk, at that) is another question; we didn't use it - simply disabled the BIOS, got a register map and the right data sheet for the chips on the cards, and wrote our own drivers, which were then successfully tested under the operating system we were using (OS-9000). >When I wrote the SCSI subsystem (yes I know how it works) Yeah, I've done that too, a few times ;^). I've done a high-res medical colour printer, a disk driver for multihost co-operative disk sharing (fun, that one) and an electronically steered, medical Ultra-sound scanner for heart arteries that thought it was a disk drive. So yes, I know how they work too. >I tried to leave 'hooks' for target mode, but none of the adapters >supported it so the drivers couldn't do it. the 1542 managed to >HALF support it for a while. I have no idea what implementation method you were using for this, but it would still boil down to getting a register address map for the chipset, an address map for the host card from the manufacturer (Adaptec were quite happy to let us have the developer docs when we asked) and getting down to it. Whether the host adapter circuitry is designed to allow full use of the chipset's capabilities is a different matter, and I can't comment for the 1542; however, the ISA part (the bus interface) of this card had some definite limitations, which you may have hit against. If I hear another anguished story about "ISA Bus Mastering" I will scream - that was why EISA appeared... >>. As >> usual, it's the **host software** that doesn't. Even then, if you are using >> the ASPI generalisation layer provided/sold by Adaptec, a lot of what you >> need for target mode is in there. >we are NOT using it as they won't give source.. No defintiely, they won't *give* you the ASPI sources for their commercially available, main income source. Would you? ;^) However, if you asked them for the developer's packages and ASPI specs, well, they'll let you have that. Maybe I was just lucky when I asked, I got all my stuff for free in '95.... >and 'MOST' is not enough. ... but it could form the solid basis of an good, original piece of work performed by you, based on commercially-accepted standards? What do you want them to do, write it all for you? >They were totally unable to get target >mode working correctly on their 154x series and I have no reason >to believe that they have spent more energy on new series. ... on Windows 3.1 systems without multi-threading capability (for which ASPI was designed), on an otherwise simple card with a bad bus interface. They have done much better, recently... >> >> Don't generalise, please. > >ok the adapter drivers don't usually support it, but in addition >those cards that are "intelligent" usually fail to support it >correctly in their firmware as well. The firmware on most cards is >usually UNTESTED in target mode. And since the cards are usually designed and marketed for a PC market, why should they possibly want Target mode operation *in the drivers and firmware* ??? 99.999999% of people using the interface cards would only care enough to plug it in, connect disks, and use them for that! So why should Adaptec (or others) waste time and development money on generalised, properly tested multi-mode support software if no-one going to ever even use it? It's *no wonder* the stuff's untested, and is only suitable for disks. Tell me, why use the firmware? I thought this was U**X? Why on earth do you need to use the card firmware? >julian Rob Schofield M.Sc. (SCSI software developer) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 09:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08266 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 09:33:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise-atm.cs.unm.edu [198.83.90.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08233 for ; Wed, 29 Apr 1998 09:33:45 -0700 (PDT) (envelope-from cfaehl@cs.unm.edu) Received: from avarice.cs.unm.edu [198.83.92.131] by enterprise.cs.unm.edu with esmtp (Exim 1.80 #2) id 0yUZnl-0005IJ-00; Wed, 29 Apr 1998 10:33:45 -0600 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hardware@FreeBSD.ORG Subject: Numbers/Densities for ARCHIVE Python 04106-XXX 715G Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Apr 1998 10:33:42 -0600 From: Chris Faehl Message-Id: Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to obtain 'optimal' settings for a Seagate DDS-3 drive, ARCHIVE Python 04106-XXX 715G. Kernel (2.2.6, btw) sez: ahc0:A:6: refuses WIDE negotiation. Using 8bit transfers (ahc0:6:0): "ARCHIVE Python 04106-XXX 715G" type 1 removable SCSI 2 'mt -f /dev/rst0 status' sez: Present Mode: Density = 0x25 Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = X3.136-1986 Blocksize = 512 bytes Mode 2: Density = X3.39-1986 Blocksize variable Mode 3: Density = X3.54-1986 Blocksize variable I'm not finding any corresponding info for density = 0x25 on a man mt, nor do I find any corresponding values in . What to do? I'd like to have access to compressed devices, none of the modes appear relevant. I'm a little confused about where I should specify density values - and what values I should use. Is this enough info to get a coherent answer? Or am I omitting some vital info? And, does anyone know what bpi this device supports? Seagate's docs are, um, suboptimal. I scanned the mail archives and the FAQ/Handbook, to no avail. ------------------------------------------------------------------------------- Chris Faehl | Email: cfaehl@cs.unm.edu The University of New Mexico | URL: http://www.cs.unm.edu/~cfaehl Computer Science Dept., Rm. FEC 313 | Phone: 505/277-3016 Albuquerque, NM 87131 USA | FAX: 505/277-6927 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 13:07:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17128 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 13:07:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17120 for ; Wed, 29 Apr 1998 13:07:44 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA26118; Wed, 29 Apr 1998 13:00:55 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026115; Wed Apr 29 20:00:53 1998 Message-ID: <354785AB.63DECDAD@whistle.com> Date: Wed, 29 Apr 1998 12:55:23 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: schofiel@xs4all.nl CC: freebsd-hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry References: <3547389F.121E@xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rob Schofield wrote: > > Julian, I suspect I may well have grievously offended you. If this is > the case, I apologise, as it was not the intention to do so (late at > night, half-busy with work). I hope you can forgive me - certainly > cheesed up everything else in that letter! no worries.. > > As regards my comments on SCSI: [says that the chipsets themselves can support both target and initiator modes] well, yes of course. and those cards that are based on a raw chip can do it. the drivers hopwever are not likely to be heavily tested in target mode if they support it at all. > Ah, now I can correct you here; I have successfully worked on two > PC-based projects where a 1510 and a 1740 were used in target mode, so > the *hardware at least* does. Whether, as you rightly say, the > PC- based BIOS provided with these cards actually implements this > mode or not (and > for any other SCSI device class other than Disk, at that) is another > question; we didn't use it - simply disabled the BIOS, got a register > map and the right data sheet for the chips on the cards, and wrote our > own drivers, which were then successfully tested under the operating > system we were using (OS-9000). t it, so we'd have to add that support.. > the 1510 was a card that was ony suitable for low load applications (or dedicated use) because the processor had to do an aweful lot of work for it's data. Of course as it was chip-level you could do anything with the driver. The 1540 (or 1520) series was more suitable as they added a coprocessor to do all the hard work. The firmware that this processor ran was capable of doing some target mode work but they broke that feature regularly and didn't always notice. ;-( As you could not bypass the coprocessor, if they didn't do target mode correctly, neither did you. The 1740 was supposed to support target mode too, but we eventually gave up on them ever getting it to work correctly. (talk to peter dufault on this). It was like the 1540 in that it had a coprocessor, but they never got the target mode reliable during the time that we tried to use it. They eventually told us that they were going to stop saying that they supported target mode on that and that we should stop asking them to fix it. Rumour was that there was one release of the firmware that worked, but they quickly corrected that oversight and we could never get one. Once again since you couldn't bypass the coprocessor you were dependent on it doing it correctly. Peter had changes to the SCSI system to make allowances for target mode operation of adapters, but as we couldn't get any adapters that could actually do it at that time (1993?) we never checked them in. > [...] > >we are NOT using it as they won't give source.. > > No defintiely, they won't *give* you the ASPI sources for their > commercially available, main income source. Would you? ;^) However, if > you asked them for the developer's packages and ASPI specs, well, > they'll let you have that. Maybe I was just lucky when I asked, I got > all my stuff for free in '95.... > > >and 'MOST' is not enough. > > ... but it could form the solid basis of an good, original piece > of work performed by you, based on commercially-accepted > standards? What do you want them to do, write it all for you? With the new CAM based system that Justin is working on, there may be an oportunity to make better use of externally written modules. [...] > > Tell me, why use the firmware? I thought this was U**X? Why on earth do > you need to use the card firmware? > Only on intelligent cards where the firmware is executed by the coprocessor. Since the advent of efficient chip-level solutions such as the adaptec and NCR/symbios/adaptec (??) chips it depends more on the drivers and we are freed of the firmware (thank god) but we still need to have people working on them who want and need target mode because of course even if the state-machines support target mode, we never use/test it. I'm basically out of the SCSI business these days. We don't use it here and I don't have the time anyhow. Justin is now the person doing all the work and he has made an engineering decision that in the long run freeBSD is better served by rewriting the SCSI system to be based on CAM rather than trying to patch the old one more. I guess that there will eventually be someone who wants to patch target mode into the CAM based version and I'm sure that Justin will have made allowances for that. (CAM supports it, so his implimentation should at least have the hooks in the right places for it) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 16:44:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07334 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 16:44:41 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06924 for ; Wed, 29 Apr 1998 16:42:42 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id RAA28319; Wed, 29 Apr 1998 17:38:27 -0600 (MDT) Date: Wed, 29 Apr 1998 17:38:27 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199804292338.RAA28319@narnia.plutotech.com> To: schofiel@xs4all.nl cc: hardware@FreeBSD.ORG Subject: Re: Ooops - sorry Newsgroups: pluto.freebsd.hardware In-Reply-To: <3547389F.121E@xs4all.nl> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <3547389F.121E@xs4all.nl> you wrote: > The chipsets Adaptec sell/use have got the capability to operate either > as SCSI Host or SCSI Target, and carry out a lot of the bus bit bashing > previously done in software using a hardware state machine. The mode is > not hard-coded by a jumper, but determined by the software driving the > chip. This you will know from writing a SCSI subsystem; I have a dead > Seagate and an HP drive in front of me with ADAPTEC writ large across > many of the chips on the PCB of the disk controller. The parts Adaptec sells to device vendors are designed for target applications only. They are rarely the same parts that are developed for HBAs. Adaptec has a long history of "providing" for target mode in their HBA chips, but never testing it. My understanding is that they did develop target mode drivers for the aic7880 internally and they sell them to certain third party integrators, but other than this development and the support for target mode in the 1542B (result of a NASA contract I believe), Adaptec has rarely supported target mode for their HBAs. Even today I received some mail from a fellow who developed a target mode driver for the 2944 (differential 2940) and found out that there was a bug in this card that caused problems for target mode that Adaptec was unwilling to fix. He did get a "cut this line, insert jumper here" kind of solution from them, but it was fairly obvious that they never tested the target mode features of their differential products. > Ah, now I can correct you here; I have successfully worked on two > PC-based projects where a 1510 and a 1740 were used in target mode, so > the *hardware at least* does. Whether, as you rightly say, the PC- based > BIOS provided with these cards actually implements this mode or not (and > for any other SCSI device class other than Disk, at that) is another > question; we didn't use it - simply disabled the BIOS, got a register > map and the right data sheet for the chips on the cards, and wrote our > own drivers, which were then successfully tested under the operating > system we were using (OS-9000). You were very lucky that the hardware worked as specified. > I have no idea what implementation method you were using for this, but > it would still boil down to getting a register address map for the > chipset, an address map for the host card from the manufacturer (Adaptec > were quite happy to let us have the developer docs when we asked) and > getting down to it. Whether the host adapter circuitry is designed to > allow full use of the chipset's capabilities is a different matter, and > I can't comment for the 1542; however, the ISA part (the bus interface) > of this card had some definite limitations, which you may have hit > against. If I hear another anguished story about "ISA Bus Mastering" I > will scream - that was why EISA appeared... For many applications, doing all of the protocol management from the kernel is simply too slow. Luckily many of the newer chips allow you to write and download your own firmware so you can provide target mode yourself if the vendor doesn't support. I need to be able to saturate a wide Ultra2 connection (80MB/s) for the target mode applications I'm interrested in. >>we are NOT using it as they won't give source.. > > No defintiely, they won't *give* you the ASPI sources for their > commercially available, main income source. Would you? ;^) However, if > you asked them for the developer's packages and ASPI specs, well, > they'll let you have that. Maybe I was just lucky when I asked, I got > all my stuff for free in '95.... ASPI is too inflexible. That is why it was not chosen as the spec for the new FreeBSD SCSI layer. We're implementing CAM instead. > Tell me, why use the firmware? I thought this was U**X? Why on earth do > you need to use the card firmware? If you don't perform some onboard processing, you will never achieve the maximum performance that adapter can provide. Remember also that Firmware != BIOS. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 20:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19426 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 20:29:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from elvis.mu.org (elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19335 for ; Wed, 29 Apr 1998 20:28:28 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (8.8.8/8.8.8) id WAA03739; Wed, 29 Apr 1998 22:28:28 -0500 (CDT) (envelope-from paul) Message-ID: <19980429222828.A3680@mu.org> Date: Wed, 29 Apr 1998 22:28:28 -0500 From: Paul Saab To: hardware@FreeBSD.ORG Subject: anyone using IBM-34560W Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone using the IBM-34560W? I am thinking of getting one of these and wanted to know if anyone has had any experience with them. Thanks, paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 23:03:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13223 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 23:03:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tandem.milestonerdl.com (main.milestonerdl.com [204.107.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13204 for ; Wed, 29 Apr 1998 23:03:37 -0700 (PDT) (envelope-from marc@tandem.milestonerdl.com) Received: (from marc@localhost) by tandem.milestonerdl.com (8.8.4/8.8.4) id BAA23776; Thu, 30 Apr 1998 01:15:42 GMT Date: Thu, 30 Apr 1998 01:15:41 +0000 () From: Marc Rassbach To: ip cc: freebsd-hardware@FreeBSD.ORG Subject: Re:driver for Dialogic bords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, if Diallogic won't play nice with 'us' 'opensource' people, who is close to Dialogic who *WILL* play nice? On Wed, 29 Apr 1998, ip wrote: > Where I can find drivers and libraries for Dialogic boards (under freebsd) ? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 29 23:10:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14050 for freebsd-hardware-outgoing; Wed, 29 Apr 1998 23:10:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles358.castles.com [208.214.167.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13934 for ; Wed, 29 Apr 1998 23:09:59 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00527; Wed, 29 Apr 1998 22:06:58 -0700 (PDT) Message-Id: <199804300506.WAA00527@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Paul Saab cc: hardware@FreeBSD.ORG Subject: Re: anyone using IBM-34560W In-reply-to: Your message of "Wed, 29 Apr 1998 22:28:28 CDT." <19980429222828.A3680@mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Apr 1998 22:06:58 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is anyone using the IBM-34560W? I am thinking of getting one of > these and wanted to know if anyone has had any experience with > them. You don't say which family it is (there is a 4-letter prefix that isn't "IBM"). We have been using the DCAS-34330W units for some time now with no trouble at all; current IBM disk models seem to offer excellent price:performance:reliability triples. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 30 00:32:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25334 for freebsd-hardware-outgoing; Thu, 30 Apr 1998 00:32:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from elvis.mu.org (elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25329 for ; Thu, 30 Apr 1998 00:32:19 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (8.8.8/8.8.8) id CAA07743; Thu, 30 Apr 1998 02:32:01 -0500 (CDT) (envelope-from paul) Message-ID: <19980430023200.A7661@mu.org> Date: Thu, 30 Apr 1998 02:32:00 -0500 From: Paul Saab To: Mike Smith Cc: hardware@FreeBSD.ORG Subject: Re: anyone using IBM-34560W References: <19980429222828.A3680@mu.org> <199804300506.WAA00527@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199804300506.WAA00527@antipodes.cdrom.com>; from Mike Smith on Wed, Apr 29, 1998 at 10:06:58PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith (mike@smith.net.au) wrote: > > Is anyone using the IBM-34560W? I am thinking of getting one of > > these and wanted to know if anyone has had any experience with > > them. > > You don't say which family it is (there is a 4-letter prefix that isn't > "IBM"). We have been using the DCAS-34330W units for some time now > with no trouble at all; current IBM disk models seem to offer excellent > price:performance:reliability triples. DDRS is the family. I have many DCAS-34330W drives too and love them. The DDRS are a little faster etc and I thought I would give them a try. On another note, how much is everyone that buy's the DCAS pay for them? I get mine for around $260-270. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 30 03:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14396 for freebsd-hardware-outgoing; Thu, 30 Apr 1998 03:11:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14387 for ; Thu, 30 Apr 1998 03:11:15 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA14359; Thu, 30 Apr 1998 06:06:39 -0400 (EDT) From: Peter Dufault Message-Id: <199804301006.GAA14359@hda.hda.com> Subject: Re: [Target Mode] Was: Ooops - sorry In-Reply-To: <354785AB.63DECDAD@whistle.com> from Julian Elischer at "Apr 29, 98 12:55:23 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 30 Apr 1998 06:06:38 -0400 (EDT) Cc: schofiel@xs4all.nl, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The 1740 was supposed to support target mode too, but we > eventually gave up on them ever getting it to work correctly. > (talk to peter dufault on this). They documented the 1740 interface in the manuals, sold it through pre-sales, it was buggy as could be (dropped a mailbox slot each time it received something and so hung up after 16 transfers, etc), they flailed trying to fix it and finally wrote a letter saying "Adaptec does not support target mode on any of their host adapters". It "worked" enough that it took several weeks of wasting time, finding and proving firmware bugs, getting fixes, finding firmware bugs, ... before finally giving up. Grrr. I switched to a Vesalogic board with an NCR chip for that project. The scripting was done using NCR SCSI SCRIPTS for an embedded system and never went into FreeBSD. As Julian says later on, I decided you had to go to the "chip merchants" and not the PC board merchants for target mode - at a cold hearted level you can't blame them for not spending engineering resources on such a small market. > It was like the 1540 in that it had a coprocessor, but they > never got the target mode reliable during the time that we > tried to use it. They eventually told us that they were going to > stop saying that they supported target mode on that and that we > should stop asking them to fix it. > > Rumour was that there was one release of the firmware that > worked, but they quickly corrected that oversight and we could never > get one. Once again since you couldn't bypass the coprocessor > you were dependent on it doing it correctly. They never had it working. The 1542B was sold to some OEM and so they made it work. They probably had similar nibbles for the 174x and so planned it but never put the resources into making it work. > Peter had changes to the SCSI system to make allowances for target > mode operation of adapters, but as we couldn't get any adapters > that could actually do it at that time (1993?) we never checked them > in. No, they are in there for the 1542B If you boot verbose with a 1542B with the correct firmware rev it will say ", target ops". Last time I tried it it worked but it could be rotted by now. Even if it is rotted it is simple enough that someone who needed it and had a 1542B could get it working quickly. Basically, you configure a target device wiring down the ID and LUN, open it, and then "dd" from it. It will disconnect and you'll get an interrupt with the transfer request direction and size when an initiator tries to access it. It doesn't support scatter gather so you need contiguous memory, etc, etc. Even with these restrictions it worked fine developing a big system. > I guess that there will eventually be someone who wants to patch > target mode into the CAM based version and I'm sure that Justin will > have made allowances for that. (CAM supports it, so his > implimentation should at least have the hooks in the right places > for it) I've had three calls about this in the last six months including one this month, so interest is picking up. I've given them Justin's and Stefan's e-mail addresses and told them "have PO will work" (in the July time frame though). We'll see if anything comes out of it. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 30 07:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19570 for freebsd-hardware-outgoing; Thu, 30 Apr 1998 07:49:26 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (root@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19555 for ; Thu, 30 Apr 1998 07:49:20 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id HAA05984; Thu, 30 Apr 1998 07:46:54 -0700 Message-ID: <35488EDD.41B464CF@feral.com> Date: Thu, 30 Apr 1998 07:46:53 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: Peter Dufault CC: Julian Elischer , schofiel@xs4all.nl, freebsd-hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry References: <199804301006.GAA14359@hda.hda.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org btw- the Qlogic boards (ISP 10X0 and 2100 for Fibre Channel) *do* have a pretty decent target mode in f/w- but I haven't ever tried to turn it on and use it- I've had reports from their use on NT && Solaris that it works fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 30 19:28:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07525 for freebsd-hardware-outgoing; Thu, 30 Apr 1998 19:28:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07489 for ; Thu, 30 Apr 1998 19:28:25 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt3-210.HiWAAY.net [208.147.146.210]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id VAA26631; Thu, 30 Apr 1998 21:28:22 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id TAA17811; Thu, 30 Apr 1998 19:56:10 -0500 (CDT) Message-Id: <199805010056.TAA17811@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" cc: hardware@FreeBSD.ORG From: David Kelly Subject: Re: Ooops - sorry In-reply-to: Message from "Justin T. Gibbs" of "Wed, 29 Apr 1998 17:38:27 MDT." <199804292338.RAA28319@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Apr 1998 19:56:09 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" writes: > Adaptec has a long history of "providing" for target mode > in their HBA chips, but never testing it. My understanding is that > they did develop target mode drivers for the aic7880 internally and > they sell them to certain third party integrators, but other than > this development and the support for target mode in the 1542B (result > of a NASA contract I believe), Adaptec has rarely supported target > mode for their HBAs. The Young Minds, Inc. CD-Studio was/is a 486 MB with custom BIOS and at least one 1542. There was another card in the machine but I don't remember if the 1542 or the other card was connected to the workstation end. One SCSI bus went to your workstation/PC/Mac, the other went to a HD and CD-R. The CD-Studio emulated an Exabyte 8200 on a couple of LUN's. One was to control the CD-Studio functions, another was for the CD-R, another for the dedicated HD, and still another for a Rimage CD printer. Probably yet another LUN for a robot for automated duplication. The more I think about it, the more I'm certian the 1542 connected to HD and CD-R. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 1 03:14:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27070 for freebsd-hardware-outgoing; Fri, 1 May 1998 03:14:07 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27063 for ; Fri, 1 May 1998 03:14:03 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA17055; Fri, 1 May 1998 06:09:20 -0400 (EDT) From: Peter Dufault Message-Id: <199805011009.GAA17055@hda.hda.com> Subject: Re: [Target Mode] Was: Ooops - sorry In-Reply-To: <35488EDD.41B464CF@feral.com> from Matthew Jacob at "Apr 30, 98 07:46:53 am" To: mjacob@feral.com (Matthew Jacob) Date: Fri, 1 May 1998 06:09:20 -0400 (EDT) Cc: dufault@hda.com, julian@whistle.com, schofiel@xs4all.nl, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > btw- the Qlogic boards (ISP 10X0 and 2100 for Fibre > Channel) *do* have a pretty decent target mode in f/w- > but I haven't ever tried to turn it on and use it- I've > had reports from their use on NT && Solaris that it > works fine. I just looked at my docs - the board we used was an Acculogic Vesaport and not a "Vesalogic" board. Sorry. The Buslogic folk (who I think have since been bought out by Adaptec) had working firmware on their 1542 clone board and seemed as if they would go the extra mile to make other things work, with higher level sales people showing up and strong statements from the company. However, at that point an NCR based board with everything under our control seemed the only sure thing. I guess that "NCR" / Symbios are now owned by Adaptec as well, but as long as they are selling chips to Qlogic, Acculogic, etc those smaller companies will be hungry enough to sell into the Linux / FreeBSD / embedded systems market. The other place to look for known working boards is to see what vendors such as QNX support. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 1 08:21:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28279 for freebsd-hardware-outgoing; Fri, 1 May 1998 08:21:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (root@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28266 for ; Fri, 1 May 1998 08:21:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id IAA08549; Fri, 1 May 1998 08:18:35 -0700 Message-ID: <3549E7CB.75A9EFFD@feral.com> Date: Fri, 01 May 1998 08:18:35 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: Peter Dufault CC: julian@whistle.com, schofiel@xs4all.nl, freebsd-hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry References: <199805011009.GAA17055@hda.hda.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Dufault wrote: > > as long as they are selling chips to Qlogic, Wrong. Qlogic is still it's own company. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 1 09:38:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08945 for freebsd-hardware-outgoing; Fri, 1 May 1998 09:38:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp2.mailsrvcs.net (smtp2.gte.net [207.115.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08936 for ; Fri, 1 May 1998 09:38:22 -0700 (PDT) (envelope-from orthoefe@gte.net) Received: from moltar.oshea.lan (1Cust50.tnt1.tampa2.fl.da.uu.net [208.251.99.50]) by smtp2.mailsrvcs.net with SMTP id LAA03322 for ; Fri, 1 May 1998 11:37:55 -0500 (CDT) Date: Fri, 1 May 1998 12:41:24 -0400 (EDT) From: Joe Orthoefer X-Sender: orthoefe@moltar.oshea.lan To: freebsd-hardware@FreeBSD.ORG Subject: compaq "dual host" pci archetecture Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1598452307-894040654=:6670" Content-ID: Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1598452307-894040654=:6670 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: I have access to a compaq 5500 that has 8 pci slots. The first four slots and the last four slots, according to compaq's sales literature are each behind their own host to pci bridge chip. When booting freebsd it recognizes and scans only one of the pci busses, though it sees both of the host to pci bridge chips. Are there allowances for such a configuration in the current pci layer? --0-1598452307-894040654=:6670 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=compac_boot Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dGV4dD0weGY3MDAwIGRhdGE9MHgxMTAwMCBic3M9MHgyMDViOCBzeW1ib2xz PVsrMHhhNDgrMHg0KzB4MTIzMDArMHg0KzB4MTk3YjJdDQp0b3RhbD0weDI1 NGFiYSBlbnRyeSBwb2ludD0weDEwMDAwMA0KQklPUyBiYXNlbWVtICg2MzhL KSAhPSBSVEMgYmFzZW1lbSAoNjQwSyksIHNldHRpbmcgdG8gQklPUyB2YWx1 ZQ0KQ29weXJpZ2h0IChjKSAxOTkyLTE5OTggRnJlZUJTRCBJbmMuDQpDb3B5 cmlnaHQgKGMpIDE5ODIsIDE5ODYsIDE5ODksIDE5OTEsIDE5OTMNCiAgICAg ICAgVGhlIFJlZ2VudHMgb2YgdGhlIFVuaXZlcnNpdHkgb2YgQ2FsaWZvcm5p YS4gQWxsIHJpZ2h0cyByZXNlcnZlZC4NCkZyZWVCU0QgMy4wLTk4MDQyOC1T TkFQICM1OiBGcmkgQXVnIDI4IDExOjM2OjQyIEdNVCAxOTk4DQogICAgcm9v dEBkcmFnby5sYWJsYW4uY29tOi91c3Ivc3JjL3N5cy9jb21waWxlL0RSQUdP DQpDYWxpYnJhdGluZyBjbG9jayhzKSAuLi4gVFNDIGNsb2NrOiAxOTk2OTAy MTQgSHosIGk4MjU0IGNsb2NrOiAxMTkzMjQwIEh6DQpDTEtfVVNFX0k4MjU0 X0NBTElCUkFUSU9OIG5vdCBzcGVjaWZpZWQgLSB1c2luZyBkZWZhdWx0IGZy ZXF1ZW5jeQ0KVGltZWNvdW50ZXIgImk4MjU0IiAgZnJlcXVlbmN5IDExOTMx ODIgSHogIGNvc3QgNTA3NCBucw0KQ0xLX1VTRV9UU0NfQ0FMSUJSQVRJT04g bm90IHNwZWNpZmllZCAtIHVzaW5nIG9sZCBjYWxpYnJhdGlvbiBtZXRob2QN ClRpbWVjb3VudGVyICJUU0MiICBmcmVxdWVuY3kgMTk5NjgyMjIyIEh6ICBj b3N0IDI5NCBucw0KQ1BVOiBQZW50aXVtIFBybyAoMTk5LjY4LU1IeiA2ODYt Y2xhc3MgQ1BVKQ0KICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAgSWQgPSAw eDYxOSAgU3RlcHBpbmc9OQ0KICBGZWF0dXJlcz0weGY5ZmY8RlBVLFZNRSxE RSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxTRVAsTVRSUixQR0UsTUNBLENN T1Y+DQpyZWFsIG1lbW9yeSAgPSA2NzEwODg2NCAoNjU1MzZLIGJ5dGVzKQ0K UGh5c2ljYWwgbWVtb3J5IGNodW5rKHMpOg0KMHgwMDAwMTAwMCAtIDB4MDAw OWVmZmYsIDY0NzE2OCBieXRlcyAoMTU4IHBhZ2VzKQ0KMHgwMDIzNTAwMCAt IDB4MDNmZmRmZmYsIDY0Nzg2NDMyIGJ5dGVzICgxNTgxNyBwYWdlcykNCmF2 YWlsIG1lbW9yeSA9IDYyNzMwMjQwICg2MTI2MEsgYnl0ZXMpDQpGb3VuZCBC SU9TMzIgU2VydmljZSBEaXJlY3RvcnkgaGVhZGVyIGF0IDB4ZjAwZmZlZTAN CkVudHJ5ID0gMHhmMDAwMCAoMHhmMDBmMDAwMCkgIFJldiA9IDAgIExlbiA9 IDENClBDSSBCSU9TIGVudHJ5IGF0IDB4NzANCk90aGVyIEJJT1Mgc2lnbmF0 dXJlcyBmb3VuZDoNCkFDUEk6IDAwMDAwMDAwDQokUG5QOiAwMDAwMDAwMA0K ZWlzYTA6IDxDUFE1NjEgKFN5c3RlbSBCb2FyZCk+DQpQcm9iaW5nIGZvciBk ZXZpY2VzIG9uIHRoZSBFSVNBIGJ1cw0KcGNpX29wZW4oMSk6ICAgIG1vZGUg MSBhZGRyIHBvcnQgKDB4MGNmOCkgaXMgMHgwMDAwMDAwMA0KcGNpX29wZW4o MWEpOiAgIG1vZGUxcmVzPTB4ODAwMDAwMDAgKDB4ODAwMDAwMDApDQpwY2lf Y2ZnY2hlY2s6ICAgZGV2aWNlIDAgW2NsYXNzPTA2MDAwMF0gW2hkcj0wMF0g aXMgdGhlcmUgKGlkPTAwMDUxMTY2KQ0KUHJvYmluZyBmb3IgZGV2aWNlcyBv biBQQ0kgYnVzIDA6DQpmb3VuZC0+IHZlbmRvcj0weDExNjYsIGRldj0weDAw MDUsIHJldmlkPTB4MDINCiAgICAgICAgY2xhc3M9MDYtMDAtMDAsIGhkcnR5 cGU9MHgwMCwgbWZkZXY9MA0KY2hpcDA6IDxIb3N0IHRvIFBDSSBicmlkZ2Ug KHZlbmRvcj0xMTY2IGRldmljZT0wMDA1KT4gcmV2IDB4MDIgb24gcGNpMC4w LjANCmZvdW5kLT4gdmVuZG9yPTB4MTAxMywgZGV2PTB4MDBhMCwgcmV2aWQ9 MHgyMg0KICAgICAgICBjbGFzcz0wMy0wMC0wMCwgaGRydHlwZT0weDAwLCBt ZmRldj0wDQogICAgICAgIGludHBpbj1hLCBpcnE9MjU1DQogICAgICAgIG1h cFswXTogdHlwZSAzLCByYW5nZSAzMiwgYmFzZSBjMjAwMDAwMCwgc2l6ZSAy NA0KdmdhMDogPENpcnJ1cyBMb2dpYyBHRDU0MzAgU1ZHQSBjb250cm9sbGVy PiByZXYgMHgyMiBpbnQgYSBpcnEgMjU1IG9uIHBjaTAuNi4wDQpmb3VuZC0+ IHZlbmRvcj0weDBlMTEsIGRldj0weGEwZWMsIHJldmlkPTB4MDMNCiAgICAg ICAgY2xhc3M9MDItODAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MA0KICAg ICAgICBpbnRwaW49YSwgaXJxPTUNCiAgICAgICAgbWFwWzBdOiB0eXBlIDQs IHJhbmdlIDMyLCBiYXNlIDAwMDA1MDAwLCBzaXplICA4DQogICAgICAgIG1h cFsxXTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwNTQwMCwgc2l6ZSAg OA0KICAgICAgICBtYXBbMl06IHR5cGUgMSwgcmFuZ2UgMzIsIGJhc2UgYzNm ZmZlMDAsIHNpemUgIDkNCmZvdW5kLT4gdmVuZG9yPTB4MGUxMSwgZGV2PTB4 MDAwMSwgcmV2aWQ9MHgwNw0KICAgICAgICBjbGFzcz0wNi0wMi0wMCwgaGRy dHlwZT0weDAwLCBtZmRldj0wDQpjaGlwMTogPFBDSSB0byBFSVNBIGJyaWRn ZSAodmVuZG9yPTBlMTEgZGV2aWNlPTAwMDEpPiByZXYgMHgwNyBvbiBwY2kw LjE1LjANCmZvdW5kLT4gdmVuZG9yPTB4MTE2NiwgZGV2PTB4MDAwNSwgcmV2 aWQ9MHgwMg0KICAgICAgICBjbGFzcz0wNi0wMC0wMCwgaGRydHlwZT0weDAw LCBtZmRldj0wDQpjaGlwMjogPEhvc3QgdG8gUENJIGJyaWRnZSAodmVuZG9y PTExNjYgZGV2aWNlPTAwMDUpPiByZXYgMHgwMiBvbiBwY2kwLjE3LjANClBy b2JpbmcgZm9yIGRldmljZXMgb24gdGhlIElTQSBidXM6DQpzYzA6IHRoZSBj dXJyZW50IGtleWJvYXJkIGNvbnRyb2xsZXIgY29tbWFuZCBieXRlIDAwNjUN CmtiZGlvOiBESUFHTk9TRSBzdGF0dXM6MDA1NQ0Ka2JkaW86IFRFU1RfS0JE X1BPUlQgc3RhdHVzOjAwMDANCmtiZGlvOiBSRVNFVF9LQkQgcmV0dXJuIGNv ZGU6MDBmYQ0Ka2JkaW86IFJFU0VUX0tCRCBzdGF0dXM6MDBhYQ0Kc2MwIGF0 IDB4NjAtMHg2ZiBpcnEgMSBvbiBtb3RoZXJib2FyZA0Kc2MwOiBCSU9TIHZp ZGVvIG1vZGU6Mw0Kc2MwOiBWR0EgcmVnaXN0ZXJzIHVwb24gcG93ZXItdXAN CjUwIDE4IDEwIDAwIDEwIDAwIDAzIDAwIDAyIDY3IDVmIDRmIDUwIDgyIDU1 IDgxIA0KYmYgMWYgMDAgNGYgMGQgMGUgMDAgMDAgMDcgMzAgOWMgOGUgOGYg MjggMWYgOTYgDQpiOSBhMyBmZiAwMCAwMSAwMiAwMyAwNCAwNSAxNCAwNyAz OCAzOSAzYSAzYiAzYyANCjNkIDNlIDNmIDBjIDAwIDBmIDA4IDAwIDAwIDAw IDAwIDAwIDEwIDBlIDAwIGZmIA0Kc2MwOiB2aWRlbyBtb2RlOjI0DQpzYzA6 IFZHQSByZWdpc3RlcnMgaW4gQklPUyBmb3IgbW9kZToyNA0KNTAgMTggMTAg MDAgMTAgMDAgMDMgMDAgMDIgNjcgNWYgNGYgNTAgODIgNTUgODEgDQpiZiAx ZiAwMCA0ZiAwZCAwZSAwMCAwMCAwMCAwMCA5YyA4ZSA4ZiAyOCAxZiA5NiAN CmI5IGEzIGZmIDAwIDAxIDAyIDAzIDA0IDA1IDE0IDA3IDM4IDM5IDNhIDNi IDNjIA0KM2QgM2UgM2YgMGMgMDAgMGYgMDggMDAgMDAgMDAgMDAgMDAgMTAg MGUgMDAgZmYgDQpzYzA6IFZHQSByZWdpc3RlcnMgdG8gYmUgdXNlZCBmb3Ig bW9kZToyNA0KNTAgMTggMTAgMDAgMTAgMDAgMDMgMDAgMDIgNjcgNWYgNGYg NTAgODIgNTUgODEgDQpiZiAxZiAwMCA0ZiAwZCAwZSAwMCAwMCAwMCAwMCA5 YyA4ZSA4ZiAyOCAxZiA5NiANCmI5IGEzIGZmIDAwIDAxIDAyIDAzIDA0IDA1 IDE0IDA3IDM4IDM5IDNhIDNiIDNjIA0KM2QgM2UgM2YgMGMgMDAgMGYgMDgg MDAgMDAgMDAgMDAgMDAgMTAgMGUgMDAgZmYgDQpzYzA6IHJvd3Nfb2Zmc2V0 OjENCnNjMDogVkdBIGNvbG9yIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFn cz0weDA+DQplZDAgbm90IGZvdW5kIGN1OiBHb3QgDQo= --0-1598452307-894040654=:6670 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=pci_scanned Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: UENJIHNheXMgY29uZmlndXJhdGlvbiB0eXBlIDENCg0KUENJIHByb2Jpbmcg Y29uZmlndXJhdGlvbiB0eXBlIDENCg0KcGNpIGJ1cyAweDAgY2FyZG51bSAw eDAwLCB2ZW5kb3IgMHgxMTY2IGRldmljZSAweDAwMDUNCiBEZXZpY2UgdW5r bm93bg0KIFNUQVRVUyAweDIyMDAgQ09NTUFORCAweDAxNDYNCiBDTEFTUyAw eDA2IDB4MDAgMHgwMCBSRVZJU0lPTiAweDAyDQogQklTVCAweDAwIEhFQURF UiAweDAwIExBVEVOQ1kgMHg0MCBDQUNIRSAweDA4DQoNCnBjaSBidXMgMHgw IGNhcmRudW0gMHgwNiwgdmVuZG9yIDB4MTAxMyBkZXZpY2UgMHgwMGEwDQog Q2lycnVzIExvZ2ljICBEZXZpY2UgdW5rbm93bg0KIFNUQVRVUyAweDAyMDAg Q09NTUFORCAweDAwMDMNCiBDTEFTUyAweDAzIDB4MDAgMHgwMCBSRVZJU0lP TiAweDIyDQogQkFTRTAgMHhjMjAwMDAwOCBhZGRyIDB4YzIwMDAwMDAgTUVN DQogTUFYX0xBVCAweDAwIE1JTl9HTlQgMHgwMCBJTlRfUElOIDB4MDEgSU5U X0xJTkUgMHhmZg0KDQpwY2kgYnVzIDB4MCBjYXJkbnVtIDB4MGMsIHZlbmRv ciAweDBlMTEgZGV2aWNlIDB4YTBlYw0KIERldmljZSB1bmtub3duDQogU1RB VFVTIDB4MDIwMCBDT01NQU5EIDB4MDE1Nw0KIENMQVNTIDB4MDIgMHg4MCAw eDAwIFJFVklTSU9OIDB4MDMNCiBCSVNUIDB4MDAgSEVBREVSIDB4MDAgTEFU RU5DWSAweDQwIENBQ0hFIDB4MDgNCiBCQVNFMCAweDAwMDA1MDAxIGFkZHIg MHgwMDAwNTAwMCBJL08NCiBCQVNFMSAweDAwMDA1NDAxIGFkZHIgMHgwMDAw NTQwMCBJL08NCiBCQVNFMiAweGMzZmZmZTAwIGFkZHIgMHhjM2ZmZmUwMCBN RU0NCiBNQVhfTEFUIDB4MDAgTUlOX0dOVCAweDAwIElOVF9QSU4gMHgwMSBJ TlRfTElORSAweDA1DQoNCnBjaSBidXMgMHgwIGNhcmRudW0gMHgwZiwgdmVu ZG9yIDB4MGUxMSBkZXZpY2UgMHgwMDAxDQogRGV2aWNlIHVua25vd24NCiBT VEFUVVMgMHgwMjAwIENPTU1BTkQgMHgwMTQ3DQogQ0xBU1MgMHgwNiAweDAy IDB4MDAgUkVWSVNJT04gMHgwNw0KDQpwY2kgYnVzIDB4MCBjYXJkbnVtIDB4 MTEsIHZlbmRvciAweDExNjYgZGV2aWNlIDB4MDAwNQ0KIERldmljZSB1bmtu b3duDQogU1RBVFVTIDB4MjIwMCBDT01NQU5EIDB4MDEwNg0KIENMQVNTIDB4 MDYgMHgwMCAweDAwIFJFVklTSU9OIDB4MDINCiBCSVNUIDB4MDAgSEVBREVS IDB4MDAgTEFURU5DWSAweDQwIENBQ0hFIDB4MDgNCg0KcGNpIGJ1cyAweDEg Y2FyZG51bSAweDA0LCB2ZW5kb3IgMHgxMDAwIGRldmljZSAweDAwMGYNCiBO Q1IgIERldmljZSB1bmtub3duDQogU1RBVFVTIDB4MDIwMCBDT01NQU5EIDB4 MDE1Nw0KIENMQVNTIDB4MDEgMHgwMCAweDAwIFJFVklTSU9OIDB4MTQNCiBC SVNUIDB4MDAgSEVBREVSIDB4ODAgTEFURU5DWSAweGZmIENBQ0hFIDB4MDgN CiBCQVNFMCAweDAwMDA2MDAxIGFkZHIgMHgwMDAwNjAwMCBJL08NCiBCQVNF MSAweGM2ZWZkZjAwIGFkZHIgMHhjNmVmZGYwMCBNRU0NCiBCQVNFMiAweGM2 ZWZmMDAwIGFkZHIgMHhjNmVmZjAwMCBNRU0NCiBNQVhfTEFUIDB4NDAgTUlO X0dOVCAweDExIElOVF9QSU4gMHgwMSBJTlRfTElORSAweDBhDQoNCnBjaSBi dXMgMHgxIGNhcmRudW0gMHgwNiwgdmVuZG9yIDB4MTAxNCBkZXZpY2UgMHgw MDIyDQogRGV2aWNlIHVua25vd24NCiBTVEFUVVMgMHgwMjgwIENPTU1BTkQg MHgwMTQ3DQogQ0xBU1MgMHgwNiAweDA0IDB4MDAgUkVWSVNJT04gMHgwMQ0K IEJJU1QgMHgwMCBIRUFERVIgMHgwMSBMQVRFTkNZIDB4ODAgQ0FDSEUgMHgw OA0KIEJBU0UyIDB4ZjgwMjAyMDEgYWRkciAweGY4MDIwMjAwIEkvTw0KIEJB U0UzIDB4MjQ4MDcxNzEgYWRkciAweDI0ODA3MTcwIEkvTw0KIEJBU0U0IDB4 YzZmMGM2ZjAgYWRkciAweGM2ZjBjNmYwIE1FTQ0KIEJBU0U1IDB4YzVmMGM0 MDAgYWRkciAweGM1ZjBjNDAwIE1FTQ0KIE1BWF9MQVQgMHgwMCBNSU5fR05U IDB4MDcgSU5UX1BJTiAweDAwIElOVF9MSU5FIDB4MDANCg0KcGNpIGJ1cyAw eDEgY2FyZG51bSAweDA4LCB2ZW5kb3IgMHgwZTExIGRldmljZSAweGFlMzIN CiBEZXZpY2UgdW5rbm93bg0KIFNUQVRVUyAweDAyODAgQ09NTUFORCAweDAx NDcNCiBDTEFTUyAweDAyIDB4ODAgMHgwMCBSRVZJU0lPTiAweDEwDQogQklT VCAweDAwIEhFQURFUiAweDAwIExBVEVOQ1kgMHg0MCBDQUNIRSAweDA4DQog QkFTRTAgMHgwMDAwNjgwMSBhZGRyIDB4MDAwMDY4MDAgSS9PDQogQkFTRTEg MHhjNmVmZGRmMCBhZGRyIDB4YzZlZmRkZjAgTUVNDQogTUFYX0xBVCAweDAw IE1JTl9HTlQgMHgwMCBJTlRfUElOIDB4MDEgSU5UX0xJTkUgMHgwOQ0KDQpw Y2kgYnVzIDB4MiBjYXJkbnVtIDB4MDAsIHZlbmRvciAweDBlMTEgZGV2aWNl IDB4YWUxMA0KIERldmljZSB1bmtub3duDQogU1RBVFVTIDB4MDIwMCBDT01N QU5EIDB4MDE0Nw0KIENMQVNTIDB4MDEgMHg4MCAweDAwIFJFVklTSU9OIDB4 MDINCiBCSVNUIDB4MDAgSEVBREVSIDB4MDAgTEFURU5DWSAweDAwIENBQ0hF IDB4MDgNCiBCQVNFMCAweDAwMDA3MDAxIGFkZHIgMHgwMDAwNzAwMCBJL08N CiBCQVNFMSAweGM2ZmZmZjAwIGFkZHIgMHhjNmZmZmYwMCBNRU0NCiBCQVNF MiAweGM0MDAwMDA4IGFkZHIgMHhjNDAwMDAwMCBNRU0NCiBNQVhfTEFUIDB4 MDAgTUlOX0dOVCAweDAwIElOVF9QSU4gMHgwMSBJTlRfTElORSAweDBhDQoN ClBDSSBwcm9iaW5nIGNvbmZpZ3VyYXRpb24gdHlwZSAyDQo= --0-1598452307-894040654=:6670-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 1 09:49:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10582 for freebsd-hardware-outgoing; Fri, 1 May 1998 09:49:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from journyx.com (journyx.com [207.8.10.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10558 for ; Fri, 1 May 1998 09:49:04 -0700 (PDT) (envelope-from dcm@srdi.com) Received: from localhost (dcm@localhost) by journyx.com (8.7.5/8.7.3) with SMTP id LAA25720 for ; Fri, 1 May 1998 11:48:30 -0500 (CDT) Date: Fri, 1 May 1998 11:48:30 -0500 (CDT) From: Craig Miller X-Sender: dcm@journyx.com To: freebsd-hardware@FreeBSD.ORG Subject: AIC-7780 (integrated scsi) supported? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, My apologies in advance if I've chosen the wrong mailing list. I've checked the FreeBSD Disk Controller list and it lists the Adaptec AIC7850 as supported. Is the AIC7880 also supported? I have a 4.3gb UW scsi drive with NT (preinstalled) on the first 2gb partition and want to install 2.2.6 on the remaining portion of the drive. On my first attempt I split the remaining sectors into a 1gb and a 1.3gb partition and successfully installed Freebsd on the first, but when I try to put filesystems on the 1.3gb partition, filesystems on the 1gb partition get wiped out, almost as if the newfs writes were going to random sectors. More info: I know that comparing NT and FreeBSD filesystems is comparing apples and oranges, but I was able to format the remaining 2.3gb as an NT filesystem, so I'm guessing it's not hardware. Suggestions, pointers and warnings are appreciated. Thanks. Craig Miller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 1 10:11:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13778 for freebsd-hardware-outgoing; Fri, 1 May 1998 10:11:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA13761 for ; Fri, 1 May 1998 10:11:00 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yVIvT-000218-00; Fri, 1 May 1998 09:44:43 -0700 Date: Fri, 1 May 1998 09:44:38 -0700 (PDT) From: Tom To: Craig Miller cc: freebsd-hardware@FreeBSD.ORG Subject: Re: AIC-7780 (integrated scsi) supported? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 1 May 1998, Craig Miller wrote: > Hi, > My apologies in advance if I've chosen the wrong mailing list. > > I've checked the FreeBSD Disk Controller list and it lists the > Adaptec AIC7850 as supported. Is the AIC7880 also supported? Yes (this is a hardware question). > I have a 4.3gb UW scsi drive with NT (preinstalled) on the first 2gb > partition and want to install 2.2.6 on the remaining portion of > the drive. On my first attempt I split the remaining sectors into a > 1gb and a 1.3gb partition and successfully installed Freebsd on the > first, but when I try to put filesystems on the 1.3gb partition, > filesystems on the 1gb partition get wiped out, almost as if > the newfs writes were going to random sectors. (This really belongs freebsd-questions) FreeBSD has been given the wrong partitioning info, so they are actually overlapping. Probably a bad disk label, or a geometry problem. Are the partitions you speak of slices? How are you refering to them? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 1 14:55:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29346 for freebsd-hardware-outgoing; Fri, 1 May 1998 14:55:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29290; Fri, 1 May 1998 14:54:43 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id XAA07962; Fri, 1 May 1998 23:54:36 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id XAA06711; Fri, 1 May 1998 23:11:06 +0200 (CEST) X-Face: " Date: Fri, 1 May 1998 23:11:05 +0200 From: Stefan Esser To: Joe Orthoefer , freebsd-hardware@FreeBSD.ORG Cc: Stefan Esser Subject: Re: compaq "dual host" pci archetecture References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Joe Orthoefer on Fri, May 01, 1998 at 12:41:24PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-05-01 12:41 -0400, Joe Orthoefer wrote: > > I have access to a compaq 5500 that has 8 pci slots. The first four slots > and the last four slots, according to compaq's sales literature are each > behind their own host to pci bridge chip. When booting freebsd it > recognizes and scans only one of the pci busses, though it sees both of > the host to pci bridge chips. Are there allowances for such a > configuration in the current pci layer? Please try the following patch and let me know, whether it works for you. Do you happen to know the name of the host bridge chips (made by either Ross or Requr, the PCI vendor list contains two matches for vendor 0x1166) ? Regards, STefan Index: /sys/pci/pcisupport.c =================================================================== RCS file: /usr/cvs/src/sys/pci/pcisupport.c,v retrieving revision 1.62 diff -C2 -r1.62 pcisupport.c *** pcisupport.c 1998/03/27 20:36:54 1.62 --- pcisupport.c 1998/05/01 20:40:03 *************** *** 133,136 **** --- 133,144 ---- static void + fixbushigh_Pequr(pcici_t tag) + { + /* the register numbers are just a guess ... */ + tag->secondarybus = pci_cfgread(tag, 0x44, 1); + tag->subordinatebus = pci_cfgread(tag, 0x45, 1); + } + + static void fixwsc_natoma(pcici_t tag) { *************** *** 244,247 **** --- 258,264 ---- case 0x01051004: return ("VLSI 82C147 IrDA Controller"); + case 0x00051166: + fixbushigh_Pequr(tag); + return ("Pequr (?) host to PCI bridge"); }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 2 05:44:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16691 for freebsd-hardware-outgoing; Sat, 2 May 1998 05:44:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16686 for ; Sat, 2 May 1998 05:44:41 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id IAA21479; Sat, 2 May 1998 08:40:04 -0400 (EDT) From: Peter Dufault Message-Id: <199805021240.IAA21479@hda.hda.com> Subject: Re: [Target Mode] Was: Ooops - sorry In-Reply-To: <3549E7CB.75A9EFFD@feral.com> from Matthew Jacob at "May 1, 98 08:18:35 am" To: mjacob@feral.com (Matthew Jacob) Date: Sat, 2 May 1998 08:39:53 -0400 (EDT) Cc: hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > as long as they are selling chips to Qlogic, > > Wrong. Qlogic is still it's own company. You misread me - I believe the "NCR" / Symbios chip company (NCR sold their SCSI chips to Symbios two or so years ago) was just bought by Adaptec. I mean as long as that group is selling chips to small indepedendent companies such as Qlogic, Acculogic, Asus, etc it should be possible to buy appropriate boards. I personally don't like Adaptec monopolizing the SCSI chip business. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 2 08:56:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11803 for freebsd-hardware-outgoing; Sat, 2 May 1998 08:56:46 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lupin.csv.warwick.ac.uk (csubl@lupin.csv.warwick.ac.uk [137.205.192.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11783 for ; Sat, 2 May 1998 08:56:38 -0700 (PDT) (envelope-from csubl@csv.warwick.ac.uk) Received: (from csubl@localhost) by lupin.csv.warwick.ac.uk (8.8.7/8.8.8) id QAA11606 for hardware@freebsd.org; Sat, 2 May 1998 16:56:33 +0100 (BST) From: Mr M P Searle Message-Id: <199805021556.QAA11606@lupin.csv.warwick.ac.uk> Subject: BX board for FreeBSD? To: hardware@FreeBSD.ORG Date: Sat, 2 May 1998 16:56:33 +0100 (BST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've seen some discussion about BX boards, but is anyone running FreeBSD on one yet? Any recommendations? (I'm looking for a 1 cpu board with 2940 SCSI and maybe sound, I assume they will all have AGP and SDRAM support.) Thanks, Michael. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 2 10:15:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21603 for freebsd-hardware-outgoing; Sat, 2 May 1998 10:15:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21588 for ; Sat, 2 May 1998 10:15:43 -0700 (PDT) (envelope-from parag@mail.codegen.com) Received: from [192.168.100.101] (ppp-asok07--135.sirius.net [205.134.245.135]) by mail1.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id KAA12957 for ; Sat, 2 May 1998 10:15:44 -0700 (PDT) Message-Id: <199805021715.KAA12957@mail1.sirius.com> Subject: Re: [Target Mode] Was: Ooops - sorry Date: Sat, 2 May 1998 10:17:36 -0700 x-sender: parag@mail.codegen.com x-mailer: Claris Emailer 2.0v3, January 22, 1998 X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm From: Parag Patel cc: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 5/2/98 5:39 AM, Peter Dufault (dufault@hda.com) said: >I personally don't like Adaptec monopolizing the SCSI chip business. Me either. Fortunately there are other chips around but unfortunately not too many people use them. AMD has a family of SCSI chips. (The Am79C974 is a combination Ethernet and SCSI-2 PCI chip that one of our customers is looking at for a custom board design.) I thought that CMD and Motorola also made some SCSI chips, but I may be mistaken. There are probably others. I suspect that if Adaptec prices their chips too high, the lower-end PCI-card vendors will simply switch to someone else's chips to keep their costs down, and it'll also give a lot of incentive to other chip makers to get into the SCSI-chip business. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 2 11:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03841 for freebsd-hardware-outgoing; Sat, 2 May 1998 11:51:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03824 for ; Sat, 2 May 1998 11:51:00 -0700 (PDT) (envelope-from kedar@asacomputers.com) Received: by gw1.asacomputers.com id LAA06165; Sat, 2 May 1998 11:51:42 -0700 (PDT) Message-Id: <2.2.32.19980502184747.00f35df4@gw1> X-Sender: rajadnya@gw1 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 02 May 1998 11:47:47 -0700 To: Mr M P Searle From: Kedar Rajadnya Subject: Re: BX board for FreeBSD? Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ABIT BX-6 and Tyan S1846S. Just loaded FreeBSD and testing. No problems so far. Kedar. At 04:56 PM 5/2/98 +0100, you wrote: >I've seen some discussion about BX boards, but is anyone running >FreeBSD on one yet? Any recommendations? (I'm looking for a 1 >cpu board with 2940 SCSI and maybe sound, I assume they will >all have AGP and SDRAM support.) > >Thanks, Michael. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message