From owner-freebsd-hardware Sun Jul 19 15:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06003 for freebsd-hardware-outgoing; Sun, 19 Jul 1998 15:46:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from jane.lfn.org ([209.16.92.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA05998 for ; Sun, 19 Jul 1998 15:46:42 -0700 (PDT) (envelope-from craig@lfn.org) Received: (qmail 20911 invoked by uid 100); 19 Jul 1998 22:46:27 -0000 Date: Sun, 19 Jul 1998 17:46:27 -0500 (CDT) From: Craig Johnston To: freebsd-hardware@FreeBSD.ORG Subject: freebsd laptop 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'm looking into a laptop to run FreeBSD on, but want to make sure the sound and video are supported. My criteria: good keyboard and pointing device TFT 1024x768 in true color 32 megs ram minimum 3 gb HD minimum 166MMX or better 12" display or better (13" optimal) Has anyone bought a laptop matching this description recently and managed to get XWindows running at 1024x768 in true color? I don't care about small size -- in fact I don't want it. I've been looking at models by Quantex and AMS -- both exceed my specs and are around $2400. Anyone having good success with models by either of these companies fitting my description? Any other companies to look at? TIA, Craig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 19 16:01:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07672 for freebsd-hardware-outgoing; Sun, 19 Jul 1998 16:01:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pm01sm.pmm.mci.net (pm01sm.pmm.mci.net [208.159.126.150]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07667 for ; Sun, 19 Jul 1998 16:01:23 -0700 (PDT) (envelope-from wolfnet@wolfnet-irc.org) Received: from wolfnet-irc.org (usr29-dialup24.mix1.Sacramento.mci.net) by PM01SM.PMM.MCI.NET (PMDF V5.1-10 #27033) with ESMTP id <0EWD00H266L0G6@PM01SM.PMM.MCI.NET> for freebsd-hardware@freebsd.org; Sun, 19 Jul 1998 23:00:39 +0000 (GMT) Date: Sun, 19 Jul 1998 17:20:32 +0000 From: Jonathan & Charmane Frazier Subject: hardware question To: freebsd-hardware@FreeBSD.ORG Message-id: <35B22AE0.89844C19@wolfnet-irc.org> Organization: The WolfNet-IRC Organization MIME-version: 1.0 X-Mailer: Mozilla 4.05 [en] (Win95; I) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just bought a new Gigabyte BX board with a PII400. I haven't purchased the RAM yet because I am not too sure about the difference between the ECC SDRAM and non-ECC. I am planning on installing FreeBSD 2.2.6 because it is the BEST and I was just wondering if any of you had any experience with this type of configuration or have had any problems with it. Also if you have any suggestions about going ECC or not and if it's even supported by FBSD or if it's totally hardware controlled and I don't need to worry about it. Thanks a lot for your time. Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 19 20:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10759 for freebsd-hardware-outgoing; Sun, 19 Jul 1998 20:40:07 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from iworks.interworks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10752 for ; Sun, 19 Jul 1998 20:40:03 -0700 (PDT) (envelope-from deischen@iworks.interworks.org) Received: (from deischen@localhost) by iworks.interworks.org (8.8.7/8.8.7) id WAA10643; Sun, 19 Jul 1998 22:42:10 -0500 (CDT) Date: Sun, 19 Jul 1998 22:42:10 -0500 (CDT) From: "Daniel M. Eischen" Message-Id: <199807200342.WAA10643@iworks.interworks.org> To: caj@lfn.org Subject: Re: freebsd laptop Cc: freebsd-hardware@FreeBSD.ORG 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 Craig Johnston wrote: > I'm looking into a laptop to run FreeBSD on, but want to make sure > the sound and video are supported. > > My criteria: > good keyboard and pointing device > TFT 1024x768 in true color > 32 megs ram minimum > 3 gb HD minimum > 166MMX or better > 12" display or better (13" optimal) > > Has anyone bought a laptop matching this description recently and managed > to get XWindows running at 1024x768 in true color? My Chemusa Chembook 6800XL (see www.chemusa.com) has all of these features: P200MMX TFT1024x768 14.1" display 32MB RAM or more 3GB Hard drive Internal CD-ROM and Floppy ESS1868 sound system C&T 65554 graphics with 4MB Video RAM 2-button touchpad mouse XFree86 works in 1024x768 at both 16bpp and 24bpp and the sound system works with FreeBSD sound drivers (not Luigi's sound (pcm) driver though). I liked Chemusa because they have the chipset information for all their products online. This will let you easily avoid the dreaded NeoMagic video chip which isn't supported by XFree86. Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 20 01:19:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10711 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 01:19:59 -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 BAA10706 for ; Mon, 20 Jul 1998 01:19:57 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id KAA23163; Mon, 20 Jul 1998 10:19:27 +0200 (MET DST) Date: Mon, 20 Jul 1998 10:19:24 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: paulo@nlink.com.br cc: dan@math.berkeley.edu, freebsd-hardware@FreeBSD.ORG Subject: Re: FBSD & PII In-Reply-To: <199807180329.UAA05935@george.lbl.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 Same here: OS/2, FBSD 2.2.1, FBSD 3.0-SNAP-may-1997. The nice thing is that the home directories are on a separate partition and can be used in both version of the opsys. Nick On Fri, 17 Jul 1998, Jin Guojun wrote: > There is nothing to be worried if you have some free disk space -- > (DOS fdisk partition, or called slice under FreeBSD). > FreeBSD installation will take care the rest thing for you. > > I have a disk runs DOS / FreeBSD 2.1.7 / FreeBSD 2.2.6 / FreeBSD 3.0-SNAP. > The boot manager will prompt you to boot one of them with F1/F2/F3/F4 key. > > -Jin > > :> I'm thinking to start use FBSD 3.0 with multi-processor but I would like > :> to have in another partition my good friend FBSD 2.2.6 :-), is this > :> possible? Did anyone do this? > : > :It should be possible in theory, but I anticipate serious problems in > :practice. You would have to make sure that you always used the slice > :specific disk device names and never the "compatibility" slice. > : > :For example, your fstab would have to specify one of /dev/sd0s{1,2,3,4}f > :instead of /dev/sd0f. I am not sure how you would manage slice > :selection during bootstrap, selecting the initial swap partition, and > :initial mounting of the root file system. I would worry about disk > :utilities (such as the disklabel program) always doing the right thing. > :I would worry about the FreeBSD installation process always using the > :specified slice. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 20 02:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14910 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 02:42:54 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from shell6.ba.best.com (jkb@shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14905 for ; Mon, 20 Jul 1998 02:42:53 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) with SMTP id CAA09753; Mon, 20 Jul 1998 02:42:37 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Mon, 20 Jul 1998 02:42:37 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: Craig Johnston cc: freebsd-hardware@FreeBSD.ORG Subject: Re: freebsd laptop 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 Check out www.jp.freebsd.org/PAO -- they have a laptop survey. I am pretty happy with my Dell Latitude CP -- 166MHz, 48RAM, 3.1HD and it is supported by XiG (www.xig.com) -- Yan Jan Koum jkb@best.com | "Turn up the lights; I don't want www.FreeBSD.org -- The Power to Serve | to go home in the dark." On Sun, 19 Jul 1998, Craig Johnston wrote: >I'm looking into a laptop to run FreeBSD on, but want to make sure >the sound and video are supported. > >My criteria: >good keyboard and pointing device >TFT 1024x768 in true color >32 megs ram minimum >3 gb HD minimum >166MMX or better >12" display or better (13" optimal) > >Has anyone bought a laptop matching this description recently and managed >to get XWindows running at 1024x768 in true color? > >I don't care about small size -- in fact I don't want it. > >I've been looking at models by Quantex and AMS -- both exceed >my specs and are around $2400. Anyone having good success >with models by either of these companies fitting my description? > >Any other companies to look at? > >TIA, >Craig. > > > >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 Mon Jul 20 02:46:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15221 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 02:46:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@199-170-160-195.la.inreach.net [199.107.160.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15165; Mon, 20 Jul 1998 02:46:34 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id CAA16629; Mon, 20 Jul 1998 02:45:50 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 20 Jul 1998 02:45:50 -0700 (PDT) Organization: Computer Help From: Donald Burr To: "Babylon (Ray)" , FreeBSD Hardware Subject: RE: Mother Board Chip Set question Cc: questions@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ moved to freebsd-hardware ] My secret spy satellite informs me that on 20-Jul-98, Babylon (Ray) wrote: > Question: Are there any know problems with the 430TX chip set for use > with FREE BSD? I am using a Tyan S1571S board, which is based on the 430TX, with both FreeBSD 2.2.6-RELEASE and 3.0-CURRENT. It works fine. If you have IDE disks, 3.0-CURRENT will support the built-in Ultra DMA 33 support on the 430TX's IDE channels. The only problem with the 430TX is that it WILL NOT cache memory above the 64 MB boundary. Whether or not this will hurt your performance, really depends on how you use your machine. For me, I could care less. --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. ----------------------------------------------------------------------- FreeBSD - Turning PCs into Workstations - http://www.freebsd.org/ !!! NEW EMAIL ADDRESS !!! This is a commercial service and works MUCH better than the (free, but buggy) POBoxes.com that I used to use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 20 10:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06463 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 10:30:15 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from inet.chipweb.ml.org (qmailr@c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA06412 for ; Mon, 20 Jul 1998 10:30:06 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Message-Id: <199807201730.KAA06412@hub.freebsd.org> Received: (qmail 9815 invoked from network); 20 Jul 1998 17:30:01 -0000 Received: from speedy.chipweb.ml.org (172.16.1.1) by inet.chipweb.ml.org with SMTP; 20 Jul 1998 17:30:01 -0000 X-Sender: ludwigp2@mail-r X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 20 Jul 1998 10:29:56 -0700 To: Donald Burr , "Babylon (Ray)" , FreeBSD Hardware From: Ludwig Pummer Subject: RE: Mother Board Chip Set question Cc: questions@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 02:45 AM 7/20/98 -0700, Donald Burr wrote: >The only problem with the 430TX is that it WILL NOT cache memory above the >64 MB boundary. Whether or not this will hurt your performance, really >depends on how you use your machine. For me, I could care less. >--- >Donald Burr - Ask me for my PGP key | PGP: Your Actually, it can, but only with a little help. On Asus TX chipset boards, there is a small socket for a 'tag SRAM' chip which would allow all memory to be cached (i think the board's max is 256MB). --Ludwig Pummer ludwigp@bigfoot.com ludwigp@chipweb.ml.org ICQ UIN: 692441 http://chipweb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 20 12:41:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00757 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 12:41:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00738; Mon, 20 Jul 1998 12:41:28 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id MAA12337; Mon, 20 Jul 1998 12:40:55 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA112693654; Mon, 20 Jul 1998 12:40:54 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id MAA11718; Mon, 20 Jul 1998 12:40:53 -0700 (PDT) Message-Id: <199807201940.MAA11718@mina.sr.hp.com> To: Ludwig Pummer Cc: Donald Burr , "Babylon (Ray)" , FreeBSD Hardware , questions@FreeBSD.ORG Subject: Re: Mother Board Chip Set question Reply-To: darrylo@sr.hp.com In-Reply-To: Your message of "Mon, 20 Jul 1998 10:29:56 PDT." <199807201730.KAA06412@hub.freebsd.org> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Mon, 20 Jul 1998 12:40:53 -0700 From: Darryl Okahata Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ludwig Pummer wrote: > At 02:45 AM 7/20/98 -0700, Donald Burr wrote: > >The only problem with the 430TX is that it WILL NOT cache memory above the > >64 MB boundary. Whether or not this will hurt your performance, really > >depends on how you use your machine. For me, I could care less. > > Actually, it can, but only with a little help. On Asus TX chipset boards, > there is a small socket for a 'tag SRAM' chip which would allow all memory > to be cached (i think the board's max is 256MB). You're confusing TX with HX. The TX is limited to caching only 64MB, whereas the ASUS HX-based boards (e.g., P55T2P4) can cache past that with a tag RAM chip (or by the appropriate COAST module). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 20 13:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08596 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 13:27:54 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from inet.chipweb.ml.org (qmailr@c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08568 for ; Mon, 20 Jul 1998 13:27:46 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Message-Id: <199807202027.NAA08568@hub.freebsd.org> Received: (qmail 28575 invoked from network); 20 Jul 1998 20:27:21 -0000 Received: from speedy.chipweb.ml.org (172.16.1.1) by inet.chipweb.ml.org with SMTP; 20 Jul 1998 20:27:21 -0000 X-Sender: ludwigp@mail.plstn1.sfba.home.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 20 Jul 1998 13:24:24 -0700 To: darrylo@sr.hp.com From: Ludwig Pummer Subject: Re: Mother Board Chip Set question Cc: Donald Burr , "Babylon (Ray)" , FreeBSD Hardware , questions@FreeBSD.ORG In-Reply-To: <199807201940.MAA11718@mina.sr.hp.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:40 PM 7/20/98 -0700, Darryl Okahata wrote: >Ludwig Pummer wrote: > >> At 02:45 AM 7/20/98 -0700, Donald Burr wrote: >> >The only problem with the 430TX is that it WILL NOT cache memory above the >> >64 MB boundary. Whether or not this will hurt your performance, really >> >depends on how you use your machine. For me, I could care less. >> >> Actually, it can, but only with a little help. On Asus TX chipset boards, >> there is a small socket for a 'tag SRAM' chip which would allow all memory >> to be cached (i think the board's max is 256MB). > > You're confusing TX with HX. The TX is limited to caching only >64MB, whereas the ASUS HX-based boards (e.g., P55T2P4) can cache past >that with a tag RAM chip (or by the appropriate COAST module). > > -- Darryl Okahata > Internet: darrylo@sr.hp.com You're right. I stand corrected. --Ludwig Pummer ludwigp@bigfoot.com ludwigp@chipweb.ml.org ICQ UIN: 692441 http://chipweb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 20 13:41:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11096 for freebsd-hardware-outgoing; Mon, 20 Jul 1998 13:41:03 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from junior.apk.net (stuart@junior.apk.net [207.54.158.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11091 for ; Mon, 20 Jul 1998 13:41:01 -0700 (PDT) (envelope-from stuart@junior.apk.net) Received: from localhost by junior.apk.net (8.9.1/8.9.1) with SMTP id QAA07751; Mon, 20 Jul 1998 16:40:27 -0400 (EDT) Date: Mon, 20 Jul 1998 16:40:27 -0400 (EDT) From: Stuart Krivis To: Ludwig Pummer cc: FreeBSD Hardware Subject: RE: Mother Board Chip Set question In-Reply-To: <199807201730.KAA06411@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 On Mon, 20 Jul 1998, Ludwig Pummer wrote: > At 02:45 AM 7/20/98 -0700, Donald Burr wrote: > >The only problem with the 430TX is that it WILL NOT cache memory above the > >64 MB boundary. Whether or not this will hurt your performance, really > >depends on how you use your machine. For me, I could care less. > >--- > >Donald Burr - Ask me for my PGP key | PGP: Your > > Actually, it can, but only with a little help. On Asus TX chipset boards, > there is a small socket for a 'tag SRAM' chip which would allow all memory > to be cached (i think the board's max is 256MB). The Intel TX chipset cannot cache more than 64 MB. Period. The end. -- Stuart Krivis stuart@krivis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 21 15:04:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25893 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 15:04:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25888 for ; Tue, 21 Jul 1998 15:04:44 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id PAA27258 for hardware@freebsd.org; Tue, 21 Jul 1998 15:03:34 -0700 (PDT) (envelope-from dhw) Date: Tue, 21 Jul 1998 15:03:34 -0700 (PDT) From: David Wolfskill Message-Id: <199807212203.PAA27258@pau-amma.whistle.com> To: hardware@FreeBSD.ORG Subject: Anyone have experience with DLT stackers? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm working on implementing "amanda" for backup & recovery. We're in the process of switching from DDS (4mm) media to DLT. I believe that it would be useful to at least begin to plan for the (eventual) deployment of a stacker (though it need not be more elaborate than a simple "gravity" stacker). The vendor we're using (Andataco, evidently -- I'm still a little new here) has a couple of stackers with similar characteristics; each handles up to 7 DLT cartridges, but one is made by Quantum, and the other is made by Exabyte. Anyone have a feel for which is more likely to work adequately for FreeBSD 2.2.6-RELEASE? Here's the list of differences I've been told about (other than price, which is in the $8K range, with a difference of about $300 between the two -- close enough that price isn't a significant differentiator): Quantum ENC-6107-40S Exabyte EXB/18D-4TS Operator interface "control panel" LCD screen Bar Code Reader n/a available Dimensions WxHxD 8.9"x10.7"x27" 9.5"x22"x21.4" MTBF 30KHrs. 200KHrs. Cycles Between Failures 400K 1000K Each is a narrow single-ended SCSI device (in addition to the DLT4000 drive, which comes with the stacker), with a rated native xfer rate of 1.5MB/sec. (As alluded to above, I have no expectation that I'd be making any use of a bar-code reader.) Thanks, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 21 15:21:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27689 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 15:21:26 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA27667 for ; Tue, 21 Jul 1998 15:21:19 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id PAA15077; Tue, 21 Jul 1998 15:20:59 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id PAA09431; Tue, 21 Jul 1998 15:21:54 -0700 Date: Tue, 21 Jul 1998 15:21:54 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807212221.PAA09431@burdell.ece.arizona.edu> To: freebsd-hardware@FreeBSD.ORG Subject: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a new GPIB driver that supports National products AT/GPIB and GPIB/TNT. I believe it to be significantly better than the one currently included in FreeBSD-2.2.6 (in /sys/i386/isa/gpib.c). It should be a whole lot faster by the use of interrupts and different polling techniques (which is why I started this in the first place). My driver is a complete rewrite, with some insight gathered from both the current FreeBSD driver and the Linux driver. The Linux driver was particularly helpful, because National apparently likes to withhold certain details about their products... (lame) I would like to contribute my code, but would like some advice on how to best package it. It would be nice to have some other folks try it out first, too. I still have to package it, though. I have been debugging the driver as an lkm, but most drivers that you aren't actually working on are easier if you just config them in. It would seem best to make it work either way. Second, it exists in multiple source files right now. Is it best to consolodate all the source into one huge file, or leave it as several? Finally, how would I go about showing that this code is reliable and is worthy of replacing the current gpib.c? I haven't contributed anything before. It would be useful to me if somebody more experienced with device drivers than myself would be willing to look over what I have and make sure that I didn't do anything particularly stupid. I do not take this list (should I?) so if you could make sure I am explicitly included in any replies, that would be much appreciated. Thanks! John Galbraith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 21 15:30:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29619 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 15:30:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29613 for ; Tue, 21 Jul 1998 15:30:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA02370; Tue, 21 Jul 1998 15:29:48 -0700 (PDT) Message-Id: <199807212229.PAA02370@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: David Wolfskill cc: hardware@FreeBSD.ORG Subject: Re: Anyone have experience with DLT stackers? In-reply-to: Your message of "Tue, 21 Jul 1998 15:03:34 PDT." <199807212203.PAA27258@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Jul 1998 15:29:48 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm working on implementing "amanda" for backup & recovery. > > We're in the process of switching from DDS (4mm) media to DLT. > > I believe that it would be useful to at least begin to plan for the > (eventual) deployment of a stacker (though it need not be more > elaborate than a simple "gravity" stacker). > > The vendor we're using (Andataco, evidently -- I'm still a little > new here) has a couple of stackers with similar characteristics; > each handles up to 7 DLT cartridges, but one is made by Quantum, > and the other is made by Exabyte. > > Anyone have a feel for which is more likely to work adequately for > FreeBSD 2.2.6-RELEASE? They should both work just fine. I'm not too happy with Amanda though; it has the major drawback that it doesn't work well with stackers (you can't split a volume across multiple tapes, for example). Most stackers are well-behaved it seems; see the chio(1) manpage for the control interface we support. -- \\ 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 Tue Jul 21 16:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08034 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 16:18:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08018; Tue, 21 Jul 1998 16:18:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA02618; Tue, 21 Jul 1998 16:17:18 -0700 (PDT) Message-Id: <199807212317.QAA02618@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: john@ece.arizona.edu (John Galbraith) cc: freebsd-hardware@FreeBSD.ORG, randal@comtest.com, dufault@FreeBSD.ORG Subject: Re: new GPIB driver In-reply-to: Your message of "Tue, 21 Jul 1998 15:21:54 PDT." <199807212221.PAA09431@burdell.ece.arizona.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Jul 1998 16:17:18 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randal, I think this just might be your lucky day. 8) > I have a new GPIB driver that supports National products AT/GPIB and > GPIB/TNT. I believe it to be significantly better than the one > currently included in FreeBSD-2.2.6 (in /sys/i386/isa/gpib.c). It > should be a whole lot faster by the use of interrupts and different > polling techniques (which is why I started this in the first place). > My driver is a complete rewrite, with some insight gathered from both > the current FreeBSD driver and the Linux driver. The Linux driver was > particularly helpful, because National apparently likes to withhold > certain details about their products... (lame) No kidding. It's not always been that way; their products used to be well-documented and easy to work with. All that remains of the old tradition is price - their stuff is still too expensive. 8( > I would like to contribute my code, but would like some advice on how > to best package it. The best technique is to make sure that you have the following: - The driver source. Every source file should contain your copyright notice. - A manpage describing the driver, which should cover the relevance of the various config options, the programming interface, any diagnostics that the driver may emit and any other useful information. - Testimonials from at least one other independant user that has tested the driver (this is not mandatory, but it is desirable). Then submit a PR (using send-pr) summarising what you've got. Either include the stuff above in the PR (eg. uuencoded), or include a reference to a public FTP or HTTP server that contains the archive. Once you have a PR number, you can post to -hardware and -hackers letting people know about it, and just quote the PR. The PR is important, because it means that we have the submission on file, and the PR database is actively monitored (unlike the mailing list archives, which just slowly turn to compost over time). > It would be nice to have some other folks try it > out first, too. I still have to package it, though. I have been > debugging the driver as an lkm, but most drivers that you aren't > actually working on are easier if you just config them in. It would > seem best to make it work either way. Right on the mark with all of those. > Second, it exists in multiple > source files right now. Is it best to consolodate all the source into > one huge file, or leave it as several? Finally, how would I go about > showing that this code is reliable and is worthy of replacing the > current gpib.c? One single file is a little better from the point of view of ease of working on it, but by no means mandatory. See the 'matcd' driver for an example of a driver that comprises several files. One other advantage of having only a single source file is that you can declare all of your non-public functions static, and thus reduce namespace pollution (which is a real problem). Initially, I would suggest that you pick a new name for your driver, eg. 'nigpib'. I'd also talk to Fred Cawthorne (the author of the current gpib driver) and see whether he thinks the version in the system right now is worth preserving. It may be that his feelings are simply that it should die and yours should replace it, in which case exactly that would happen. > I haven't contributed anything before. It would be useful to me if > somebody more experienced with device drivers than myself would be > willing to look over what I have and make sure that I didn't do > anything particularly stupid. Sure. When you're happy it's working for you and your test candidates, submit the PR and start harrassing us to look at it. Please bear in mind that most of the committers are sufficiently overloaded that they work largely in interrupt mode - if you haven't gotten a result from us a few days after you ask, poke again. 8) > I do not take this list (should I?) so if you could make sure I am > explicitly included in any replies, that would be much appreciated. If you're planning to maintain the driver, it would be a good idea to try to watch the activity on either -current or -hackers, although this can be quite a lot of work. > Thanks! Thanks to you! -- \\ 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 Tue Jul 21 17:03:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16303 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 17:03:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from oldyeller.comtest.com (oahu-93.u.aloha.net [207.12.0.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16216 for ; Tue, 21 Jul 1998 17:03:11 -0700 (PDT) (envelope-from randal@comtest.com) Received: from graphics.comtest.com (graphics.comtest.com [206.127.245.194]) by oldyeller.comtest.com (8.8.8/8.8.8) with SMTP id OAA20288; Tue, 21 Jul 1998 14:11:45 -1000 (HST) (envelope-from randal@comtest.com) Message-Id: <199807220011.OAA20288@oldyeller.comtest.com> From: "Randal S. Masutani" Organization: ComTest Technologies, Inc. To: john@ece.arizona.edu (John Galbraith) Date: Tue, 21 Jul 1998 14:05:35 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: new GPIB driver Reply-to: randal@comtest.com CC: Peter Dufault , Mike Smith , FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807212221.PAA09431@burdell.ece.arizona.edu> X-mailer: Pegasus Mail for Windows (v3.01b) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 21 Jul 98, at 15:21, John Galbraith wrote: > I have a new GPIB driver that supports National products AT/GPIB and > GPIB/TNT. I believe it to be significantly better than the one > currently included in FreeBSD-2.2.6 (in /sys/i386/isa/gpib.c). It > should be a whole lot faster by the use of interrupts and different > polling techniques (which is why I started this in the first place). > My driver is a complete rewrite, with some insight gathered from both > the current FreeBSD driver and the Linux driver. The Linux driver was > particularly helpful, because National apparently likes to withhold > certain details about their products... (lame) Great! This is exactly what I've been looking for! :) > I would like to contribute my code, but would like some advice on how > to best package it. It would be nice to have some other folks try it > out first, too. I still have to package it, though. I have been > debugging the driver as an lkm, but most drivers that you aren't > actually working on are easier if you just config them in. It would > seem best to make it work either way. Second, it exists in multiple > source files right now. Is it best to consolodate all the source into > one huge file, or leave it as several? Finally, how would I go about > showing that this code is reliable and is worthy of replacing the > current gpib.c? I will take your code as is. I am trying to meet some deadlines and would appreciate if you could email me what you have. > I haven't contributed anything before. It would be useful to me if > somebody more experienced with device drivers than myself would be > willing to look over what I have and make sure that I didn't do > anything particularly stupid. I have been hacking at the current gpib.c driver and had some success getting it upto 600Kbytes/s transfers. But I would definitely like to eval your driver. > I do not take this list (should I?) so if you could make sure I am > explicitly included in any replies, that would be much appreciated. > > Thanks! > John Galbraith Randal Masutani ------------------------------------------------------------------------- ComTest Technologies, Inc. 3049 Ualena St., Suite 1005 Honolulu, Hawaii 96819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 21 23:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15276 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 23:13:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15269 for ; Tue, 21 Jul 1998 23:13:33 -0700 (PDT) (envelope-from tg@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.8/8.8.6) with ESMTP id IAA20070; Wed, 22 Jul 1998 08:13:07 +0200 (CEST) Received: (from tg@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id IAA25269; Wed, 22 Jul 1998 08:13:03 +0200 (CEST) To: john@ece.arizona.edu (John Galbraith) Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: new GPIB driver References: <199807212221.PAA09431@burdell.ece.arizona.edu> From: Thomas Gellekum Date: 22 Jul 1998 08:13:02 +0200 In-Reply-To: john@ece.arizona.edu's message of "Tue, 21 Jul 1998 15:21:54 -0700" Message-ID: <874swaxvkh.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 13 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org john@ece.arizona.edu (John Galbraith) writes: > I haven't contributed anything before. It would be useful to me if > somebody more experienced with device drivers than myself would be > willing to look over what I have and make sure that I didn't do > anything particularly stupid. ``More experienced'' I'm probably not, but I could use this driver in a short while. Just send me a copy when you're decided about the packaging. I can import the bits into the CVS tree when all the issues with Fred's driver have been worked out. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 21 23:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17722 for freebsd-hardware-outgoing; Tue, 21 Jul 1998 23:27:55 -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 XAA17682; Tue, 21 Jul 1998 23:27:37 -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 IAA03231; Wed, 22 Jul 1998 08:22:53 +0200 (CEST) To: Mike Smith cc: john@ece.arizona.edu (John Galbraith), freebsd-hardware@FreeBSD.ORG, randal@comtest.com, dufault@FreeBSD.ORG Subject: Re: new GPIB driver In-reply-to: Your message of "Tue, 21 Jul 1998 16:17:18 PDT." <199807212317.QAA02618@dingo.cdrom.com> Date: Wed, 22 Jul 1998 08:22:53 +0200 Message-ID: <3229.901088573@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199807212317.QAA02618@dingo.cdrom.com>, Mike Smith writes: > >Randal, I think this just might be your lucky day. 8) > >> I have a new GPIB driver that supports National products AT/GPIB and >> GPIB/TNT. I believe it to be significantly better than the one >> currently included in FreeBSD-2.2.6 (in /sys/i386/isa/gpib.c). Now, I havn't worked with GPIB since my days at Commodore, but just a few days ago I talked to a lab-programmer, and he was very interested in a "serious GPIB" interface, in particular if it came with a non-C interface for script people like him. Do you have anything that would allow the use of this driver from shell/tcl/perl/whatever for people like him ? -- 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 Wed Jul 22 01:43:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12967 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 01:43:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12821; Wed, 22 Jul 1998 01:42:45 -0700 (PDT) (envelope-from tg@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.8/8.8.6) with ESMTP id KAA20457; Wed, 22 Jul 1998 10:40:11 +0200 (CEST) Received: (from tg@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.8/8.8.5) id KAA00390; Wed, 22 Jul 1998 10:40:08 +0200 (CEST) To: Poul-Henning Kamp Cc: Mike Smith , john@ece.arizona.edu (John Galbraith), freebsd-hardware@FreeBSD.ORG, randal@comtest.com, dufault@FreeBSD.ORG Subject: Re: new GPIB driver References: <3229.901088573@critter.freebsd.dk> From: Thomas Gellekum Date: 22 Jul 1998 10:40:08 +0200 In-Reply-To: Poul-Henning Kamp's message of "Wed, 22 Jul 1998 08:22:53 +0200" Message-ID: <87n2a2s2hj.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 24 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Poul-Henning Kamp writes: > In message <199807212317.QAA02618@dingo.cdrom.com>, Mike Smith writes: > > > >Randal, I think this just might be your lucky day. 8) > > > >> I have a new GPIB driver that supports National products AT/GPIB and > >> GPIB/TNT. I believe it to be significantly better than the one > >> currently included in FreeBSD-2.2.6 (in /sys/i386/isa/gpib.c). > > Now, I havn't worked with GPIB since my days at Commodore, but just a > few days ago I talked to a lab-programmer, and he was very interested > in a "serious GPIB" interface, in particular if it came with a non-C > interface for script people like him. Do you have anything that would > allow the use of this driver from shell/tcl/perl/whatever for people > like him ? I'll probably have to write a clone for NI's libgpib. I intend to write an interface to Python for that. But that won't be today or tomorrow, it's more likely to be in the course of a few months. SWIG could probably be used to generate interfaces for several scripting languages. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 05:19:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18212 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 05:19:07 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA18192 for ; Wed, 22 Jul 1998 05:18:58 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA12276; Wed, 22 Jul 1998 08:18:15 -0400 Date: Wed, 22 Jul 1998 08:18:15 -0400 (EDT) From: Jamie Bowden Reply-To: Jamie Bowden To: David Wolfskill cc: hardware@FreeBSD.ORG, amanda-users@cs.umd.edu Subject: Re: Anyone have experience with DLT stackers? In-Reply-To: <199807212203.PAA27258@pau-amma.whistle.com> 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 Tue, 21 Jul 1998, David Wolfskill wrote: > I'm working on implementing "amanda" for backup & recovery. > > We're in the process of switching from DDS (4mm) media to DLT. > > I believe that it would be useful to at least begin to plan for the > (eventual) deployment of a stacker (though it need not be more > elaborate than a simple "gravity" stacker). > > The vendor we're using (Andataco, evidently -- I'm still a little > new here) has a couple of stackers with similar characteristics; > each handles up to 7 DLT cartridges, but one is made by Quantum, > and the other is made by Exabyte. > > Anyone have a feel for which is more likely to work adequately for > FreeBSD 2.2.6-RELEASE? > > Here's the list of differences I've been told about (other than price, > which is in the $8K range, with a difference of about $300 between the > two -- close enough that price isn't a significant differentiator): > > Quantum ENC-6107-40S Exabyte EXB/18D-4TS > Operator interface "control panel" LCD screen > Bar Code Reader n/a available > Dimensions WxHxD 8.9"x10.7"x27" 9.5"x22"x21.4" > MTBF 30KHrs. 200KHrs. > Cycles Between Failures 400K 1000K > > Each is a narrow single-ended SCSI device (in addition to the DLT4000 > drive, which comes with the stacker), with a rated native xfer rate of > 1.5MB/sec. > > (As alluded to above, I have no expectation that I'd be making any use > of a bar-code reader.) > > Thanks, > david The amanda mailing lists are probably a better place to be asking this. I have cc'd this message there. -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 06:58:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02710 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 06:58:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02702 for ; Wed, 22 Jul 1998 06:58:13 -0700 (PDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id JAA00997 for ; Wed, 22 Jul 1998 09:57:53 -0400 (EDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Date: Wed, 22 Jul 1998 09:57:53 -0400 (EDT) From: Greg Lynn To: freebsd-hardware@FreeBSD.ORG Subject: PCI modems... 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 was looking in a mag that had a PCI 56K modem with the flex technology and ability to upgrade V.90 made by Infotel. Does anyone have any comments on this card and does/will it work on 2.2.6? For $55 is's not that bad although it has a rockwell chipset on it... -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 08:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20862 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 08:34:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cs1.cityscope.net (cs1.cityscope.net [206.222.183.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20790 for ; Wed, 22 Jul 1998 08:34:08 -0700 (PDT) (envelope-from ingrid@cityscope.net) Received: from cityscope.net (193.cityscope.net [209.16.49.193]) by cs1.cityscope.net (8.9.0/8.9.0) with ESMTP id KAA01555 for ; Wed, 22 Jul 1998 10:43:10 -0500 (CDT) Message-ID: <35B60650.CAFF3E36@cityscope.net> Date: Wed, 22 Jul 1998 10:33:36 -0500 From: Ingrid Kast Fuller Reply-To: ingrid@cityscope.net Organization: CityScope Net X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Adaptec 2940UW & Seagate STT38000N Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone in the group had problems using the Adaptec 2940UW and Seagate STT38000N Tape Drive? We have 2 Quantum 4.3Gb Ultra Wide Hard Drives using the UW SCSI Bus and 1 Seagate STT38000N Tape Drive using the regular SCSI Bus on the Adaptec 2940UW card. We've had some HARDWARE FAILURE messages and we're trying to pin-point the problem, wondering if it could be a compatibility problem. We've already put in another new STT38000N and the messages still occurred. -- *********************************************************** Ingrid Kast Fuller (ingrid@cityscope.net) CityScope Net (http://www.cityscope.net) 1(713)477-6161 109 West Southmore, Pasadena, TX 77502-1001 *********************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 09:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26807 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 09:02:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA26750; Wed, 22 Jul 1998 09:02:28 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA14924; Wed, 22 Jul 1998 09:01:24 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA09842; Wed, 22 Jul 1998 09:02:20 -0700 Date: Wed, 22 Jul 1998 09:02:20 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807221602.JAA09842@burdell.ece.arizona.edu> To: phk@critter.freebsd.dk CC: mike@smith.net.au, freebsd-hardware@FreeBSD.ORG, randal@comtest.com, dufault@FreeBSD.ORG In-reply-to: <3229.901088573@critter.freebsd.dk> (message from Poul-Henning Kamp on Wed, 22 Jul 1998 08:22:53 +0200) Subject: Re: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Poul-Henning" == Poul-Henning Kamp writes: Poul-Henning> Now, I havn't worked with GPIB since my days at Poul-Henning> Commodore, but just a few days ago I talked to a Poul-Henning> lab-programmer, and he was very interested in a Poul-Henning> "serious GPIB" interface, in particular if it came Poul-Henning> with a non-C interface for script people like him. Poul-Henning> Do you have anything that would allow the use of Poul-Henning> this driver from shell/tcl/perl/whatever for people Poul-Henning> like him ? My personal use of the GPIB driver so far is mostly with Python - except the GPIB stuff itself is buried in a C++ extension module. I do have the expertise to write a python extension module to do lower level GPIB operations, though. I would rather work on the driver itself for now, but I would be willing to take this on sometime in the future. The Linux folks have a TCL module/C library that emulates National's library as closely as possible. I could do something like that, except that it would definitely be Python instead. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 09:07:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28086 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 09:07:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA28075 for ; Wed, 22 Jul 1998 09:07:35 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA15132; Wed, 22 Jul 1998 09:06:51 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA09866; Wed, 22 Jul 1998 09:07:46 -0700 Date: Wed, 22 Jul 1998 09:07:46 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807221607.JAA09866@burdell.ece.arizona.edu> To: randal@comtest.com CC: dufault@hda.com, mike@smith.net.au, FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807220011.OAA20288@oldyeller.comtest.com> (randal@comtest.com) Subject: Re: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Randal" == Randal S Masutani writes: Randal> I will take your code as is. I am trying to meet some Randal> deadlines and would appreciate if you could email me what Randal> you have. OK. I was hacking on it yesterday here at work and found a few things I need to look at that I discovered with the higher end equipment that I have here. This week I am going to put two cards in the machine and really try to tweak the performance also, although I think my code is useful even if I don't quite get the transfer rate that I want yet. Give me a couple of days to absorb the feedback I have received from the mailing list and write some documentation (and fix a couple of bugs 8-) ). I will then send you my code, and hopefully we can work together making sure that remaining bugs are few and far between. Thanks for the enthusiasm - it is nice to know that others are interested in one's work! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 10:18:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13014 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 10:18:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12924; Wed, 22 Jul 1998 10:17: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 AAA00856; Wed, 22 Jul 1998 00:14:41 -0700 (PDT) Message-Id: <199807220714.AAA00856@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp cc: Mike Smith , john@ece.arizona.edu (John Galbraith), freebsd-hardware@FreeBSD.ORG, randal@comtest.com, dufault@FreeBSD.ORG Subject: Re: new GPIB driver In-reply-to: Your message of "Wed, 22 Jul 1998 08:22:53 +0200." <3229.901088573@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 00:14:41 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In message <199807212317.QAA02618@dingo.cdrom.com>, Mike Smith writes: > > > >Randal, I think this just might be your lucky day. 8) > > > >> I have a new GPIB driver that supports National products AT/GPIB and > >> GPIB/TNT. I believe it to be significantly better than the one > >> currently included in FreeBSD-2.2.6 (in /sys/i386/isa/gpib.c). > > Now, I havn't worked with GPIB since my days at Commodore, but just a > few days ago I talked to a lab-programmer, and he was very interested > in a "serious GPIB" interface, in particular if it came with a non-C > interface for script people like him. Do you have anything that would > allow the use of this driver from shell/tcl/perl/whatever for people > like him ? You could almost certainly write something using the binary I/O capabilities of Tcl8 to deal with this. Or a Tcl extension writer (*wave*) could be contracted for a nominal consideration to produce an extension suitable for the job. -- \\ 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 Wed Jul 22 16:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19574 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 16:34:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19496 for ; Wed, 22 Jul 1998 16:34:10 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id QAA01887; Wed, 22 Jul 1998 16:30:36 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id QAA10025; Wed, 22 Jul 1998 16:31:31 -0700 Date: Wed, 22 Jul 1998 16:31:31 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807222331.QAA10025@burdell.ece.arizona.edu> To: randal@comtest.com CC: dufault@hda.com, mike@smith.net.au, FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807221926.JAA23230@oldyeller.comtest.com> (randal@comtest.com) Subject: Re: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Randal" == Randal S Masutani writes: Randal> Thanks John. I will be glad to work with you on your Randal> driver. My customer has signed the non-disclosure with NI Randal> for their TNT controller chip and will hopefully get some Randal> docs soon(but I've been waiting for over a month now. Very Randal> typical of NI I suppose.) OK, but if he signed a NDA, we can't exactly use that info in the driver, and distribute it all over the planet. At least not according to the agreement. If he wants to give me or you the information, it seems to be a legal risk (and rightly so) for your customer. Randal> I need to have NI 488.2 library interface for the project Randal> I am working on. Currently I am only required to Randal> implement about 10 functions from NI's library and that's Randal> all I have time for, due to my deadline. I am currently Randal> working on getting it working with Freds code. Randal> From your last email I take it that you haven't Randal> implemented any of NI's 488.2 library calls? So do you Randal> have a similar interface to Freds code? Yeah, it uses ioctl() calls. They are quite similar. It didn't take me more than a few minutes to convert my code from the stock driver to mine. If I had thought about it more, I could have just left them identical (except I would have to add a bunch). Another difference between his and my driver is how he uses the minor numbers. He likes to be able to open minor device 4, and write() to a device on the GPIB bus at address 4. This is sometimes useful, granted, but I personally don't even need to write to a GPIB printer or anything this way. Instead, I use the minor number as a card index, so I can have multiple cards in the machine at the same time. This may not be very common in real life, but I anticipate this being very useful for debugging the driver itself. I don't know any other way to actually measure the GPIB transfer rate. Maybe there is some special equipment available, but I don't have it. In any case, it would be trivial to write a program that would direct raw data directly to a specific device on the GPIB without any controller functions included. It just struck me that I could have the lower minor numbers work like Fred's driver, and some upper number (like 32) to be the main special file that you would open when you just wanted to dump data directly to a specific device. Not a big deal for now, though. Right now, I haven't even implemented write() and read(), other than to return the "system call not implemented" error. I will be hacking on this tonight, unless I get called off on some social errand... John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 17:17:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27842 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 17:17:15 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27810 for ; Wed, 22 Jul 1998 17:16:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA02438; Wed, 22 Jul 1998 17:13:40 -0700 (PDT) Message-Id: <199807230013.RAA02438@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: john@ece.arizona.edu (John Galbraith) cc: randal@comtest.com, dufault@hda.com, mike@smith.net.au, FreeBSD-hardware@FreeBSD.ORG Subject: Re: new GPIB driver In-reply-to: Your message of "Wed, 22 Jul 1998 16:31:31 PDT." <199807222331.QAA10025@burdell.ece.arizona.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 17:13:40 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Randal> From your last email I take it that you haven't > Randal> implemented any of NI's 488.2 library calls? So do you > Randal> have a similar interface to Freds code? > > Yeah, it uses ioctl() calls. They are quite similar. It didn't take > me more than a few minutes to convert my code from the stock driver to > mine. If I had thought about it more, I could have just left them > identical (except I would have to add a bunch). Another difference > between his and my driver is how he uses the minor numbers. He likes > to be able to open minor device 4, and write() to a device on the GPIB > bus at address 4. This is sometimes useful, granted, but I personally > don't even need to write to a GPIB printer or anything this way. I don't like this at all (as I pointed out to Randal). GPIB is a bus, and it should be treated like one. The GBIB driver should provide GPIB I/O services to a set of peripheral drivers (consider SCSI as an example). ioctl() is not good for I/O. > Instead, I use the minor number as a card index, so I can have > multiple cards in the machine at the same time. This may not be very > common in real life, but I anticipate this being very useful for > debugging the driver itself. You can encode both the card number and the address in the minor number I expect; there's lots of room there. Again, see how disks are handled. -- \\ 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 Wed Jul 22 20:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29182 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 20:49:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29176 for ; Wed, 22 Jul 1998 20:49:24 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.8/8.7.3) with ESMTP id XAA15671; Wed, 22 Jul 1998 23:48:50 -0400 (EDT) Message-Id: <199807230348.XAA15671@whizzo.transsys.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Greg Lynn cc: freebsd-hardware@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: PCI modems... References: In-reply-to: Your message of "Wed, 22 Jul 1998 09:57:53 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 23:48:49 -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't have any experience with this particular modem. Two things to consider: - make sure that this isn't a "Win modem", where much of what usually happens inside the modem by a microcontroller gets to be done by your host CPU. This is things like V.42bis. - While having a rockwell chipset is a good sign, you should be aware that the quality of the analog front-end of the modem may be the limiting factor that will affect what rate the modem manages to train at. For instance, the USR Sportster and Courier modems have more or less the same DSP implementation, by the quality of the analog front end in the Courier will have it connect at at higher rate than the Sportster, all other things being equal. louie > I was looking in a mag that had a PCI 56K modem with the flex > technology and ability to upgrade V.90 made by Infotel. Does anyone > have any comments on this card and does/will it work on 2.2.6? > For $55 is's not that bad although it has a rockwell chipset on it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 22 23:40:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21058 for freebsd-hardware-outgoing; Wed, 22 Jul 1998 23:40:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles163.castles.com [208.214.165.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21025 for ; Wed, 22 Jul 1998 23:39:54 -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 XAA00669; Wed, 22 Jul 1998 23:38:54 -0700 (PDT) Message-Id: <199807230638.XAA00669@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: randal@comtest.com cc: Mike Smith , Peter Dufault , john@ece.arizona.edu (John Galbraith), FreeBSD-hardware@FreeBSD.ORG Subject: Re: GPIB drivers? In-reply-to: Your message of "Wed, 22 Jul 1998 14:55:55 -1000." <199807230102.PAA23783@oldyeller.comtest.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 23:38:54 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On 22 Jul 98, at 17:07, Mike Smith wrote: > > > > Freds driver is using copyin/copyout in the ioctl(). > > > So is this bad to do this(copyin/out) here? > > > > It's bad insofar as using ioctl() for data transfer is generally > > considered the wrong way to do it. You should be using read and write > > to do data transfer. > > If not for data transfer how about configuring the driver settings like; > timeout, bus timing, end of line char,...? ioctl() exists for out-of-band activities, so yes, it's perfectly suited for that. Think of it as the "control channel". > > > case GPIBWRITE: > > > error=copyin(gd->count,&count,sizeof(count)); > > > if (error!=0) return(error); > > > > This should use fuword() > > I checked the fuword() manpage sound good. I guess i could use also > suword() to return values to userspace? Correct; make sure you always check the return value from it. A better construct than the one above is: if ((error = foobar(...))) return(error); This makes it clear that the test/return are a single action (though lots of people don't like assignments in tests...) > > > The standard read/write calls are using uiomove(). > > > > ... which is how IMHO it should be done. > > > > > I am not familiar with these issues but the driver does work. Why is bad > > > to use copyin/out vs. uiomove? I would appreciate any input. > > > > copyin/out precludes calling the driver from elsewhere within the > > kernel, and if you use it in a read/write/strategy routine, it means > > you can't handle readv/writev easily. (The latter are a godsend if > > you're trying to do scatter-gather style I/O). > > Not familiar with this (scatter-gather)concept, something I should learn? If, for example, your application is using an internal buffering scheme where you have data split into small buffers (eg. you are using a set of buffer chains because you are performing several sets of decoupled signal processing), and you wish to populate possibly many of these buffers at once (rather than making lots of read() calls, you can construct an array of iovec structures and pass the address and length of each of the buffers in a single readv() call. See the manpage for more details. If your application is performance-sensitive, avoiding lots of system calls (or a copy to/from a flat buffer) can be important. For example, in a data-processing application I was working on a while back, we had a stackable module architecture where data was received from the hardware into fixed-size buffers, which were pushed onto the input queue of the first module, and then the module queue kicked, which would ripple the buffers down the stack. Eventuall some number of buffers would come off the bottom. The buffers themselves were relatively small (usually around 100 bytes, up to about 512 or so tops) but the actual data rate was very high (1MB/s and up). Making 2000 syscalls a second to read the data, and another 1000 or so to commit it to the next processing stage was hurting a lot. On top of that, the next stage was in a pipe, and small pipe writes are very inefficient. So instead, we used readv() to fill as much of the freelist with buffers as possible, and at the other end writev() to push as many of them into the pipe at once as possible. > > The real problem is that GPIB is a bus, not a device. The GPIB driver > > should be a bus controller, not a device, and it should have multiple > > instances of a peripheral driver hung off it (one for each device on > > the bus). > > > > You'd then open each peripheral and implicitly anything you wrote to/ > > read from that peripheral would go to the device in question. > > > > This would make it much cleaner, eg. to support multiple processes > > talking to multiple devices on the bus, as well as to embed some > > intelligence into the kernel for some devices. > > You said it. That is exactly how I would like it to be done. I do have > plans to make the application multi-treaded. My client does want to > control several devices from multiple processes. I didn't mention this > before because I was trying to do one step at a time, but I guess I just > have to rewrite the whole driver from the beginning to do something like > this. Not at all. The bulk of the driver is the stuff that talks to the hardware; the infrastructure on top is pretty simple. If you have a deadline, by all means work with what you have. When you have a little more time, bring the matter back up and we can talk about how you might go about splitting the driver to busify it. -- \\ 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 Jul 23 08:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01943 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 08:19:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01898 for ; Thu, 23 Jul 1998 08:19:15 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id IAA05634; Thu, 23 Jul 1998 08:17:12 -0700 (PDT) (envelope-from dhw) Date: Thu, 23 Jul 1998 08:17:12 -0700 (PDT) From: David Wolfskill Message-Id: <199807231517.IAA05634@pau-amma.whistle.com> To: dglynn@vaview5.vavu.vt.edu, louie@TransSys.COM Subject: Re: PCI modems... Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <199807230348.XAA15671@whizzo.transsys.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From: "Louis A. Mamakos" >Date: Wed, 22 Jul 1998 23:48:49 -0400 >- While having a rockwell chipset is a good sign, you should be aware >that the quality of the analog front-end of the modem may be the limiting >factor that will affect what rate the modem manages to train at. >> For $55 is's not that bad although it has a rockwell chipset on it... I've been tracking this fairly closely, and to the best of my knowledge and belief, the Rockwell implementation of the proposed V.90 standard is not currently interoperable with the Lucent RABU (as in "PortMaster") implementation. It is my current understanding that Rockwell declined to participate in interoperability testing with Lucent until about a month or so ago. In any case, this may be an issue if there's an expectation that the MODEM's V.90 mode will be used for connection to a PortMaster. If connection to a PM is wanted, the K56Flex mode would undoubtedly work better. And it wouldn't surprise me in the slightest if the Rockwell V.90 implementation may need a tweak or two before it's both conformant with the actual standard (on track, as I understand it, for approval in September, 1998) and interoperability with Lucent gear. (It's certain that the Lucent code will need to be changed, as it's a beta version of ComOS that supports V.90 at all, and there remain some issues to be resolved. On the other hand, I fully expect that when Lucent releases the code (as non-beta), it will be solid.) david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 23 09:21:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11701 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 09:21:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA11696 for ; Thu, 23 Jul 1998 09:21:06 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA28869; Thu, 23 Jul 1998 09:20:07 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA10487; Thu, 23 Jul 1998 09:21:03 -0700 Date: Thu, 23 Jul 1998 09:21:03 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807231621.JAA10487@burdell.ece.arizona.edu> To: mike@smith.net.au CC: randal@comtest.com, dufault@hda.com, mike@smith.net.au, FreeBSD-hardware@FreeBSD.ORG, john@ece.arizona.edu In-reply-to: <199807230013.RAA02438@dingo.cdrom.com> (message from Mike Smith on Wed, 22 Jul 1998 17:13:40 -0700) Subject: Re: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Mike" == Mike Smith writes: Mike> I don't like this at all (as I pointed out to Randal). GPIB Mike> is a bus, and it should be treated like one. The GBIB Mike> driver should provide GPIB I/O services to a set of Mike> peripheral drivers (consider SCSI as an example). ioctl() Mike> is not good for I/O. OK, I might take another shot at this. I do see your point. I will try using the lower 5 bits of the minor number as the GPIB address (with the 32 address being some sort of "global" control device?). Bits above that will encode the card. Any flaws with this idea? I am not very familiar with the SCSI driver. (I just got my first SCSI machine ever a month ago - I like it, too). But now that you mention it, I see that GPIB is set up the same way with the bus controller and then any of a multitude of possible devices can be hooked up to it. I think that the peripheral drivers should be implemented in userland, IMHO. Would there be any advantages to those being in the kernel? This is really great getting feedback from you guys - let me know any other suggestions or concerns you might have. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 23 09:36:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14775 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 09:36:34 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA14670 for ; Thu, 23 Jul 1998 09:36:16 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA29286; Thu, 23 Jul 1998 09:35:31 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id JAA10489; Thu, 23 Jul 1998 09:36:27 -0700 Date: Thu, 23 Jul 1998 09:36:27 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807231636.JAA10489@burdell.ece.arizona.edu> To: randal@comtest.com CC: dufault@hda.com, mike@smith.net.au, FreeBSD-hardware@FreeBSD.ORG, john@ece.arizona.edu In-reply-to: <199807230102.PAA23786@oldyeller.comtest.com> (randal@comtest.com) Subject: Re: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Randal" == Randal S Masutani writes: Randal> So what exaclty do you have implemented? What functions Randal> do you have in ioctl()? Besides the main I/O, I have ioctl's to do bus management stuff like interface clear (IFC), triggering (GET), serial poll, and all that. I also have in the pipeline an ioctl to set up the controller parameters like 1) interrupt timeout 2) poll timeout 3) end of string (EOS) byte 4) termination stuff (EOI, EOS) 5) controller's GPIB address (right now it defaults to the minor number - lame) 6) T1 delay 7) more? There will probably be a gp_info structure that holds all this info, and an ioctl that fills the structure with the current configuration, and another to set it. After reading last night's posts, I definitely want to move the I/O into write() and read() with better usage of the minor numbers. That is a much better way to go all around. As far as the I/O goes, I plan on having three types: programmed I/O with polling, programmed I/O with interrupts, and DMA transfers with interrupts. Currently, the two programmed routines work (both read and write) and I am working on the DMA routine. The polling routine was mainly to get the driver working initially - I doubt people will use it very often. The driver selects which one to use based on if it was configured with an interrupt and DMA channel or not. I also have quite a bit of debugging stuff in there. A large portion of the code gets preprocessed out if debugging is turned off. I found these cards to be kind of difficult to program due to the huge number of different registers and possibilities. There really are a lot of features on these cards, and if you don't configure each of them exactly like you want, things don't work. On the other hand, a lot of the work of bus management is done in hardware, so the driver is actually simplified once you get it configured correctly. All this just led to a lot of debugging code in there. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 23 09:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17616 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 09:50:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles357.castles.com [208.214.167.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17515 for ; Thu, 23 Jul 1998 09:50:17 -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 JAA03068; Thu, 23 Jul 1998 09:49:21 -0700 (PDT) Message-Id: <199807231649.JAA03068@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: john@ece.arizona.edu (John Galbraith) cc: randal@comtest.com, dufault@hda.com, FreeBSD-hardware@FreeBSD.ORG Subject: Re: new GPIB driver In-reply-to: Your message of "Thu, 23 Jul 1998 09:21:03 PDT." <199807231621.JAA10487@burdell.ece.arizona.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Jul 1998 09:49:21 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >>>>> "Mike" == Mike Smith writes: > > Mike> I don't like this at all (as I pointed out to Randal). GPIB > Mike> is a bus, and it should be treated like one. The GBIB > Mike> driver should provide GPIB I/O services to a set of > Mike> peripheral drivers (consider SCSI as an example). ioctl() > Mike> is not good for I/O. > > OK, I might take another shot at this. I do see your point. I will > try using the lower 5 bits of the minor number as the GPIB address > (with the 32 address being some sort of "global" control device?). > Bits above that will encode the card. Any flaws with this idea? If you're going to have the GPIB driver do everything, then that's probably OK. (Is there some sort of 'extended' addressing scheme that lets you put more than 31 devices on the bus? If so, save more room for the address; there's lots of room in the minor). > I am not very familiar with the SCSI driver. (I just got my first > SCSI machine ever a month ago - I like it, too). But now that you > mention it, I see that GPIB is set up the same way with the bus > controller and then any of a multitude of possible devices can be > hooked up to it. > > I think that the peripheral drivers should be implemented in userland, > IMHO. Would there be any advantages to those being in the kernel? Yes; not least the ability to export a GPIB-specific API between the GPIB and peripheral driver, as well as the ability to implement callbacks (the GPIB driver calls the peripheral driver instead of the other way around), which would be useful eg. for the system running in listener rather than talker mode. If you have a -current system (or just browse the relevant bits via FTP) have a look at how the 'ppbus' stuff works. There's an ISA driver that handles talking to the parallel port, and it exports an API up to the generic ppbus code, which in turn exports a completely hardware independant API to the peripheral drivers. IMHO this is how GPIB "should" be done; it means that writing a driver for a new card becomes nothing more than matching the established hardware<->gbpibbus API. > This is really great getting feedback from you guys - let me know any > other suggestions or concerns you might have. As I said to Randall, I think the first thing to do is to get your current, more-or-less Cawthorne-compatible driver out and being tested. This'll help Randal out, as well as help you iron out any problems in your TNT code, etc. Once that's looking good, you can attack the busification happy that the hardware will behave. If you want more input, just keeping asking. 8) -- \\ 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 Jul 23 09:59:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19530 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 09:59:31 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19514 for ; Thu, 23 Jul 1998 09:59:27 -0700 (PDT) (envelope-from schofiel@xs4all.nl) Received: from xs2.xs4all.nl (root@xs2.xs4all.nl [194.109.6.43]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id SAA13326 for ; Thu, 23 Jul 1998 18:59:02 +0200 (CEST) Received: from excelsior (enterprise.xs4all.nl [194.109.14.215]) by xs2.xs4all.nl (8.8.8/8.8.6) with SMTP id SAA09774 for ; Thu, 23 Jul 1998 18:59:01 +0200 (MET DST) Message-ID: <35B76B85.7BF3@xs4all.nl> Date: Thu, 23 Jul 1998 18:57:41 +0200 From: Rob Schofield Reply-To: schofiel@xs4all.nl Organization: Knights of the Round Table, Ltd. X-Mailer: Mozilla 3.04Gold (WinNT; I) MIME-Version: 1.0 To: Free BSD Hardware list Subject: Imagination... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org .. needed for this. What would you recommend for a setup to: - digitise all my home videos - store digitally long term (cheaply, probably compressed) - play back to a TV (of course) - index all the stored movies? I would be basing this around a FreeBSD system, but relatively low cost/low power if possible (say a recent 2nd hand Pentium 166?), and would be prepared to invest in hot peripherals for the digitisation, storage and playback. It shouldn't need a keyboard monitor or mouse, but should be accessable via Ethernet for control purposes. It also needs to be connectable to a HiFi/Sound/Vision centre, probably through SCART. => In other words, the ultimate digital VCR..... So what would *you* do? Rob Schofield To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 23 11:04:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29454 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 11:04:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29426 for ; Thu, 23 Jul 1998 11:04:15 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with SMTP id LAA22360; Thu, 23 Jul 1998 11:03:31 -0700 (PDT) Date: Thu, 23 Jul 1998 11:03:31 -0700 (PDT) From: Brooks Davis Reply-To: brooks@one-eyed-alien.net To: Mike Smith cc: hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress Pro 100 Server vs. client adapter In-Reply-To: <199807071744.KAA00908@dingo.cdrom.com> 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 Tue, 7 Jul 1998, Mike Smith wrote: > You want the Pro 100/B or 100+, not the original 100. > > Paying more than about US$50 for either is too much. We just got bit by some 3c905B's from Micron and are looking to buy a couple of Pro 100+ cards. I can't seem to find anyone with prices in the $50 range. Could someone recomend a vendor? Thanks, Brooks Davis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 23 11:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05061 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 11:30:56 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05040 for ; Thu, 23 Jul 1998 11:30:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00302; Thu, 23 Jul 1998 11:28:50 -0700 (PDT) Message-Id: <199807231828.LAA00302@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: brooks@one-eyed-alien.net cc: Mike Smith , hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress Pro 100 Server vs. client adapter In-reply-to: Your message of "Thu, 23 Jul 1998 11:03:31 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Jul 1998 11:28:50 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, 7 Jul 1998, Mike Smith wrote: > > > You want the Pro 100/B or 100+, not the original 100. > > > > Paying more than about US$50 for either is too much. > > We just got bit by some 3c905B's from Micron and are looking to buy a > couple of Pro 100+ cards. I can't seem to find anyone with prices in the > $50 range. Could someone recomend a vendor? www.pricewatch.com The price war on them appears to have eased recently; most retailers are back in the $60-80 bracket again. -- \\ 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 Jul 23 12:24:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13641 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 12:24:26 -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 MAA13568 for ; Thu, 23 Jul 1998 12:23:56 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA13084; Thu, 23 Jul 1998 12:15:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdW13082; Thu Jul 23 19:15:15 1998 Date: Thu, 23 Jul 1998 12:15:13 -0700 (PDT) From: Julian Elischer To: Rob Schofield cc: Free BSD Hardware list Subject: Re: Imagination... In-Reply-To: <35B76B85.7BF3@xs4all.nl> 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 you need the system Justin is working on (the reason for CAM) I think they are digitizing the hollywood archives or something :-) julian On Thu, 23 Jul 1998, Rob Schofield wrote: > .. needed for this. > > What would you recommend for a setup to: > > - digitise all my home videos > - store digitally long term (cheaply, probably compressed) > - play back to a TV (of course) > - index all the stored movies? > > I would be basing this around a FreeBSD system, but relatively low > cost/low power if possible (say a recent 2nd hand Pentium 166?), and > would be prepared to invest in hot peripherals for the digitisation, > storage and playback. It shouldn't need a keyboard monitor or mouse, but > should be accessable via Ethernet for control purposes. It also needs to > be connectable to a HiFi/Sound/Vision centre, probably through SCART. > > => In other words, the ultimate digital VCR..... > > So what would *you* do? > > Rob Schofield > > 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 Thu Jul 23 18:59:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14648 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 18:59:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cc-server9.massey.ac.nz (cc-server9.massey.ac.nz [130.123.128.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA14625 for ; Thu, 23 Jul 1998 18:59:18 -0700 (PDT) (envelope-from crh@outpost.co.nz) Received: from acme.gen.nz by cc-server9.massey.ac.nz id <12783-0@cc-server9.massey.ac.nz>; Fri, 24 Jul 1998 13:57:01 +1200 Received: from officedonkey by acme.gen.nz with smtp (Smail3.1.29.1 #2) id m0yzVcr-0028ziC; Fri, 24 Jul 1998 12:22:21 +1200 Message-Id: Comments: Authenticated sender is From: Craig Harding Organization: Outpost Digital Media Ltd To: Rob Schofield Date: Fri, 24 Jul 1998 11:57:47 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Imagination... Reply-to: crh@outpost.co.nz CC: freebsd-hardware@FreeBSD.ORG In-reply-to: <35B76B85.7BF3@xs4all.nl> X-mailer: Pegasus Mail for Windows (v2.52) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rob Schofield wrote: > What would you recommend for a setup to: > > - digitise all my home videos > - store digitally long term (cheaply, probably compressed) > - play back to a TV (of course) > - index all the stored movies? > > I would be basing this around a FreeBSD system, but relatively low > cost/low power if possible (say a recent 2nd hand Pentium 166?), and > would be prepared to invest in hot peripherals for the digitisation, > storage and playback. It shouldn't need a keyboard monitor or mouse, > but should be accessable via Ethernet for control purposes. It also > needs to be connectable to a HiFi/Sound/Vision centre, probably > through SCART. > > => In other words, the ultimate digital VCR..... > > So what would *you* do? Well, the real issue is the video compression format. Sure, you can do it with uncompressed video (it makes some things a lot easier), but you're going to need a very (very) fast server and enormous amounts of hard drive. Consider it this way, in the broadcast industry boxes that do this (such as the excellent Pluto video server based on freebsd which I recently got to see in person - nice deskstop display) are priced around $US20k and up (emphasis on the up). So let's get realistic. What you really want is MPEG1 or 2 video. I'm not all that hot on MPEG1, but at least it's affordable. There's now a range of MPEG2 playback devices, so all you need are device drivers for FreeBSD and you'd be in business. The problem is input. You need a hardware based MPEG2 compression card, and last time I looked (8 months ago) they were hideously expensive. Like, NZ$15k (about US$7.5k). They may have come down a bit, and you can probably get them a bit cheaper in the US than I can here, but that's still big bucks we're talking about. Long term I expect MPEG2 encoders to drop dramatically to the $1k-$2k mark, this is a typical pattern for I/O cards in the video market. If you can get an MPEG2 video stream, you can have very decent video quality for 1MB/s of bandwidth, at that's trivial for nearly any modern Pentium PC. BTW, if you can do this cheaply and reliably, then forget the VCR angle (from a consumer perspective), you have a video server that would be in demand globally. I've wanted to do the same thing, but lack (a) the funds and (b) the nous to develop appropriate device drivers. -- C. -- Craig Harding Head of Postproduction, Outpost Digital Media Ltd "I don't know about God, I just think we're handmade" - Polly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 23 22:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20407 for freebsd-hardware-outgoing; Thu, 23 Jul 1998 22:37:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from user2.dancris.com (mail.dancris.com [204.177.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20388 for ; Thu, 23 Jul 1998 22:37:06 -0700 (PDT) (envelope-from p@mail.dancris.com) Received: from [204.177.81.182] by user2.dancris.com (8.8.8/DANCRIS-1.2) id WAA02497 for <>; Thu, 23 Jul 1998 22:33:59 -0700 (MST) Message-Id: <199807240533.WAA02497@user2.dancris.com> X-Mailer: Eudora Pro 1.1 for Newton Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 23 Jul 1998 22:32:00 -0700 To: From: Peter Jones Subject: Install From CD-ROM Trouble Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi everyone, I am trying to install 2.2.6 from CD, the computer boots from the CD just fine. After the last warning before newfs, I hit OK and then the computer restarts. Sometimes before newfs and sometimes the install starts and the computer restarts at about 4% done with bin. The CD-ROM Drive is IDE Primary Slave. The Hard Drive is IDE Primary Master. All Hardware is supported. FreeBSD will be the only OS on this system. I hope that this is all the info you need. I would be glad to hear anything at all so that I would be forced to stop pulling my hair out and use my brain. Thanks, Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 05:57:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02052 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 05:57:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ux10.cso.uiuc.edu (swwilso1@ux10.cso.uiuc.edu [128.174.5.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02047; Fri, 24 Jul 1998 05:57:23 -0700 (PDT) (envelope-from swwilso1@students.uiuc.edu) Received: from localhost (swwilso1@localhost) by ux10.cso.uiuc.edu (8.8.8/8.8.8) with SMTP id HAA19567; Fri, 24 Jul 1998 07:56:55 -0500 (CDT) X-Authentication-Warning: ux10.cso.uiuc.edu: swwilso1 owned process doing -bs Date: Fri, 24 Jul 1998 07:56:55 -0500 (CDT) From: steven wesley wilson X-Sender: swwilso1@ux10.cso.uiuc.edu To: freebsd-questions cc: freebsd-hardware Subject: Supported Hardware in FreeBSD 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 need advice on two things: 1. I'm considering buying a celeron 266 cpu with an Abit BX6 motherboard. Will FreeBSD run with this cpu/board combo? 2. If I get item 1. I'll eventually want an AGP video board. Would someone please recommend an AGP that works well with XFree86. Thanks in advance, Steve Wilson swwilso1@uiuc.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 09:18:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06710 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 09:18:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alcatel.fr (ns.celwave.tm.fr [194.133.58.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06642; Fri, 24 Jul 1998 09:17:43 -0700 (PDT) (envelope-from THIERRY.HERBELOT@telspace.alcatel.fr) From: THIERRY.HERBELOT@telspace.alcatel.fr Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (ALCANET/SMTP.9.9.9) with ESMTP id QAA30342; Fri, 24 Jul 1998 16:46:28 +0200 Received: from aifhs1.alcatel.fr (aifhs1.alcatel.fr [155.132.180.86]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id QAA25588; Fri, 24 Jul 1998 16:34:06 +0200 (MET DST) Received: from aifhs2.alcatel.fr (localhost [127.0.0.1]) by aifhs1.alcatel.fr (8.8.8/8.8.8) with ESMTP id QAA22716; Fri, 24 Jul 1998 16:36:30 +0200 (MET DST) Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id QAA24797; Fri, 24 Jul 1998 16:32:20 +0200 (MET DST) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.7.6/8.7.3) with SMTP id QAA07594; Fri, 24 Jul 1998 16:33:57 +0200 (MET DST) Received: from telspace.alcatel.fr by telss1 (4.1/SMI-4.1) id AA24177; Fri, 24 Jul 98 16:22:30 +0200 Received: from localhost by telspace.alcatel.fr with SMTP (1.40.112.12/16.2) id AA090169867; Fri, 24 Jul 1998 16:17:47 +0200 X-Openmail-Hops: 1 Date: Fri, 24 Jul 98 16:17:43 +0200 Message-Id: In-Reply-To: Subject: Supported Hardware in FreeBSD Mime-Version: 1.0 To: swwilso1@students.uiuc.edu Cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII; name="Supported" Content-Disposition: inline; filename="Supported" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > 2. If I get item 1. I'll eventually want an AGP video board. Would > someone please recommend an AGP that works well with XFree86. > FreeBSd by itself will run on whatever graphics board : FreeBSD uses only the text display (console) Xfree86 (The free X-Windows server that runs the graphical Interface) uses the graphics board. You can check the latest supported hardware on www.xfree86.org. Thierry > Thanks in advance, > > Steve Wilson > swwilso1@uiuc.edu > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Fri Jul 24 09:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14421 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 09:58:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA14252; Fri, 24 Jul 1998 09:56:44 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id SAA00622; Fri, 24 Jul 1998 18:55:57 +0200 Message-ID: <35B8BC9C.44A7F05A@we.lc.ehu.es> Date: Fri, 24 Jul 1998 18:55:57 +0200 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.05 [en] (X11; I; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: steven wesley wilson CC: freebsd-questions , freebsd-hardware Subject: Re: Supported Hardware in FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org steven wesley wilson wrote: > > 2. If I get item 1. I'll eventually want an AGP video board. Would > someone please recommend an AGP that works well with XFree86. > Yes, the Matrox Millennium II AGP works like a charm. With 4 MB of WRAM you can reach 1152x864 at 32 bpp. The XFree86's driver for this card is FAST, and I have not had any image problems. -- JM ----------------------------------------------------------------------- Jose M. Alcaide | mailto:jose@we.lc.ehu.es Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electronica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 11:04:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29428 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 11:04:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29357 for ; Fri, 24 Jul 1998 11:04:13 -0700 (PDT) (envelope-from keithm@hprrc726.rose.hp.com) Received: from hprrc726.rose.hp.com (hprrc181.rose.hp.com [15.56.217.181]) by atlrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id OAA07846 for ; Fri, 24 Jul 1998 14:03:26 -0400 (EDT) Received: by hprrc726.rose.hp.com (1.37.109.16/15.5+ECS 3.3) id AA167143429; Fri, 24 Jul 1998 11:03:49 -0700 From: Keith Middlekauff Message-Id: <199807241803.AA167143429@hprrc726.rose.hp.com> Subject: ASUS P2L97-S To: freebsd-hardware@FreeBSD.ORG Date: Fri, 24 Jul 98 11:03:48 PDT Mailer: Elm [revision: 70.85] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have a problem with this board, P2L97-S, and using only a single ended scsi disk. I have nothing on the wide interface and one disk on the narrow. The disk is terminated. This is my message when I boot. FreeBSD 2.2.6-RELEASE #0: Fri Jul 24 09:38:13 PDT 1998 ahc0 rev 0 int a irq 12 on pci0:6:0 Illegal cable configuration!!. Only two connectors on the adapter may be used at a time!ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "HP C3725S 4299" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) Any help or ideas appreciated Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 14:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02125 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 14:19:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from shell6.ba.best.com (jkb@shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02117; Fri, 24 Jul 1998 14:19:42 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) with SMTP id OAA02754; Fri, 24 Jul 1998 14:19:17 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Fri, 24 Jul 1998 14:19:17 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: steven wesley wilson cc: freebsd-questions , freebsd-hardware Subject: Re: Supported Hardware in FreeBSD 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, 24 Jul 1998, steven wesley wilson wrote: >I need advice on two things: > >1. I'm considering buying a celeron 266 cpu with an Abit BX6 motherboard. >Will FreeBSD run with this cpu/board combo? Yes > >2. If I get item 1. I'll eventually want an AGP video board. Would >someone please recommend an AGP that works well with XFree86. I use XiG server -- Everything matrox works fine here. > >Thanks in advance, > >Steve Wilson >swwilso1@uiuc.edu > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" 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 Fri Jul 24 15:56:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17330 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 15:56:21 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17221 for ; Fri, 24 Jul 1998 15:55:19 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from tempest ([195.121.58.75]) by smtp02.wxs.nl (Netscape Messaging Server 3.52) with SMTP id AAA59EC for ; Sat, 25 Jul 1998 00:54:12 +0200 X-Sender: skywise@pop.wxs.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Sat, 25 Jul 1998 00:56:56 +0200 To: freebsd-hardware From: Jeroen Ruigrok/Asmodai Subject: NeoMagic/Dell Latitude CP Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <77182A661523.AAA59EC@smtp02.wxs.nl> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well met, I found some documents on the web about the NeoMagic Magicgraph chipset but they are for the 2.2.5 release as far as I can tell. Anyone else have updated XF86Config files for this chipset? Any other pointers info on this chip would be welcome, thanks in advance and hopefully not posted to the wrong list =) -- Jeroen Ruigrok van der Werven / Asmodai ICQ-UIN: 1564317 .:. Ninth Circle Enterprises Network/Security Specialist As far as ye can't tell, I am the Future in Computer Hell... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 16:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23923 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 16:30:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from send1c.yahoomail.com (send1c.yahoomail.com [205.180.60.38]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA23900 for ; Fri, 24 Jul 1998 16:30:50 -0700 (PDT) (envelope-from omenzel@yahoo.com) Message-ID: <19980724233237.24302.rocketmail@send1c.yahoomail.com> Received: from [209.109.224.220] by send1c; Fri, 24 Jul 1998 16:32:37 PDT Date: Fri, 24 Jul 1998 16:32:37 -0700 (PDT) From: Oliver Menzel Subject: 3com 980 To: freebsd-net@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does freebsd support 3COM 980 Server PCI NIC?? I just got 2 3com 980's, but not sure if freebsd supports them It would be a real shame if it doesn't.. Anyone know? Oliver _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 16:43:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26545 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 16:43:16 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from shell6.ba.best.com (jkb@shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26537 for ; Fri, 24 Jul 1998 16:43:14 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.9.0/8.9.0/best.sh) with SMTP id QAA12489; Fri, 24 Jul 1998 16:42:49 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Fri, 24 Jul 1998 16:42:49 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: Jeroen Ruigrok/Asmodai cc: freebsd-hardware Subject: Re: NeoMagic/Dell Latitude CP In-Reply-To: <77182A661523.AAA59EC@smtp02.wxs.nl> 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 Hello, I am using this same exact laptop (166Mhz). I am using XiG server however and it works just fine under FreeBSD. Check out www.xig.com -- Yan Jan Koum jkb@best.com | "Turn up the lights; I don't want www.FreeBSD.org -- The Power to Serve | to go home in the dark." On Sat, 25 Jul 1998, Jeroen Ruigrok/Asmodai wrote: >Well met, > >I found some documents on the web about the NeoMagic Magicgraph chipset but >they are for the 2.2.5 release as far as I can tell. > >Anyone else have updated XF86Config files for this chipset? > >Any other pointers info on this chip would be welcome, > >thanks in advance and hopefully not posted to the wrong list =) > > >-- >Jeroen Ruigrok van der Werven / Asmodai >ICQ-UIN: 1564317 .:. Ninth Circle Enterprises >Network/Security Specialist > >As far as ye can't tell, I am the Future in Computer Hell... > >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 Fri Jul 24 18:22:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15568 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 18:22:48 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from oldyeller.comtest.com (comtest.hits.net [206.127.244.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15535 for ; Fri, 24 Jul 1998 18:22:34 -0700 (PDT) (envelope-from randal@comtest.com) Received: from graphics.comtest.com (graphics.comtest.com [206.127.245.194]) by oldyeller.comtest.com (8.8.8/8.8.8) with SMTP id PAA23786; Wed, 22 Jul 1998 15:02:07 -1000 (HST) (envelope-from randal@comtest.com) Message-Id: <199807230102.PAA23786@oldyeller.comtest.com> From: "Randal S. Masutani" Organization: ComTest Technologies, Inc. To: john@ece.arizona.edu (John Galbraith) Date: Wed, 22 Jul 1998 14:55:55 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: new GPIB driver Reply-to: randal@comtest.com CC: dufault@hda.com, mike@smith.net.au, FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807222331.QAA10025@burdell.ece.arizona.edu> References: <199807221926.JAA23230@oldyeller.comtest.com> (randal@comtest.com) X-mailer: Pegasus Mail for Windows (v3.01b) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22 Jul 98, at 16:31, John Galbraith wrote: > OK, but if he signed a NDA, we can't exactly use that info in the > driver, and distribute it all over the planet. At least not according > to the agreement. If he wants to give me or you the information, it > seems to be a legal risk (and rightly so) for your customer. Yes, you are right. I didn't say that. Nobody heard that. > It just struck me that I could have the lower minor numbers work like > Fred's driver, and some upper number (like 32) to be the main special > file that you would open when you just wanted to dump data directly to > a specific device. Not a big deal for now, though. Right now, I > haven't even implemented write() and read(), other than to return the > "system call not implemented" error. So what exaclty do you have implemented? What functions do you have in ioctl()? Randal ------------------------------------------------------------------------- ComTest Technologies, Inc. 3049 Ualena St., Suite 1005 Honolulu, Hawaii 96819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 18:22:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15587 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 18:22:54 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from oldyeller.comtest.com (comtest.hits.net [206.127.244.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15555 for ; Fri, 24 Jul 1998 18:22:40 -0700 (PDT) (envelope-from randal@comtest.com) Received: from graphics.comtest.com (graphics.comtest.com [206.127.245.194]) by oldyeller.comtest.com (8.8.8/8.8.8) with SMTP id JAA23230; Wed, 22 Jul 1998 09:26:59 -1000 (HST) (envelope-from randal@comtest.com) Message-Id: <199807221926.JAA23230@oldyeller.comtest.com> From: "Randal S. Masutani" Organization: ComTest Technologies, Inc. To: john@ece.arizona.edu (John Galbraith) Date: Wed, 22 Jul 1998 09:20:55 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: new GPIB driver Reply-to: randal@comtest.com CC: Peter Dufault , Mike Smith , FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807221607.JAA09866@burdell.ece.arizona.edu> References: <199807220011.OAA20288@oldyeller.comtest.com> (randal@comtest.com) X-mailer: Pegasus Mail for Windows (v3.01b) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22 Jul 98, at 9:07, John Galbraith wrote: > OK. I was hacking on it yesterday here at work and found a few things > I need to look at that I discovered with the higher end equipment that > I have here. This week I am going to put two cards in the machine and > really try to tweak the performance also, although I think my code is > useful even if I don't quite get the transfer rate that I want yet. > > Give me a couple of days to absorb the feedback I have received from > the mailing list and write some documentation (and fix a couple of > bugs 8-) ). I will then send you my code, and hopefully we can work > together making sure that remaining bugs are few and far between. > > Thanks for the enthusiasm - it is nice to know that others are > interested in one's work! > > John Thanks John. I will be glad to work with you on your driver. My customer has signed the non-disclosure with NI for their TNT controller chip and will hopefully get some docs soon(but I've been waiting for over a month now. Very typical of NI I suppose.) I need to have NI 488.2 library interface for the project I am working on. Currently I am only required to implement about 10 functions from NI's library and that's all I have time for, due to my deadline. I am currently working on getting it working with Freds code. >From your last email I take it that you haven't implemented any of NI's 488.2 library calls? So do you have a similar interface to Freds code? Randal ------------------------------------------------------------------------- ComTest Technologies, Inc. 3049 Ualena St., Suite 1005 Honolulu, Hawaii 96819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 18:23:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15609 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 18:23:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from oldyeller.comtest.com (comtest.hits.net [206.127.244.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15570 for ; Fri, 24 Jul 1998 18:22:48 -0700 (PDT) (envelope-from randal@comtest.com) Received: from graphics.comtest.com (graphics.comtest.com [206.127.245.194]) by oldyeller.comtest.com (8.8.8/8.8.8) with SMTP id PAA23783; Wed, 22 Jul 1998 15:02:04 -1000 (HST) (envelope-from randal@comtest.com) Message-Id: <199807230102.PAA23783@oldyeller.comtest.com> From: "Randal S. Masutani" Organization: ComTest Technologies, Inc. To: Mike Smith Date: Wed, 22 Jul 1998 14:55:55 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: GPIB drivers? Reply-to: randal@comtest.com CC: Peter Dufault , john@ece.arizona.edu (John Galbraith), FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807230007.RAA02391@dingo.cdrom.com> References: Your message of "Wed, 22 Jul 1998 12:12:00 -1000." <199807222218.MAA23397@oldyeller.comtest.com> X-mailer: Pegasus Mail for Windows (v3.01b) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22 Jul 98, at 17:07, Mike Smith wrote: > > Freds driver is using copyin/copyout in the ioctl(). > > So is this bad to do this(copyin/out) here? > > It's bad insofar as using ioctl() for data transfer is generally > considered the wrong way to do it. You should be using read and write > to do data transfer. If not for data transfer how about configuring the driver settings like; timeout, bus timing, end of line char,...? > > case GPIBWRITE: > > error=copyin(gd->count,&count,sizeof(count)); > > if (error!=0) return(error); > > This should use fuword() I checked the fuword() manpage sound good. I guess i could use also suword() to return values to userspace? > > The standard read/write calls are using uiomove(). > > ... which is how IMHO it should be done. > > > I am not familiar with these issues but the driver does work. Why is bad > > to use copyin/out vs. uiomove? I would appreciate any input. > > copyin/out precludes calling the driver from elsewhere within the > kernel, and if you use it in a read/write/strategy routine, it means > you can't handle readv/writev easily. (The latter are a godsend if > you're trying to do scatter-gather style I/O). Not familiar with this (scatter-gather)concept, something I should learn? > The real problem is that GPIB is a bus, not a device. The GPIB driver > should be a bus controller, not a device, and it should have multiple > instances of a peripheral driver hung off it (one for each device on > the bus). > > You'd then open each peripheral and implicitly anything you wrote to/ > read from that peripheral would go to the device in question. > > This would make it much cleaner, eg. to support multiple processes > talking to multiple devices on the bus, as well as to embed some > intelligence into the kernel for some devices. You said it. That is exactly how I would like it to be done. I do have plans to make the application multi-treaded. My client does want to control several devices from multiple processes. I didn't mention this before because I was trying to do one step at a time, but I guess I just have to rewrite the whole driver from the beginning to do something like this. > > Compare GPIB to SCSI, if you like, for an idea as to what I mean. Randal ------------------------------------------------------------------------- ComTest Technologies, Inc. 3049 Ualena St., Suite 1005 Honolulu, Hawaii 96819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 24 21:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07131 for freebsd-hardware-outgoing; Fri, 24 Jul 1998 21:57:31 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA07126 for ; Fri, 24 Jul 1998 21:57:30 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from [208.143.84.54] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id qa377822 for ; Fri, 24 Jul 1998 23:56:16 -0500 Received: (from tom@localhost) by peeper.TOJ.org (8.8.8/8.8.8) id XAA03653 for freebsd-hardware@FreeBSD.ORG; Fri, 24 Jul 1998 23:57:21 -0500 (CDT) (envelope-from tom) Message-ID: <19980724235650.B3582@TOJ.org> Date: Fri, 24 Jul 1998 23:56:50 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: Re: ASUS P2L97-S References: <199807241803.AA167143429@hprrc726.rose.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199807241803.AA167143429@hprrc726.rose.hp.com>; from Keith Middlekauff on Fri, Jul 24, 1998 at 11:03:48AM -0700 Reply_To: Tom Jackson Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 24, 1998 at 11:03:48AM -0700, Keith Middlekauff wrote: > Hello, well hello I have the ds and its a great board. I'm not an expert but since you have such a simple setup I'll try. Using the EZSCSI setup, ctrl-A at bootup brings it up, choose the set all to default option. This sets everything reasonable. Use the scsi utility, part of EZSCSI, to check that your adapter and drive are being read correctly. The adapter should be set to scsi id 7 and the drive to 0. If still having problem, try another cable. *Do* read the handbook on scsi; it's very good. Good luck, > > I have a problem with this board, P2L97-S, and using only a single ended > scsi disk. > > I have nothing on the wide interface and one disk on the narrow. The > disk is terminated. > > This is my message when I boot. > > FreeBSD 2.2.6-RELEASE #0: Fri Jul 24 09:38:13 PDT 1998 > > ahc0 rev 0 int a irq 12 on pci0:6:0 > Illegal cable configuration!!. Only two connectors on the adapter may be used at > a time!ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc0 waiting for scsi devices to settle > (ahc0:0:0): "HP C3725S 4299" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) > > Any help or ideas appreciated > > Keith > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 25 08:19:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28425 for freebsd-hardware-outgoing; Sat, 25 Jul 1998 08:19:34 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.eunet.ch (mail.eunet.ch [146.228.10.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28419 for ; Sat, 25 Jul 1998 08:19:32 -0700 (PDT) (envelope-from fjaccard@webshuttle.ch) Received: from wwwsw.webshuttle.ch (www.webshuttle.ch [146.228.6.1]) by mail.eunet.ch (8.8.6/1.34) via ESMTP id PAA29138 for ; Sat, 25 Jul 1998 15:18:35 GMT env-from (fjaccard@webshuttle.ch) Received: from Asus233 (dyna-mo-22.dial.eunet.ch [193.72.151.245]) by wwwsw.webshuttle.ch (8.8.6/8.8.2) with SMTP id RAA28362 for ; Sat, 25 Jul 1998 17:18:32 +0200 (MET DST) Message-Id: <199807251518.RAA28362@wwwsw.webshuttle.ch> From: "Francois Jaccard" To: Subject: Support for Asus P2B-L? Date: Sat, 25 Jul 1998 17:18:32 +0200 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I would like to know if the LAN chip (Intel 8255b) and the 440BX chip of the Asus P2B-L motherboard are supported under 3.0-current. I searched the archives but found nothing. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 25 10:14:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09200 for freebsd-hardware-outgoing; Sat, 25 Jul 1998 10:14:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09195 for ; Sat, 25 Jul 1998 10:14:35 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id MAA17913; Sat, 25 Jul 1998 12:50:05 -0400 Date: Sat, 25 Jul 1998 12:50:05 -0400 (EDT) From: Jamie Bowden To: Keith Middlekauff cc: freebsd-hardware@FreeBSD.ORG Subject: Re: ASUS P2L97-S In-Reply-To: <199807241803.AA167143429@hprrc726.rose.hp.com> 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, 24 Jul 1998, Keith Middlekauff wrote: > Hello, > > I have a problem with this board, P2L97-S, and using only a single ended > scsi disk. > > I have nothing on the wide interface and one disk on the narrow. The > disk is terminated. > > This is my message when I boot. > > FreeBSD 2.2.6-RELEASE #0: Fri Jul 24 09:38:13 PDT 1998 > > ahc0 rev 0 int a irq 12 on pci0:6:0 > Illegal cable configuration!!. Only two connectors on the adapter may be used at > a time!ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc0 waiting for scsi devices to settle > (ahc0:0:0): "HP C3725S 4299" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) > > Any help or ideas appreciated Make sure your scsi bios has termination set to auto, or that you don't have all possible chans terminated in the bios if auto bugs you. I caused this message to pop up on freebsd by putting a terminator on the external scsi interface of my 2940uw, while simultaneoulsy using both 50 and 68 pin internal interfaces. It doesn't like all three points to be terminated (understandably so), even if there are no devices on the other points of entry. -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message