From owner-freebsd-hardware Mon Jul 15 02:25:18 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA21231 for hardware-outgoing; Mon, 15 Jul 1996 02:25:18 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-180.ut.nl.ibm.net [139.92.42.180]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA21220; Mon, 15 Jul 1996 02:25:08 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id LAA02500; Sun, 7 Jul 1996 11:27:07 +0200 (MET DST) Message-Id: <199607070927.LAA02500@vector.jhs.no_domain> To: Joel Yancey cc: "Jacob M. Parnas" , Richard Foulk , hardware@freebsd.org, bsdi-users@bsdi.com Subject: Re: cable vs. ISDN From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (later) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Sat, 06 Jul 1996 20:15:24 MDT." Date: Sun, 07 Jul 1996 11:27:06 +0200 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Joel Yancey > > All this talk about Cable modems. i Really dont think there such a great > idea. Please remove hardware@freebsd.org from cc line. Thread has departed from hardware@freebsd.org remit, (echo "info hardware" | mail majordomo@freebsd.org to verify ) I & many other FreeBSD users have zero availability to cable modems. Newsroups exist ... failing that ... move to chat@freebsd.org please. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-hardware Tue Jul 16 11:20:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19868 for hardware-outgoing; Tue, 16 Jul 1996 11:20:31 -0700 (PDT) Received: from webserver.casc.com (webserver.casc.com [152.148.41.200]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA19863; Tue, 16 Jul 1996 11:20:29 -0700 (PDT) Received: from casc.com (alpo [152.148.10.6]) by webserver.casc.com (8.6.12/8.6.12) with ESMTP id OAA16599; Tue, 16 Jul 1996 14:19:34 -0400 Received: from centime.cascade by casc.com (SMI-8.6/SMI-SVR4-bob.2) id OAA05745; Tue, 16 Jul 1996 14:20:37 -0400 Received: by centime.cascade (5.x/SMI-SVR4) id AA12434; Tue, 16 Jul 1996 14:20:34 -0400 Date: Tue, 16 Jul 1996 14:20:34 -0400 From: conta@alpo.casc.com (Alex Conta) Message-Id: <9607161820.AA12434@centime.cascade> To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 Cc: conta@alpo.casc.com X-Sun-Charset: US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk SCSI hardware/freebsd problem: 1. I have an Adaptec 2940 PCI-SCSI-2 adapter that works just fine under FreeBSD 2.1 on a DEC Starion 960 PC (SCSI-2 hard disk drive + cd-rom). The same adapter works fine on a Compaq ProLinea 5100 (SCSI hard disk and cd-rom) under Windows 3.1, but it does not work when I try to install FreeBSD from a CD-ROM distribution. The installation fails because the adapter is not recognized. Booting with "-c" and setting manually the IRQ, Port Address, and other parameters didn't help. Known problem? Known solution? 2. Any plans to add support for the AMD SCSI adapter that is embedded with Compaq DexPro 6200 XL? Alex From owner-freebsd-hardware Tue Jul 16 11:53:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22932 for hardware-outgoing; Tue, 16 Jul 1996 11:53:45 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA22911; Tue, 16 Jul 1996 11:53:40 -0700 (PDT) Message-Id: <199607161853.LAA22911@freefall.freebsd.org> To: conta@alpo.casc.com (Alex Conta) cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 In-reply-to: Your message of "Tue, 16 Jul 1996 14:20:34 EDT." <9607161820.AA12434@centime.cascade> Date: Tue, 16 Jul 1996 11:53:40 -0700 From: "Justin T. Gibbs" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >SCSI hardware/freebsd problem: > >1. > >I have an Adaptec 2940 PCI-SCSI-2 adapter that works just fine under FreeBSD >2.1 on a DEC Starion 960 PC (SCSI-2 hard disk drive + cd-rom). > >The same adapter works fine on a Compaq ProLinea 5100 (SCSI hard disk and >cd-rom) under Windows 3.1, but it does not work when I try to install FreeBSD >from a CD-ROM distribution. > >The installation fails because the adapter is not recognized. Booting with >"-c" and setting manually the IRQ, Port Address, and other parameters didn't >help. The 2940 shouldn't show up in Userconfig anymore. It is not an ISA device. >Known problem? Known solution? This is the first I've heard of this kind of problem. Perhaps our PCI code is having problems with this board. >Alex > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Tue Jul 16 12:20:35 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27439 for hardware-outgoing; Tue, 16 Jul 1996 12:20:35 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA27428; Tue, 16 Jul 1996 12:20:31 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA22308 (5.67b/IDA-1.5); Tue, 16 Jul 1996 21:20:17 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00899; Tue, 16 Jul 1996 21:20:08 +0200 (MET DST) Date: Tue, 16 Jul 1996 21:20:08 +0200 (MET DST) Message-Id: <199607161920.VAA00899@x14.mi.uni-koeln.de> From: Stefan Esser To: conta@alpo.casc.com (Alex Conta) Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 In-Reply-To: <9607161820.AA12434@centime.cascade> References: <9607161820.AA12434@centime.cascade> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alex Conta writes: > > SCSI hardware/freebsd problem: > > 1. > > I have an Adaptec 2940 PCI-SCSI-2 adapter that works just fine under FreeBSD > 2.1 on a DEC Starion 960 PC (SCSI-2 hard disk drive + cd-rom). > > The same adapter works fine on a Compaq ProLinea 5100 (SCSI hard disk and > cd-rom) under Windows 3.1, but it does not work when I try to install FreeBSD > from a CD-ROM distribution. > > The installation fails because the adapter is not recognized. Booting with > "-c" and setting manually the IRQ, Port Address, and other parameters didn't > help. Please enter "-v" at the "Boot: " prompt and send me all numbers from the lines starting with pcibus_setup or pcibus_check. If it reports success in the pcibus_check line, then I need any information about devices found on the PCI bus. > Known problem? Known solution? Compaq caused lots of problems because of their knowingly ignoring the PCI specs. I once got a reply that it wouldn't matter, since the BIOS and their drivers worked around the problems introduced this way. But what they didn't care about was, that the required workaround might break support for other systems. They don't bother, since they know their drivers are only used with their machines. But we hardly want to have a special FreeBSD version just for Compaq machines ... :) > 2. > > Any plans to add support for the AMD SCSI adapter that is embedded with > Compaq DexPro 6200 XL? There was a message from Tekram recently, who seem to offer a SCSI board based on the same chip and who seemed to be interested in having it supported under FreeBSD. I sent them a reply, but did not hear from them thereafter ... Many people have asked for support of the AMD SCSI chip. But since it is far less powerful than the NCR 53c810, which is available for some $70, nobody bothered to actually write a driver for it ... I understand that it might be good enough to connect an external CDROM or tape ... (It is a bus-master controller, but requires the CPU to handle disconnect and that means that there are multiple interrupts per transfer required and also that SCSI latencies are being introduced which limit the SCSI throughput. The NCR 53c810 as well as the Adaptec 2940 series offers a small CPU as part of the host adapter.) Reagrds, STefan From owner-freebsd-hardware Tue Jul 16 12:23:16 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA27815 for hardware-outgoing; Tue, 16 Jul 1996 12:23:16 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA27787; Tue, 16 Jul 1996 12:23:10 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA22315 (5.67b/IDA-1.5); Tue, 16 Jul 1996 21:22:52 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id VAA00902; Tue, 16 Jul 1996 21:22:39 +0200 (MET DST) Date: Tue, 16 Jul 1996 21:22:39 +0200 (MET DST) Message-Id: <199607161922.VAA00902@x14.mi.uni-koeln.de> From: Stefan Esser To: "Justin T. Gibbs" Cc: conta@alpo.casc.com (Alex Conta), freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 In-Reply-To: <199607161853.LAA22911@freefall.freebsd.org> References: <9607161820.AA12434@centime.cascade> <199607161853.LAA22911@freefall.freebsd.org> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs writes: > The 2940 shouldn't show up in Userconfig anymore. It is not an ISA device. > > >Known problem? Known solution? > > This is the first I've heard of this kind of problem. Perhaps our PCI > code is having problems with this board. No, it most probably is another problem with a PCI chip set in a Compaq machine ... :( Regards, STefan From owner-freebsd-hardware Tue Jul 16 12:25:16 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA28140 for hardware-outgoing; Tue, 16 Jul 1996 12:25:16 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-139.ut.nl.ibm.net [139.92.42.139]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA28024; Tue, 16 Jul 1996 12:24:49 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id WAA03841; Mon, 15 Jul 1996 22:37:13 +0200 (MET DST) Message-Id: <199607152037.WAA03841@vector.jhs.no_domain> To: hardware@freebsd.org cc: chat@freebsd.org Subject: Re: your mail From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (later) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Thu, 11 Jul 1996 10:15:40 EDT." Date: Mon, 15 Jul 1996 22:37:12 +0200 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To the USA/Canadian Cable comms enthusiasts currently blathering away on Cc: hardware@freebsd.org, bsdi-users@bsdi.com A 2nd reminder: hardware@freebsd.org Is NOT for the discussion of Americas' regional cable networking technology ! It IS for the world wide discussion of FreeBSD hardware. If you don't believe do this: echo "info freebsd-hardware" | mail majordomo@freebsd.org This thread long ceased being appropriate to FreeBSD, so _Please_ Either move it to chat@freebsd.org or to a newsgroup. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-hardware Tue Jul 16 15:07:07 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29338 for hardware-outgoing; Tue, 16 Jul 1996 15:07:07 -0700 (PDT) Received: from webserver.casc.com (webserver.casc.com [152.148.41.200]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA29332; Tue, 16 Jul 1996 15:07:03 -0700 (PDT) Received: from casc.com (alpo [152.148.10.6]) by webserver.casc.com (8.6.12/8.6.12) with ESMTP id RAA17702; Tue, 16 Jul 1996 17:55:27 -0400 Received: from centime.cascade by casc.com (SMI-8.6/SMI-SVR4-bob.2) id RAA13338; Tue, 16 Jul 1996 17:56:32 -0400 Received: by centime.cascade (5.x/SMI-SVR4) id AA12557; Tue, 16 Jul 1996 17:56:29 -0400 Date: Tue, 16 Jul 1996 17:56:29 -0400 From: conta@alpo.casc.com (Alex Conta) Message-Id: <9607162156.AA12557@centime.cascade> To: conta@alpo.casc.com, se@ZPR.Uni-Koeln.DE Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org X-Sun-Charset: US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Please enter "-v" at the "Boot: " prompt > and send me all numbers from the lines > starting with pcibus_setup or pcibus_check. > > If it reports success in the pcibus_check > line, then I need any information about > devices found on the PCI bus. Stefan, and Justin, Thanks much for the quick answers. Sorry for not giving this info earlier. With 'boot': On the DEC PC there is a successful, and laborious PCI probe - there are several lines displayed with info about the SCSI adapter, the SCSI CD-ROM, and Hard Disk Drive found, as well as the other PCI cards. On Compaq the PCI probe is apparently very short, and with no comments or lines displayed on the screen. With 'boot -v': on Compaq after the lines: npx0 on motherboard npx0: INT 16 interface the following 5 lines are displayed (only with 'boot -v'): pcibus_setup(1): mode1res=0x80000000c (0x80000000), mode2res = 0x0c (0x0e) rootfs is 1000 kbyte compiled in MFS BIOS geometries: 0:01953f20 0..405=406 cylinders, 0..63=64 heads, 1..32=32 sectors 0 accounted for followed by: /stand/sysinstall running as init > > Compaq caused lots of problems because of > their knowingly ignoring the PCI specs. > I once got a reply that it wouldn't matter, > since the BIOS and their drivers worked > around the problems introduced this way. > > But what they didn't care about was, that > the required workaround might break support > for other systems. They don't bother, since > they know their drivers are only used with > their machines. But we hardly want to have > a special FreeBSD version just for Compaq > machines ... :) The PCI-SCSI adapter works with Windows 3.1 and the Adaptec Windows 3.1 drivers - "EASY-SCSI 4.0" - that I installed from an Adaptec distribution diskette, which are perhaps tunned to the Compaq PCI behavior. Some additional info: on the DEC PC, the PCI-SCSI adapter has the following: IRQ = 9 Port addr = 7000-70ff (length 0xff) Mem Addr = c8000-c8fff (length 0xfff) = f1ef0000 - f1ef0fff (length 0xfff) on Compaq, it has the following: IRQ = 11 Port addr = 1000-10ff (length 0xff) Mem Addr = c8000-cffff (length 0x7fff) - note length difference = 41000000 - 41000fff (length 0xfff) On Compaq the PCI Master is bu default Enabled (BIOS parameter). Changing it didn't have any effect on the FreeBSD behavior. On Compaq an additional PCI device is a Cirrus VGA compatible controller that has: mem addr: 40000000-40ffffff dependencies: 3b0-3bb, 3c0-3df, a0000-bffff, c0000-c7fff I hope this helps to diagnose the problem. > > > 2. > > > > Any plans to add support for the AMD SCSI adapter that is embedded with > > Compaq DexPro 6200 XL? > > There was a message from Tekram recently, who ... > The NCR 53c810 as well as the Adaptec 2940 series > offers a small CPU as part of the host adapter.) > It seems that the AMD based SCSI adapter which comes integrated with the DEXPRO 6200 XL, a high end Compaq desktop, helps Compaq to lower the costs. > Reagrds, STefan > Thanks, Alex From owner-freebsd-hardware Tue Jul 16 15:11:28 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29705 for hardware-outgoing; Tue, 16 Jul 1996 15:11:28 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA29669; Tue, 16 Jul 1996 15:11:16 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id PAA21814 ; Tue, 16 Jul 1996 15:11:15 -0700 Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id SAA03009; Tue, 16 Jul 1996 18:09:47 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: conta@alpo.casc.com (Alex Conta) cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org From: "Gary Palmer" Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 In-reply-to: Your message of "Tue, 16 Jul 1996 14:20:34 EDT." <9607161820.AA12434@centime.cascade> Date: Tue, 16 Jul 1996 18:09:47 -0400 Message-ID: <3006.837554987@orion.webspan.net> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alex Conta wrote in message ID <9607161820.AA12434@centime.cascade>: > I have an Adaptec 2940 PCI-SCSI-2 adapter that works just fine under FreeBSD > 2.1 on a DEC Starion 960 PC (SCSI-2 hard disk drive + cd-rom). > The same adapter works fine on a Compaq ProLinea 5100 (SCSI hard disk and > cd-rom) under Windows 3.1, but it does not work when I try to install FreeBSD > from a CD-ROM distribution. > The installation fails because the adapter is not recognized. Booting with > "-c" and setting manually the IRQ, Port Address, and other parameters didn't > help. > Known problem? Known solution? My money is on the Compaq having one of the ``interesting'' Compaq PCI implimentations which causes our code nightmares. You may want to try 2.1.5 to see if it has the Compaq fixes in it, if not then -current does. (BTW: the ahc driver doesn't appear to the `-c' boot config. as it's a PCI device and all necessary information is auto-detected, but *ONLY* if the PCI bus is detected) > 2. > Any plans to add support for the AMD SCSI adapter that is embedded with > Compaq DexPro 6200 XL? Not that I am aware of. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hardware Tue Jul 16 15:22:33 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA01268 for hardware-outgoing; Tue, 16 Jul 1996 15:22:33 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA01030; Tue, 16 Jul 1996 15:20:10 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id SAA03485; Tue, 16 Jul 1996 18:17:45 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Stefan Esser cc: conta@alpo.casc.com (Alex Conta), freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org From: "Gary Palmer" Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 In-reply-to: Your message of "Tue, 16 Jul 1996 21:20:08 +0200." <199607161920.VAA00899@x14.mi.uni-koeln.de> Date: Tue, 16 Jul 1996 18:17:45 -0400 Message-ID: <3481.837555465@orion.webspan.net> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Esser wrote in message ID <199607161920.VAA00899@x14.mi.uni-koeln.de>: > Compaq caused lots of problems because of > their knowingly ignoring the PCI specs. > I once got a reply that it wouldn't matter, > since the BIOS and their drivers worked > around the problems introduced this way. > But what they didn't care about was, that > the required workaround might break support > for other systems. They don't bother, since > they know their drivers are only used with > their machines. But we hardly want to have > a special FreeBSD version just for Compaq > machines ... :) Which is (IMNSHO) is *EXTREMELY* shortshighted of ANY company ... how many ``high end'' OS's rely on the crappy PC bios for I/O? I'm not meaning the M$ stuff, I'm meaning the true UN*X stuff (e.g. Solaris, SCO, FreeBSD. Sorry, maybe I shouldn't have said UN*X :-) ). It basically means that Compaq hardware is limited to running M$ stuff, which is cutting out other people from the game ... has Compaq been bought out by M$, perhaps? :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hardware Tue Jul 16 16:26:35 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA11142 for hardware-outgoing; Tue, 16 Jul 1996 16:26:35 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA11125; Tue, 16 Jul 1996 16:26:31 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id XAA28224; Tue, 16 Jul 1996 23:20:12 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma028222; Tue Jul 16 23:20:12 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id QAA21999; Tue, 16 Jul 1996 16:20:11 -0700 Date: Tue, 16 Jul 1996 16:20:11 -0700 From: "M.R.Murphy" Message-Id: <199607162320.QAA21999@meerkat.mole.org> To: gpalmer@FreeBSD.org, se@ZPR.Uni-Koeln.DE Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 Cc: conta@alpo.casc.com, freebsd-hardware@FreeBSD.org, freebsd-scsi@FreeBSD.org Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Which is (IMNSHO) is *EXTREMELY* shortshighted of ANY company ... how > many ``high end'' OS's rely on the crappy PC bios for I/O? I'm not > meaning the M$ stuff, I'm meaning the true UN*X stuff (e.g. Solaris, > SCO, FreeBSD. Sorry, maybe I shouldn't have said UN*X :-) ). It > basically means that Compaq hardware is limited to running M$ stuff, > which is cutting out other people from the game ... has Compaq been > bought out by M$, perhaps? :) > (money spent on non-M$ stuff) + (money spent on M$ stuff) --------------------------------------------------------- = 1 (money spent on M$ stuff) More's the pity, but the money talks. That makes it not necessarily shortsighted from a business standpoint :-( The good of it is that there's a driving force for less expensive, more powerful hardware to run M$ (and it's required), and other OS's get to ride the coattails. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-hardware Tue Jul 16 18:20:02 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29073 for hardware-outgoing; Tue, 16 Jul 1996 18:20:02 -0700 (PDT) Received: from webserver.casc.com (webserver.casc.com [152.148.41.200]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA29020; Tue, 16 Jul 1996 18:19:59 -0700 (PDT) Received: from casc.com (alpo [152.148.10.6]) by webserver.casc.com (8.6.12/8.6.12) with ESMTP id VAA17988; Tue, 16 Jul 1996 21:19:01 -0400 Received: from centime.cascade by casc.com (SMI-8.6/SMI-SVR4-bob.2) id VAA15504; Tue, 16 Jul 1996 21:20:03 -0400 Received: by centime.cascade (5.x/SMI-SVR4) id AA12607; Tue, 16 Jul 1996 21:20:00 -0400 Date: Tue, 16 Jul 1996 21:20:00 -0400 From: conta@alpo.casc.com (Alex Conta) Message-Id: <9607170120.AA12607@centime.cascade> To: gpalmer@freebsd.org, se@zpr.uni-koeln.de Subject: More on Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org, conta@alpo.casc.com X-Sun-Charset: US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gary wrote: .. > My money is on the Compaq having one of the ``interesting'' Compaq PCI > implimentations which causes our code nightmares. You may want to try > 2.1.5 to see if it has the Compaq fixes in it, if not then -current > does. > > (BTW: the ahc driver doesn't appear to the `-c' boot config. as it's a > PCI device and all necessary information is auto-detected, but *ONLY* > if the PCI bus is detected) > config in "line mode" allows entering commands for it. By the way, the manual - Installing and Running FreeBSD - is in contradiction: at page 7 ahc0 is 294x, and ahc1 is 274x, while at page 165 ahc0 is 274x, and ahc1 is 2940/3940. And then again at page 181, 27dx is ahb0, while 174x is ahc0, and ahc1. At any rate, I learn more about this, as I go along. Some more information related to the PCI problem: I installed the Adaptec PIC-SCSI card into a Compaq DexPro 6200 XL, as a second SCSI adapter, I disabled the embeded SCSI (AMD), and the FreeBSD installation went well so far - I didn't boot yet. What I think is relevant is that 'boot -v' listed this time the following: pcibus_setup(1): mode1res=0x80000000c (0x80000000), mode2res = 0xff (0x0e) as opposed to when it failed: pcibus_setup(1): mode1res=0x80000000c (0x80000000), mode2res = 0x0c (0x0e) It seems that the value 0 of bit 1 causes the failure. 2. > > > Any plans to add support for the AMD SCSI adapter that is embedded with > > Compaq DexPro 6200 XL? > > Not that I am aware of. > Apparently the Compaq's PCI Ethernet (AMD) is recognized but no driver exists. So it looks like a further mismatch between Compaq and FreeBSD. Alex From owner-freebsd-hardware Wed Jul 17 12:29:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11777 for hardware-outgoing; Wed, 17 Jul 1996 12:29:05 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA11754; Wed, 17 Jul 1996 12:28:59 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id VAA08165; Wed, 17 Jul 1996 21:30:07 +0200 Received: by uni4nn.iaf.nl with UUCP id AA09544 (5.67b/IDA-1.5); Wed, 17 Jul 1996 21:29:41 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA05601 (5.67b/IDA-1.5); Wed, 17 Jul 1996 20:57:58 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id TAA00615; Wed, 17 Jul 1996 19:08:17 +0200 From: Wilko Bulte Message-Id: <199607171708.TAA00615@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: Adaptec 2940 PCI-SCSI on Compaq ProLinea 5100 To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Wed, 17 Jul 1996 19:08:17 +0200 (MET DST) Cc: se@zpr.uni-koeln.de, conta@alpo.casc.com, freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG In-Reply-To: <3481.837555465@orion.webspan.net> from "Gary Palmer" at Jul 16, 96 06:17:45 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Gary Palmer wrote... > > But what they didn't care about was, that > > the required workaround might break support > > for other systems. They don't bother, since > > they know their drivers are only used with > > their machines. But we hardly want to have > > a special FreeBSD version just for Compaq > > machines ... :) > > Which is (IMNSHO) is *EXTREMELY* shortshighted of ANY company ... how > many ``high end'' OS's rely on the crappy PC bios for I/O? I'm not > meaning the M$ stuff, I'm meaning the true UN*X stuff (e.g. Solaris, People get filty rich by just doing mainstream (read: M$ stuff). Why bother with niche markets? It's sad, true... > SCO, FreeBSD. Sorry, maybe I shouldn't have said UN*X :-) ). It > basically means that Compaq hardware is limited to running M$ stuff, > which is cutting out other people from the game ... has Compaq been > bought out by M$, perhaps? :) > > Gary Wilko 'The Devils Attorney' _ ____________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------- From owner-freebsd-hardware Wed Jul 17 15:54:33 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28669 for hardware-outgoing; Wed, 17 Jul 1996 15:54:33 -0700 (PDT) Received: from Kryten.nina.com (dyn051-gnv.51.fdt.net [205.229.51.52]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA28662 for ; Wed, 17 Jul 1996 15:54:30 -0700 (PDT) Received: from localhost (frankd@localhost) by Kryten.nina.com (8.7.5/8.6.12) with SMTP id SAA20607 for ; Wed, 17 Jul 1996 18:51:39 -0400 (EDT) X-Authentication-Warning: Kryten.nina.com: frankd owned process doing -bs Date: Wed, 17 Jul 1996 18:51:39 -0400 (EDT) From: Frank Seltzer X-Sender: frankd@Kryten.nina.com To: freebsd-hardware@freebsd.org Subject: Comments wanted on new system Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am assembling a new system to run FreeBSD. The proposed hardware currently consists of : Asus P6RP4 Pentium Pro 200 motherboard 64 megs RAM Asus SC200 SCSI controller I had originally wanted to get a 4.3 GB hard drive for this system but the price (900-1000) is prohibitive. I am therefore considering 2-3 1.0-1.6 GB drives at 250-300 each (all prices are USD). Does anyone have any suggestions or recommendations to make about this idea? Any favorite drives to recommend? I am also looking for suggestions for a tape backup at a reasonable price. All comments and suggestions are welcome as I am not very familiar with SCSI peripherals. Thanks, Frank -- Only in America can a homeless veteran sleep in a cardboard box while a draft dodger sleeps in the White House. From owner-freebsd-hardware Wed Jul 17 16:09:57 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA29513 for hardware-outgoing; Wed, 17 Jul 1996 16:09:57 -0700 (PDT) Received: from ng.netgate.net (root@ng.netgate.net [204.145.147.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA29508 for ; Wed, 17 Jul 1996 16:09:55 -0700 (PDT) Received: from s29 (s29.netgate.net [205.214.175.29]) by ng.netgate.net (8.7.4/8.6.9) with SMTP id QAA22824 for ; Wed, 17 Jul 1996 16:16:27 -0700 (PDT) Message-ID: <31E439C6.1B6F@netgate.net> Date: Wed, 10 Jul 1996 16:16:22 -0700 From: Matt Clark X-Mailer: Mozilla 2.02 (Win16; I) MIME-Version: 1.0 To: hardware@freefall.freebsd.org Subject: Supra 288i PnP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a Supra 288 internal plug n pray modem. And ideas on getting freebsd to reconize it? I have set sio2 to the correct settings (IRQ 5, Port 0x3e8), but it still will not accept it. --matt Clark From owner-freebsd-hardware Wed Jul 17 17:26:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04309 for hardware-outgoing; Wed, 17 Jul 1996 17:26:44 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA04302 for ; Wed, 17 Jul 1996 17:26:38 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id RAA07661; Wed, 17 Jul 1996 17:26:30 -0700 From: "Rodney W. Grimes" Message-Id: <199607180026.RAA07661@GndRsh.aac.dev.com> Subject: Re: Comments wanted on new system To: frankd@yoda.fdt.net (Frank Seltzer) Date: Wed, 17 Jul 1996 17:26:30 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.org In-Reply-To: from Frank Seltzer at "Jul 17, 96 06:51:39 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I am assembling a new system to run FreeBSD. The proposed hardware > currently consists of : > > Asus P6RP4 Pentium Pro 200 motherboard I would highly recommend _not_ getting this board, it uses the Orion chipset, which is older and known to have certain bugs. ASUS is now in production with the PCI/I-P6NP5 board based on the newer Natoma chipset, the boards are still on allocation, but I am not having much problem getting them. > 64 megs RAM > Asus SC200 SCSI controller > > I had originally wanted to get a 4.3 GB hard drive for this system but the > price (900-1000) is prohibitive. I am therefore considering 2-3 1.0-1.6 GB > drives at 250-300 each (all prices are USD). Does anyone have any > suggestions or recommendations to make about this idea? Any favorite > drives to recommend? You might want to consider the Micropolis MC4421, new on the market, but at an attractive price/performance point for 2G drives (street price should be less than $550.) Many of the high performance 1G class scsi drives are gone from the market, you might find some one with Fujitsu M1606SAU's... going price is in the $250-$275 range. > I am also looking for suggestions for a tape backup at a reasonable price. > > All comments and suggestions are welcome as I am not very familiar with > SCSI peripherals. > > Thanks, > Frank -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Jul 17 18:00:12 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA05389 for hardware-outgoing; Wed, 17 Jul 1996 18:00:12 -0700 (PDT) Received: from Kryten.nina.com (dyn051-gnv.51.fdt.net [205.229.51.52]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA05378 for ; Wed, 17 Jul 1996 18:00:08 -0700 (PDT) Received: from localhost (frankd@localhost) by Kryten.nina.com (8.7.5/8.6.12) with SMTP id UAA21832; Wed, 17 Jul 1996 20:57:01 -0400 (EDT) X-Authentication-Warning: Kryten.nina.com: frankd owned process doing -bs Date: Wed, 17 Jul 1996 20:57:01 -0400 (EDT) From: Frank Seltzer X-Sender: frankd@Kryten.nina.com To: "Rodney W. Grimes" cc: freebsd-hardware@FreeBSD.org Subject: Re: Comments wanted on new system In-Reply-To: <199607180026.RAA07661@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Jul 1996, Rodney W. Grimes wrote: > I would highly recommend _not_ getting this board, it uses the Orion > chipset, which is older and known to have certain bugs. ASUS is now > in production with the PCI/I-P6NP5 board based on the newer Natoma > chipset, the boards are still on allocation, but I am not having much > problem getting them. > What kind of problems exist in the Orion chipset? > You might want to consider the Micropolis MC4421, new on the market, but > at an attractive price/performance point for 2G drives (street price should > be less than $550.) I have heard a lot of horror stories about Micropolis drives. Is this a better unit than previous drives? > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD > Frank -- Only in America can a homeless veteran sleep in a cardboard box while a draft dodger sleeps in the White House. From owner-freebsd-hardware Wed Jul 17 18:32:12 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06890 for hardware-outgoing; Wed, 17 Jul 1996 18:32:12 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA06840; Wed, 17 Jul 1996 18:31:58 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.5/8.7.3) id LAA00152; Thu, 18 Jul 1996 11:31:53 +1000 (EST) Date: Thu, 18 Jul 1996 11:31:52 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hardware@freebsd.org, freebsd-isp@freebsd.org cc: peter.hawkins@cc.monash.edu.au Subject: Cyclades cards PCI/ISA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, Could someone please clarify whether the cy driver in 2.1.5 (last updated 1996/01/29) handles the new PCI based cyclades boards. There is no mention of PCI anywhere in cy.c. Thanks, Danny From owner-freebsd-hardware Wed Jul 17 18:33:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA06946 for hardware-outgoing; Wed, 17 Jul 1996 18:33:10 -0700 (PDT) Received: from zombie.ncsc.mil (zombie.ncsc.mil [144.51.15.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA06941 for ; Wed, 17 Jul 1996 18:33:07 -0700 (PDT) Received: (from sjr@localhost) by zombie.ncsc.mil (8.6.11/8.6.11) id VAA20531 for freebsd-hardware@freebsd.org; Wed, 17 Jul 1996 21:33:01 -0400 Date: Wed, 17 Jul 1996 21:33:01 -0400 From: "Stephen J. Roznowski" Message-Id: <199607180133.VAA20531@zombie.ncsc.mil> To: freebsd-hardware@freebsd.org Subject: Support for on-board SoundBlaster? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running FreeBSD 2.2-CURRENT [supped within the last few days]. My motherboard (Micron) has an onboard SoundBlaster 16. [Chip is Vibra 16C; Creative Tech 95; CT2505-TDQ; 9605-ES0461B3] When I boot, I see the following messages: sb0 not found at 0x220 sbxvi0 not found sbmidi0 not found at 0x330 This chip is recognized by Win95 with the following information: IRQ 5 DMA 1 DMA 5 0x220-0x22F 0x330-0x331 0x388-0x38B What do I need to do to get FreeBSD to recognize this? Thanks, Stephen Roznowski (sjr@zombie.ncsc.mil) From owner-freebsd-hardware Wed Jul 17 18:45:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08166 for hardware-outgoing; Wed, 17 Jul 1996 18:45:39 -0700 (PDT) Received: from ref.tfs.com ([206.245.251.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA08161 for ; Wed, 17 Jul 1996 18:45:36 -0700 (PDT) Received: (from julian@localhost) by ref.tfs.com (8.7.5/8.7.3) id SAA12771; Wed, 17 Jul 1996 18:44:23 -0700 (PDT) Message-Id: <199607180144.SAA12771@ref.tfs.com> Subject: Re: Supra 288i PnP To: narf@netgate.net (Matt Clark) Date: Wed, 17 Jul 1996 18:44:21 -0700 (PDT) From: "JULIAN Elischer" Cc: hardware@freefall.freebsd.org In-Reply-To: <31E439C6.1B6F@netgate.net> from "Matt Clark" at Jul 10, 96 04:16:22 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk in sio.c look for the test where it sets failure[1] through failure[4] there is a delay there.. I just increased it to 10000 so it would find some modems.. you might do the same.. (I checked in the change so it should be in -current now) best thing to do.... boot -c flags sio2 0x80 quit dmesg shold show you which tests failed... if it's 3 and 4, then do the above patch.. julian > > I have a Supra 288 internal plug n pray modem. And ideas on getting > freebsd to reconize it? I have set sio2 to the correct settings (IRQ 5, > Port 0x3e8), but it still will not accept it. > > --matt Clark > From owner-freebsd-hardware Wed Jul 17 19:57:27 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA11769 for hardware-outgoing; Wed, 17 Jul 1996 19:57:27 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA11754 for ; Wed, 17 Jul 1996 19:57:16 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id TAA07745; Wed, 17 Jul 1996 19:57:01 -0700 From: "Rodney W. Grimes" Message-Id: <199607180257.TAA07745@GndRsh.aac.dev.com> Subject: Re: Comments wanted on new system To: frankd@yoda.fdt.net (Frank Seltzer) Date: Wed, 17 Jul 1996 19:57:01 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.org In-Reply-To: from Frank Seltzer at "Jul 17, 96 08:57:01 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > On Wed, 17 Jul 1996, Rodney W. Grimes wrote: > > > I would highly recommend _not_ getting this board, it uses the Orion > > chipset, which is older and known to have certain bugs. ASUS is now > > in production with the PCI/I-P6NP5 board based on the newer Natoma > > chipset, the boards are still on allocation, but I am not having much > > problem getting them. > > > > What kind of problems exist in the Orion chipset? One more time.... Chip sets belowing stepping B0 have a PCI bus mastering bug that prevents data tranfer rates to reach much beyond 4.4MB/s on the PCI bus. There is a fundemental flaw in the design of the chipset/CPU interface logic as well, that will never be fixed which has a significant impact on CPU/Memory bandwidth. > > > You might want to consider the Micropolis MC4421, new on the market, but > > at an attractive price/performance point for 2G drives (street price should > > be less than $550.) > > I have heard a lot of horror stories about Micropolis drives. Is this a > better unit than previous drives? I have heard horror stories about _ALL_ drive manufactures, most of them blown far out of proportion. Yes, even some about Micropolis. Far more about Conner and Seagate though :-) :-). As far as I can tell the MC4421's seem to be just fine, but then horror stories don't usually show up until the drive has been shipping for 3 or 4 months, and this drive just became avaliable in volume. Given that it is basically a revision of the MC4221 (which has been out for over a year, with little known problems) I would say it has as good a chance as any other 2G drive on the market. Ohh.. and avoid HP SureStore drives... they've decided they can't be in the disk drive market any longer, they where loosing money at it and I suspect a large portion of that ``loss'' came from the number of dead drives they had to replace, now there's a horror story. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Thu Jul 18 00:15:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01876 for hardware-outgoing; Thu, 18 Jul 1996 00:15:31 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA01866 for ; Thu, 18 Jul 1996 00:15:28 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA19697 for ; Thu, 18 Jul 1996 09:14:50 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma019418; Thu Jul 18 09:13:09 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA14430 for ; Thu, 18 Jul 1996 09:15:29 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id JAA10681 for ; Thu, 18 Jul 1996 09:11:59 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 18 Jul 96 09:12:14 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 18 Jul 96 09:11:44 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hardware@freebsd.org Date: Thu, 18 Jul 1996 09:11:42 GMT+0100 Subject: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail v3.22 Message-ID: <3E5A6A874E1@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hoi Hardware, I own a SOYO SY-30F2 mainboard (4xpci, 2xvesa, all 486's) with a NCR 53C810 on the PCI bus. Until a week ago that was the only device on the PCI bus. A week ago I added a 'Diamond Stealth 64 video 2001' to my system. Pretty cool video card, but not for me. X crashes my system (as in immediate reboot). Needless to say Descent^H^H^H^H^H^H^HMS-DOS runs fine :( I have no MS Windows to try it with. In the shop they told me that my mainboard has trouble handling two PCI busmastering devices and that I need a new mainboard if I want to run a FreeBSD on it. Any truth in that? boot -v reveals that both the SCSI and the VGA card use int# a. and occupy the same memory address. This is regardless of the settings I do in the bios (Award modular bios). Any suggestions? Groetjes, Kees Jan PS. I tried to attach my dmesg output to this mail, but pegasus mail is not a useful mailer. Sorry if it causes problems. I'll mail dmesg to anyone who asks personally. From owner-freebsd-hardware Thu Jul 18 00:15:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01885 for hardware-outgoing; Thu, 18 Jul 1996 00:15:32 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA01867 for ; Thu, 18 Jul 1996 00:15:28 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA19710 for ; Thu, 18 Jul 1996 09:14:54 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma019419; Thu Jul 18 09:13:09 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA14429 for ; Thu, 18 Jul 1996 09:15:29 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id JAA10678 for ; Thu, 18 Jul 1996 09:11:59 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 18 Jul 96 09:12:13 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 18 Jul 96 09:11:44 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hardware@freebsd.org Date: Thu, 18 Jul 1996 09:11:40 GMT+0100 Subject: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail v3.22 Message-ID: <3E5A6A80622@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FreeBSD 2.1.0-RELEASE #2: Tue Jul 16 21:43:57 MET DST 1996 root@LikeEver:/usr/src/sys/compile/LIKEEVER CPU: i486DX (486-class CPU) real memory = 8388608 (8192K bytes) avail memory = 6885376 (6724K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 drq 5 on isa ed0: address 08:00:57:81:00:00, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, dma, iordis wcd0: 689Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: medium type unknown, unlocked npx0 on motherboard npx0: INT 16 interface pcibus_setup(1): mode1res=0x80000000 (0x80000000), mode2res=0xff (0x0e) pcibus_setup(2): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 is there (id=c8221045) Probing for devices on the PCI bus: configuration mode 1 allows 32 devices. pci0:16: OPTI, device=0xc822, class=bridge (host) [no driver assigned] vga0 rev 67 int a irq ?? on pci0:17 register_mem: bus=0 base=fc000000 limit=ffffffff mapreg[10] type=0 addr=fc000000 size=4000000. ncr0 rev 1 int a irq 15 on pci0:18 register_io: bus=0 base=d000 limit=d0ff mapreg[10] type=1 addr=0000d000 size=0100. register_mem: bus=0 base=fc000000 limit=fc0000ff mapreg[14] type=0 addr=fc000000 size=0100. reg20: virtual=0xf1ac0000 physical=0xfc000000 size=0x100 ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 (V2 pl23 95/09/07) (ncr0:0:0): "MAXTOR LXT-213S 4.20" type 0 fixed SCSI 1 sd0(ncr0:0:0): Direct-Access 202MB (415436 512 byte sectors) sd0(ncr0:0:0): with 1310 cyls, 7 heads, and an average 45 sectors/track (ncr0:1:0): "IMPRIMIS 94601-15 4638" type 0 fixed SCSI 1 sd1(ncr0:1:0): Direct-Access 1001MB (2050995 512 byte sectors) sd1(ncr0:1:0): with 1931 cyls, 15 heads, and an average 70 sectors/track pci0: uses 67109120 bytes of memory from fc000000 upto ffffffff. pci0: uses 256 bytes of I/O space from d000 upto d0ff. BIOS Geometries: 0:03fe063a 0..1022=1023 cylinders, 0..6=7 heads, 1..58=58 sectors 1:03f9203d 0..1017=1018 cylinders, 0..32=33 heads, 1..61=61 sectors 0 accounted for sd0s1: type 0x6, start 58, end = 204623, size 204566 : OK sd0s2: type 0xa5, start 204624, end = 415337, size 210714 : OK sd1s1: type 0xa5, start 61, end = 1024616, size 1024556 : OK sd1s2: type 0xa5, start 1024617, end = 1125266, size 100650 : OK sd1s3: type 0xa5, start 1125267, end = 2049233, size 923967 : OK ed0: device timeout From owner-freebsd-hardware Thu Jul 18 02:24:17 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA07654 for hardware-outgoing; Thu, 18 Jul 1996 02:24:17 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA07645 for ; Thu, 18 Jul 1996 02:24:06 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id CAA07953; Thu, 18 Jul 1996 02:23:55 -0700 From: "Rodney W. Grimes" Message-Id: <199607180923.CAA07953@GndRsh.aac.dev.com> Subject: Re: SOYO SY-30F2 blues To: Kees.Koster@nym.sc.philips.com Date: Thu, 18 Jul 1996 02:23:55 -0700 (PDT) Cc: hardware@freebsd.org In-Reply-To: <3E5A6A874E1@NLNMG01.nym.sc.philips.com> from Kees Jan Koster at "Jul 18, 96 09:11:42 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hoi Hardware, > > I own a SOYO SY-30F2 mainboard (4xpci, 2xvesa, all 486's) with a > NCR 53C810 on the PCI bus. Until a week ago that was the only device > on the PCI bus. > > A week ago I added a 'Diamond Stealth 64 video 2001' to my system. > Pretty cool video card, but not for me. X crashes my system (as in > immediate reboot). Needless to say Descent^H^H^H^H^H^H^HMS-DOS runs > fine :( I have no MS Windows to try it with. > > In the shop they told me that my mainboard has trouble handling two > PCI busmastering devices and that I need a new mainboard if I want to > run a FreeBSD on it. Any truth in that? But you do _not_ have two PCI busmastering devices. A video card is not a bus mastering device, the only bus master you have is the NCR 53C810. If anything I would syspect the Diamond Stealth 64 video 2001, I have heard nothing but nightmares from my freinds down the street who build regular PC for DOS/Windows/WIN95 when they try to use these things on just about anyones motherboard. > > boot -v reveals that both the SCSI and the VGA card use int# a. and > occupy the same memory address. This is regardless of the settings I > do in the bios (Award modular bios). It sounds like maybe the bios on the VGA card or the motherboard bios are not doing the right thing with respect to memory space assignment. > > Any suggestions? Yea, try someone elses S3-968 based card, Miro, Number Nine, anyone but diamond and you'll probably be running just fine. > Groetjes, > Kees Jan > > PS. I tried to attach my dmesg output to this mail, but pegasus mail > is not a useful mailer. Sorry if it causes problems. I'll mail dmesg > to anyone who asks personally. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Thu Jul 18 05:54:21 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA16220 for hardware-outgoing; Thu, 18 Jul 1996 05:54:21 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA16214 for ; Thu, 18 Jul 1996 05:54:19 -0700 (PDT) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id FAA02940 for ; Thu, 18 Jul 1996 05:05:46 -0700 (PDT) Received: from mekong.biomath.jussieu.fr (mekong.biomath.jussieu.fr [134.157.72.87]) by shiva.jussieu.fr (8.7.5/jtpda-5.2) with SMTP id OAA14077 for ; Thu, 18 Jul 1996 14:03:45 +0200 (METDST) Received: from iaka.biomath.jussieu.fr (iaka) by mekong.biomath.jussieu.fr (5.67b/jn930126+af960507(mailhost)) at Thu, 18 Jul 1996 14:03:11 +0100 Received: by iaka.biomath.jussieu.fr (5.67b/jf930126) at Thu, 18 Jul 1996 14:03:09 +0100 Message-Id: <199607181303.AA02553@iaka.biomath.jussieu.fr> Subject: Re: SOYO SY-30F2 blues To: freebsd-hardware@freefall.freebsd.org Date: Thu, 18 Jul 1996 14:03:08 +0100 (GMT+0100) From: "Alain FAUCONNET" X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hoi Hardware, > > > > I own a SOYO SY-30F2 mainboard (4xpci, 2xvesa, all 486's) with a > > NCR 53C810 on the PCI bus. Until a week ago that was the only device > > on the PCI bus. > > > > A week ago I added a 'Diamond Stealth 64 video 2001' to my system. > > Pretty cool video card, but not for me. X crashes my system (as in > > immediate reboot). Needless to say Descent^H^H^H^H^H^H^HMS-DOS runs > > fine :( I have no MS Windows to try it with. > > [......] > > If anything I would syspect the Diamond Stealth 64 video 2001, I have > heard nothing but nightmares from my freinds down the street who build > regular PC for DOS/Windows/WIN95 when they try to use these things on > just about anyones motherboard. > > > > > boot -v reveals that both the SCSI and the VGA card use int# a. and > > occupy the same memory address. This is regardless of the settings I > > do in the bios (Award modular bios). > > It sounds like maybe the bios on the VGA card or the motherboard bios > are not doing the right thing with respect to memory space assignment. > I'm not sure about the 2xxx series, but the 3xxx Diamond Stealth 64 are nice and fast controllers for FBSD/XFree86... once you figured out how to configure them. Make sure you are using the latest XFree86 3.1.2 beta release (I think it's 3.1.2e). Also try playing with options in the /etc/XF86Config file. I have had to explicitely specify the VRAM base address in mine as follows (remember my card is a 3400): Section "Device" Identifier "Diamond Stealth 64 Video VRAM" VendorName "Diamond" BoardName "Stealth 64 Video VRAM" MemBase 0x8000000 #Option "slow_vram" Option "sw_cursor" Option "Diamond" # Use Option "nolinear" if the server doesn't start up correctly # (this avoids the linear framebuffer probe). If that fails try # option "nomemaccess". # # Refer to /usr/X11R6/lib/doc/README.S3, and the XF86_S3 man page. EndSection Note that the address will probably vary for your configuration. Actually I picked up mine from what the demo Xaccel commercial server printed at startup. You might want to try it, I think it's available on www.xinside.com. Option "slow_vram" (commented out above) is said to avoid some cases of image corruption and/or crashes too. Good luck, _Alain_ -- Alain FAUCONNET Ingenieur systeme - System Manager AP-HP/SIM Public Health 91 bld de l'Hopital 75013 PARIS FRANCE Medical Computing Research Labs Mail: af@biomath.jussieu.fr Tel: (+33) 1-40-77-96-19 Fax: (+33) 1-45-86-80-68 I've RTFMed. It says: "Refer to your system administrator" But... I *am* the system administrator :-] From owner-freebsd-hardware Thu Jul 18 06:37:22 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA17901 for hardware-outgoing; Thu, 18 Jul 1996 06:37:22 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA17895 for ; Thu, 18 Jul 1996 06:37:19 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id PAA07939 for ; Thu, 18 Jul 1996 15:36:43 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma007791; Thu Jul 18 15:35:57 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id PAA24084 for ; Thu, 18 Jul 1996 15:38:18 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id PAA03238 for ; Thu, 18 Jul 1996 15:34:47 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 18 Jul 96 15:34:57 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 18 Jul 96 15:34:43 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: freebsd-hardware@freebsd.org Date: Thu, 18 Jul 1996 15:34:34 GMT+0100 Subject: Re: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <3EC09A1000B@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > boot -v reveals that both the SCSI and the VGA card use int# a. and > > > occupy the same memory address. This is regardless of the settings I > > > do in the bios (Award modular bios). > > > > It sounds like maybe the bios on the VGA card or the motherboard bios > > are not doing the right thing with respect to memory space assignment. > Yes, that was my thought too. Any idea how to cure this? I looked into /sys/pci/pci.c, but I could not figure out if it was possible to make FreeBSD do the memory allocation, or manually setting the pci parameters, such as int# and memory base. Could someone inform me about this, please? Is it possible to manually configure pci devices? There seems to be a pci_alloc() function, but the comment claims it's not complete nor tested. That's scary :-( Would it make a difference if I await the 2.1.5-release cdrom? > > I'm not sure about the 2xxx series, but the 3xxx Diamond Stealth 64 > are nice and fast controllers for FBSD/XFree86... once you figured out > how to configure them. > I've been using a 2xxx series at SPaSE while I worked there: no trouble at all. > > Make sure you are using the latest XFree86 3.1.2 beta release (I think > it's 3.1.2e). Also try playing with options in the /etc/XF86Config > file. I have had to explicitely specify the VRAM base address in mine > as follows (remember my card is a 3400): > I did ftp the 3.1.2e release for FreeBSD 2.1.0-release and played around. The problem did not change. XFree86 would detect my chipset and ram size correctly ... start ... display the familiar grey grid ... add the mouse cursor ... sometimes even an xterm or two ... and hang the system, leaving the SCSI activity led burning (!) This behaviour is the same with every server version I tried. > > Section "Device" [...] > MemBase 0x8000000 Curious... I tried this option, but the membase reported did not change... [...] > EndSection > > Note that the address will probably vary for your configuration. > Actually I picked up mine from what the demo Xaccel commercial server > printed at startup. You might want to try it, I think it's available > on www.xinside.com. > I'll try that later, thanks for the pointer. > > Option "slow_vram" (commented out above) is said to avoid some cases > of image corruption and/or crashes too. > From owner-freebsd-hardware Thu Jul 18 08:10:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA26089 for hardware-outgoing; Thu, 18 Jul 1996 08:10:05 -0700 (PDT) Received: from charon.siemens.be (charon.siemens.be [193.210.172.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA26057 for ; Thu, 18 Jul 1996 08:09:57 -0700 (PDT) Received: by charon.siemens.be (8.7.4/nsafe-1.3) id ; Thu, 18 Jul 1996 15:08:51 GMT Received: from atea.atea.be(193.210.197.11) by charon via smap (V1.3mjr) id sma009049; Thu Jul 18 17:08:43 1996 Received: from atdec1 by atea with SMTP (1.37.109.4/15.6-FW) id AA11568; Thu, 18 Jul 96 17:08:03 +0200 Received: from vnet by atdec1.atea.be (5.65/Ultrix3.0-C) id AA20167; Thu, 18 Jul 1996 17:08:52 +0200 Received: by vnet.atea.be; Thu, 18 Jul 96 17:08:58 +0200 Date: Thu, 18 Jul 96 18:08:38 WET Message-Id: X-Priority: 3 (Normal) To: From: (Rob Schofield) Subject: Multiple COM ports with same IRQ X-Incognito-Sn: 319 X-Incognito-Format: VERSION=2.01a ENCRYPTED=NO Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone tried converging two or more more COM ports on one IRQ, ala multi-port board method? Let me explain... Using sio for multiport configuration is reasonably straightforward according to the Handbook. However, if you've got more UARTs than the standard IBM pair (ie., COM1 & 2) the naughty "convention" is to have COM1 & 3 on IRQ4 and COM2 & 4 on IRQ3. Under DOS, this is a functional limitation and causes problems. If there's no free IRQ lines left in your box, then you can't just re-assign COM3 & 4 IRQs to something other than IRQ4 or 3. EISA boxes can use shared interrupts, level or edge triggered. ISA boxes can have hardware installed (accidentally?) with devices sharing the same IRQ, but the drivers cannot deal with it. So - here's the nub; suppose we have an ISA/EISA box with sio0 (DOS = COM1) attached to a mouse, IO add XXX, interrupt 4; sio1 (COM 2) at IO XXY and sio2 (COM 3) at IO XXZ, sharing interupt 3 (you could also plonk in COM4 on the same IRQ). Then, under FreeBSD, configure sio to recognise the 3 ISA devices at the three IO adds XXX, XXY and XXZ, with sio 2 & 3 considered to be a multiport board comprising 2 UARTS sharing one master IRQ: device sio0 at isa? port 0xXXX tty irq 4 vector siointr options "COM_MULTIPORT" device sio1 at isa? port 0xXXY tty flags 0x??? device sio2 at isa? port 0xXXZ tty flags 0x??? irq 3 vector siointr - plus the neccessary /dev device entries as well. XXX is at a lower IO add then XXY, and XXY is lower than XXZ. Considering the UARTS will generate edge interrupt rather than level, will this work? Will sio grab the "dual port" interrupt then interrogate the individual status regs of the UARTS? I'm not too concerned with operation under DOS here, so I'm only concerned with FBSD. Somebody tell me I'm an idiot and why this won't work (otherwise someone would have done it by now, wouldn't they?) Rob Schofield -- Happiness is a smoking processor....... Rob Schofield M.Sc. AMIEE schofiel@xs4all.nl http://www.xs4all.nl/~schofiel From owner-freebsd-hardware Thu Jul 18 09:03:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28791 for hardware-outgoing; Thu, 18 Jul 1996 09:03:31 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA28759 for ; Thu, 18 Jul 1996 09:03:15 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id LAA24671 for ; Thu, 18 Jul 1996 11:04:15 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id LAA24665 for ; Thu, 18 Jul 1996 11:04:15 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id LAA00289; Thu, 18 Jul 1996 11:08:33 -0500 (CDT) Date: Thu, 18 Jul 1996 11:08:33 -0500 (CDT) From: Alex Nash To: E00114@vnet.atea.be cc: freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 18 Jul 1996 E00114@vnet.atea.be wrote: > ISA boxes can > have hardware installed (accidentally?) with devices sharing the same IRQ, but > the drivers cannot deal with it. The sharing of interrupts between ISA devices is an electrical constraint. When two devices are attempting to use a common IRQ line, the devices compete with each other (electrically) to put the line in their desired state. Needless to say, the results are less than optimal. It is possible for the devices to share an interrupt if both devices can tri-state their IRQ lines. That way when you're operating device A, device B's IRQ line has no pull on the line, and vice versa. Naturally this precludes you from using both devices simultaneously (and even if the hardware does support tri-stating the IRQ line, the software may not activate it). [This only deals with ISA cards, the operation of on board serial ports are implementation specific.] Alex From owner-freebsd-hardware Thu Jul 18 10:48:14 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05135 for hardware-outgoing; Thu, 18 Jul 1996 10:48:14 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA05128 for ; Thu, 18 Jul 1996 10:48:08 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-49.slip.Uni-Koeln.DE) by Sisyphos with SMTP id AA14705 (5.67b/IDA-1.5 for ); Thu, 18 Jul 1996 19:47:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.7.5/8.6.9) id TAA00328; Thu, 18 Jul 1996 19:47:31 +0200 (MET DST) Date: Thu, 18 Jul 1996 19:47:31 +0200 (MET DST) Message-Id: <199607181747.TAA00328@x14.mi.uni-koeln.de> From: Stefan Esser To: Kees.Koster@nym.sc.philips.com Cc: freebsd-hardware@freebsd.org Subject: Re: SOYO SY-30F2 blues In-Reply-To: <3EC09A1000B@NLNMG01.nym.sc.philips.com> References: <3EC09A1000B@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Kees Jan Koster writes: > > > > boot -v reveals that both the SCSI and the VGA card use int# a. and > > > > occupy the same memory address. This is regardless of the settings I > > > > do in the bios (Award modular bios). It is not a problem that both cards use Int A, since this may be a different interrupt line for each PCI slot, and there is not even an IRQ assigned in your case ... The overlapping memory mappings are a totally different issue, I agree ... > > > It sounds like maybe the bios on the VGA card or the motherboard bios > > > are not doing the right thing with respect to memory space assignment. > > > Yes, that was my thought too. Any idea how to cure this? I looked > into /sys/pci/pci.c, but I could not figure out if it was possible to > make FreeBSD do the memory allocation, or manually setting the pci > parameters, such as int# and memory base. Could someone inform me > about this, please? Is it possible to manually configure pci devices? > There seems to be a pci_alloc() function, but the comment claims it's > not complete nor tested. That's scary :-( Would it make a difference > if I await the 2.1.5-release cdrom? No, it won't, for sure ! Short answer: Try to get a PCI BIOS update for your motherboard. The current version is buggy if it assigns the same mappings to different devices! The code in pci_alloc() will never be implemented, since it was meant to provide a workaround for systems with buggy PCI BIOS implementations, but all currently sold systems do this better than a PCI driver possibly could :) The problem is, that the BIOS has knowledge about certain PCI cards, which can't easily be duplicated in the FreeBSD PCI driver, and does know the PCI Int to ISA IRQ routing hardware, which has to be setup to match the IRQs used. While PCI supports interrupt sharing, and the code in FreeBSD does as well, the IRQ mapping will never have to be changed. The originally planned (re)assignment of mappings has been dropped, because the most likely need for it arises in old systems that didn't know about PCI to PCI bridges (as found on the Adaptec 3940 or on 4 channel Ethernet cards, for example). But since the IRQ routing hardware has to be set accordingly, and that can't be done in a hardware independent way on all (including OLD systems), there is no way to use such a card. Sorry, but there is hardly any generic way to solve your problem in a device driver. I can send you a fix, which will modify the NCR address to any value you choose, but you will have to compile that address into your kernel, which precludes its use on other FreeBSD systems. (Ok. I can make it dependent on the specific characteristics of your system, but there will never be an official version that includes that patch.) Regards, STefan From owner-freebsd-hardware Thu Jul 18 11:18:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06903 for hardware-outgoing; Thu, 18 Jul 1996 11:18:52 -0700 (PDT) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA06889 for ; Thu, 18 Jul 1996 11:18:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id MAA11039; Thu, 18 Jul 1996 12:18:39 -0600 Message-Id: <199607181818.MAA11039@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: hardware@FreeBSD.org cc: Kees.Koster@nym.sc.philips.com Subject: Re: SOYO SY-30F2 blues In-reply-to: Your message of "Thu, 18 Jul 1996 15:34:34 BST." <3EC09A1000B@NLNMG01.nym.sc.philips.com> Mime-Version: 1.0 Content-Type: text/plain Date: Thu, 18 Jul 1996 12:18:38 -0600 Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, > > Make sure you are using the latest XFree86 3.1.2 beta release (I think > > it's 3.1.2e). Also try playing with options in the /etc/XF86Config > > file. I have had to explicitely specify the VRAM base address in mine > > as follows (remember my card is a 3400): > > > I did ftp the 3.1.2e release for FreeBSD 2.1.0-release and played > around. The problem did not change. XFree86 would detect my chipset > and ram size correctly ... start ... display the familiar grey grid > ... add the mouse cursor ... sometimes even an xterm or two ... > and hang the system, leaving the SCSI activity led burning (!) > This behaviour is the same with every server version I tried. I have a diamond 2201 which I bought for a doz box I had to build. It works well in doz95 (a few things purturb it, but it is doz!). I tried X 3.1.2e just for grins and also had trouble. For me the problem was that xpm icons turned to grey mush, and the mouse was a large white square. Can't remember for sure, but I believe there was a vertical strip in first 16 or so pixels at left of screen. I suspect that this will work fine once the XFree86 people catch up with it. The chipset is some flavor of Trio 64+. The motherboard I tested in was an Intel Zappa II. -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-hardware Thu Jul 18 11:24:15 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA07270 for hardware-outgoing; Thu, 18 Jul 1996 11:24:15 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA07265 for ; Thu, 18 Jul 1996 11:24:12 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id LAA08235; Thu, 18 Jul 1996 11:22:54 -0700 From: "Rodney W. Grimes" Message-Id: <199607181822.LAA08235@GndRsh.aac.dev.com> Subject: Re: SOYO SY-30F2 blues To: af@biomath.jussieu.fr (Alain FAUCONNET) Date: Thu, 18 Jul 1996 11:22:54 -0700 (PDT) Cc: freebsd-hardware@freefall.freebsd.org In-Reply-To: <199607181303.AA02553@iaka.biomath.jussieu.fr> from Alain FAUCONNET at "Jul 18, 96 02:03:08 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ... > I'm not sure about the 2xxx series, but the 3xxx Diamond Stealth 64 > are nice and fast controllers for FBSD/XFree86... once you figured out > how to configure them. And you make my point perfectly about why I avoid Diamond products, with S3, Elsa, Miro, Number Nine, and Cardex S3-based cards I run xf86config and I am up and running. Realize I am in the system building business and having to go play with software for 2 hours to make some video card work is not an option when your turing out systems in volume. > Make sure you are using the latest XFree86 3.1.2 beta release (I think > it's 3.1.2e). Also try playing with options in the /etc/XF86Config > file. I have had to explicitely specify the VRAM base address in mine > as follows (remember my card is a 3400): Hummm having to explicitly spec the VRAM address for a PCI card tells me that the PCI card is broken! No thank you :-( -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Thu Jul 18 20:04:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA18341 for hardware-outgoing; Thu, 18 Jul 1996 20:04:32 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA18332 for ; Thu, 18 Jul 1996 20:04:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA30281; Fri, 19 Jul 1996 12:47:51 +1000 Date: Fri, 19 Jul 1996 12:47:51 +1000 From: Bruce Evans Message-Id: <199607190247.MAA30281@godzilla.zeta.org.au> To: E00114@vnet.atea.be, alex@fa.tdktca.com Subject: Re: Multiple COM ports with same IRQ Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> ISA boxes can >> have hardware installed (accidentally?) with devices sharing the same IRQ, but >> the drivers cannot deal with it. >The sharing of interrupts between ISA devices is an electrical >constraint. When two devices are attempting to use a common IRQ line, That's why he only wanted to share them for EISA/ISA boxes :-). sio should be able to handle it if the hardware permits level triggered interrupts. It doesn't depend on the trigger level and doesn't have board-specific multiport optimizations (only board-specific initializations for AST boards), so it shouldn't be able to tell the difference between a a bunch of ports connected to the same level triggered IRQ and a nondescript non-AST multiport board. Bruce From owner-freebsd-hardware Thu Jul 18 20:09:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA18814 for hardware-outgoing; Thu, 18 Jul 1996 20:09:46 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA18776 for ; Thu, 18 Jul 1996 20:09:24 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA30468; Fri, 19 Jul 1996 12:54:02 +1000 Date: Fri, 19 Jul 1996 12:54:02 +1000 From: Bruce Evans Message-Id: <199607190254.MAA30468@godzilla.zeta.org.au> To: E00114@vnet.atea.be, freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Considering the UARTS will generate edge interrupt rather than level, will >this work? Will sio grab the "dual port" interrupt then interrogate the >individual status regs of the UARTS? I'm not too concerned with operation >under DOS here, so I'm only concerned with FBSD. 16550 UARTs just generate signals that should work with either level or edge sensitive schemes. If the interrupts are still edge sensitive from the 8259 PIC's point of view, then they can't be shared. Bruce From owner-freebsd-hardware Fri Jul 19 00:00:55 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA09707 for hardware-outgoing; Fri, 19 Jul 1996 00:00:55 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA09699 for ; Fri, 19 Jul 1996 00:00:53 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA01364 for ; Fri, 19 Jul 1996 09:00:14 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma001217; Fri Jul 19 08:59:08 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA29999 for ; Fri, 19 Jul 1996 09:01:25 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id IAA17010 for ; Fri, 19 Jul 1996 08:57:48 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 19 Jul 96 08:57:59 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 19 Jul 96 08:57:48 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hardware@freebsd.org Date: Fri, 19 Jul 1996 08:57:45 GMT+0100 Subject: Re: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <3FD6DBD5D74@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I did ftp the 3.1.2e release for FreeBSD 2.1.0-release and played [... personal nightmare omitted...] > > I have a diamond 2201 which I bought for a doz box I had to build. It > works well in doz95 (a few things purturb it, but it is doz!). > I tried X 3.1.2e just for grins and also had trouble. For me the problem > was that xpm icons turned to grey mush, and the mouse was a large > white square. Can't remember for sure, but I believe there was a vertical > strip in first 16 or so pixels at left of screen > Well, at least I know I'm not the only one. I bought this card because it's smaller cousin _worked_. But your problem is not the same. I have a normal mouse cursor and X is running flawless for a few seconds, before the machine locks up. No white squares or strips. Groetjes, Kees Jan From owner-freebsd-hardware Fri Jul 19 00:07:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10433 for hardware-outgoing; Fri, 19 Jul 1996 00:07:24 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA10426 for ; Fri, 19 Jul 1996 00:07:21 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA02320 for ; Fri, 19 Jul 1996 09:06:48 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma002244; Fri Jul 19 09:06:01 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA00784 for ; Fri, 19 Jul 1996 09:08:21 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id JAA25071 for ; Fri, 19 Jul 1996 09:04:44 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 19 Jul 96 09:04:55 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 19 Jul 96 09:04:53 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hardware@freebsd.org Date: Fri, 19 Jul 1996 09:04:47 GMT+0100 Subject: Re: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <3FD8BF9780E@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I had a memory problem with 2 PCI cards - in my case a Cirrus Logic 5434 > and an Adaptec 2940. As with your case, the cards were grabbing the same > memory area. I 'cured' it by swapping their positions on the motherboard. > It seems that they were deciding on their memory area by some kind of > base x slot number calculation. When they were in the positions I used > first, they overlaid each other, after I reversed them, the problem > disappeared. > > Although my experience is with different cards, and I'm no hardware > maven - try swapping slots - it couldn't hurt! > Oh, I didn't mention that? I tried swapping cards, moving the SCSI controller to slot 2 and the S3 to slot 1. In any combination where the SCSI card has a higher slot number than the S3 the machine will boot, up to the point where FreeBSD inserts it's own device drivers. The I will see a message similar to: ncr0: CACHE CONFIGURED INCORRECTLY I haven't tried MS-DOS in this situation, but then again it'd probably work just fine and that would freak me out %-) Groetjes, Kees Jan From owner-freebsd-hardware Fri Jul 19 00:45:36 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA12278 for hardware-outgoing; Fri, 19 Jul 1996 00:45:36 -0700 (PDT) Received: from charon.siemens.be (charon.siemens.be [193.210.172.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA12271 for ; Fri, 19 Jul 1996 00:45:29 -0700 (PDT) Received: by charon.siemens.be (8.7.4/nsafe-1.3) id ; Fri, 19 Jul 1996 07:44:43 GMT Received: from atea.atea.be(193.210.197.11) by charon via smap (V1.3mjr) id sma010528; Fri Jul 19 09:44:26 1996 Received: from atdec1 by atea with SMTP (1.37.109.4/15.6-FW) id AA14000; Fri, 19 Jul 96 09:43:31 +0200 Received: from vnet by atdec1.atea.be (5.65/Ultrix3.0-C) id AA06590; Fri, 19 Jul 1996 09:44:21 +0200 Received: by vnet.atea.be; Fri, 19 Jul 96 9:44:31 +0200 Date: Fri, 19 Jul 96 9:43:10 WET Message-Id: X-Priority: 3 (Normal) To: From: (Rob Schofield) Subject: Re: Multiple COM ports with same IRQ X-Incognito-Sn: 319 X-Incognito-Format: VERSION=2.01a ENCRYPTED=NO Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans Wrote: | That's why he only wanted to share them for EISA/ISA boxes | :-). Somebody's reading my mind ;^) | sio should be able to handle it if the hardware permits | level triggered | interrupts. It doesn't depend on the trigger level and | doesn't have | board-specific multiport optimizations (only | board-specific | initializations for AST boards), so it shouldn't be able | to tell the | difference between a a bunch of ports connected to the | same level | triggered IRQ and a nondescript non-AST multiport board. I have to confess, this reply is rather heartening (thanks to everyone who's answered, by the way!). I was not sure (since I haven't been rooting around at board level for years now) what scheme the ISA PC was using for interrupts - my guess (based on my previous experience, but without looking at my architecture book) is that it would be some sort of active low scheme, where any board can assert using an open collector sink device (read: big transistor connected to ground which pulls the 5V IRQ line down). The problem is, I seem to remember that the line is not held high by the PC (it floats), meaning naughty boards could hold the line perpetually low, giving no other edge triggering board a chance. Additionally, we have the question of the interrupt being Edge (it spikes down, which latches on the interrupt controller) or level (it goes down and stays down until the CPU has serviced it). I have an EISA box which allows you to say "for this device at this address, expect an interrupt on IRQ X, level triggered" or "edge triggered". This sets up the PIC (interrupt controller) to expect a certain type of interrupt alright, but if the card in the slot doesn't behave like that, then interrupts might not register with the PIC. The original question was really to fish for opinions - given conventional UARTS (16550s) on an ISA card in an EISA box, can I set these two up to appear as a multiport by setting up the interrupt controller to handle two UARTs at different register addresses but sharing the same IRQ line? (ie. "dupe" sio into thinking it's handling a multiport). (to be honest I need to look in my ISA architecture book this weekend) If this could work, then it gives cheap advantage to EISA boxes simply by tweaking the setup parameters and moving a jumper, then building a kernel to handle it. This could free up an interrupt line for other cards with limited choices. I have to confess though, I'm not sure it'll work at the electronic level - is there anyone out there with any ISA/EISA card design experience who could comment on this? Rob -- Happiness is a smoking processor....... Rob Schofield M.Sc. AMIEE schofiel@xs4all.nl http://www.xs4all.nl/~schofiel From owner-freebsd-hardware Fri Jul 19 01:49:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA15471 for hardware-outgoing; Fri, 19 Jul 1996 01:49:45 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA15466 for ; Fri, 19 Jul 1996 01:49:41 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id KAA14641 for ; Fri, 19 Jul 1996 10:49:05 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma014595; Fri Jul 19 10:48:52 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id KAA11060 for ; Fri, 19 Jul 1996 10:51:13 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id KAA17630 for ; Fri, 19 Jul 1996 10:47:36 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 19 Jul 96 10:47:49 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 19 Jul 96 10:47:27 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hardware@freebsd.org Date: Fri, 19 Jul 1996 10:47:24 GMT+0100 Subject: Re: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <3FF419D0D14@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Short answer: Try to get a PCI BIOS update for > your motherboard. The current version is buggy > if it assigns the same mappings to different > devices! > Do you happen to have an ftp pointer? I have very limited internet access, sorry. My motherboard is a SOYO SY-30F2 with an Award Modular bios v4.50G. > > The code in pci_alloc() will never be implemented, [... useful information omitted > > Sorry, but there is hardly any generic way to solve > your problem in a device driver. I can send you a > fix, which will modify the NCR address to any value > you choose, but you will have to compile that address > into your kernel, which precludes its use on other > FreeBSD systems. (Ok. I can make it dependent on the > specific characteristics of your system, but there > will never be an official version that includes that > patch.) > Yes please, that patch would be extremely welcome. I tried to hack the kernel to do that, but I found I don't know enough about the pci handling stuff to do so. From owner-freebsd-hardware Fri Jul 19 02:47:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17772 for hardware-outgoing; Fri, 19 Jul 1996 02:47:37 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA17765 for ; Fri, 19 Jul 1996 02:47:34 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id LAA22283 for ; Fri, 19 Jul 1996 11:46:56 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma022127; Fri Jul 19 11:45:45 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id LAA17252 for ; Fri, 19 Jul 1996 11:48:06 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id LAA18802 for ; Fri, 19 Jul 1996 11:44:29 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 19 Jul 96 11:44:42 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 19 Jul 96 11:44:19 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hardware@freebsd.org Date: Fri, 19 Jul 1996 11:44:12 GMT+0100 Subject: Re: SOYO SY-30F2 blues Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <400344E3CB5@NLNMG01.nym.sc.philips.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > boot -v reveals that both the SCSI and the VGA card use int# a. and > > occupy the same memory address. This is regardless of the settings I > > do in the bios (Award modular bios). > > The 810 card I have has a hardware jumper to choose between #a - #d. > My video card (S3) also insists on using #a, so the NCR card is now on > #b and working well. > No hardware jumper i'm afraid. The only jumper is one to select "internal bus" or "external bus". What does the S3 card want an interrupt for anyway, I explicitly disabled all irq assignments in the BIOS settings. Groetjes, Kees Jan Plug and Play ... ... play what, the piano? From owner-freebsd-hardware Fri Jul 19 04:35:17 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21264 for hardware-outgoing; Fri, 19 Jul 1996 04:35:17 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA21258 for ; Fri, 19 Jul 1996 04:35:16 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0uhFdD-000xAPC; Fri, 19 Jul 96 06:30 PDT Received: from cc:Mail by ccgate.infoworld.com id AA837775962; Thu, 18 Jul 96 20:01:57 PST Date: Thu, 18 Jul 96 20:01:57 PST From: "Brett Glass" Message-Id: <9606198377.AA837775962@ccgate.infoworld.com> To: (Rob Schofield), freebsd-hardware@freebsd.org Subject: Multiple COM ports with same IRQ Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Under ISA, interrupts CANNOT be shared. It is an electrical problem that cannot be fixed via software. From owner-freebsd-hardware Fri Jul 19 04:35:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21281 for hardware-outgoing; Fri, 19 Jul 1996 04:35:24 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA21275 for ; Fri, 19 Jul 1996 04:35:23 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0uhFdO-000xAUC; Fri, 19 Jul 96 06:30 PDT Received: from cc:Mail by ccgate.infoworld.com id AA837775954; Thu, 18 Jul 96 19:52:13 PST Date: Thu, 18 Jul 96 19:52:13 PST From: "Brett Glass" Message-Id: <9606198377.AA837775954@ccgate.infoworld.com> To: "JULIAN Elischer" , narf@netgate.net Cc: hardware@freefall.freebsd.org Subject: Re: Supra 288i PnP Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've played with this modem, and I fear that Diamond -- like some other hardware vendors who are particularly shortsighted -- has gone Windows-specific. I would not expect support from them for any other OS. From owner-freebsd-hardware Fri Jul 19 06:43:22 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26421 for hardware-outgoing; Fri, 19 Jul 1996 06:43:22 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA26416 for ; Fri, 19 Jul 1996 06:43:20 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id IAA10912 for ; Fri, 19 Jul 1996 08:44:11 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id IAA10905 for ; Fri, 19 Jul 1996 08:44:11 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id IAA09527; Fri, 19 Jul 1996 08:48:38 -0500 (CDT) Date: Fri, 19 Jul 1996 08:48:38 -0500 (CDT) From: Alex Nash To: Bruce Evans cc: E00114@vnet.atea.be, freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ In-Reply-To: <199607190247.MAA30281@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Bruce Evans wrote: > >> ISA boxes can ^^^^^^^^^ > >> have hardware installed (accidentally?) with devices sharing the same IRQ, but > >> the drivers cannot deal with it. > > >The sharing of interrupts between ISA devices is an electrical > >constraint. When two devices are attempting to use a common IRQ line, > > That's why he only wanted to share them for EISA/ISA boxes :-). That's funny, I see ISA boxes mentioned above :) But maybe you can tell me how an EISA/ISA box solves the IRQ sharing problem for ISA devices. Alex From owner-freebsd-hardware Fri Jul 19 07:30:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28663 for hardware-outgoing; Fri, 19 Jul 1996 07:30:40 -0700 (PDT) Received: from home.winc.com (mgessner@home.winc.com [204.178.182.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28652 for ; Fri, 19 Jul 1996 07:30:37 -0700 (PDT) Received: (from mgessner@localhost) by home.winc.com (8.7.1/8.7.3) id KAA09554 for freebsd-hardware@freebsd.org; Fri, 19 Jul 1996 10:30:43 -0400 Message-Id: <199607191430.KAA09554@home.winc.com> Subject: WinModems and FreeBSD To: freebsd-hardware@freebsd.org (FreeBSD Hardware) Date: Fri, 19 Jul 1996 10:30:42 -0400 (EDT) From: mgessner@aristar.com Organization: Aristar Software Development, Inc. Reply-To: mgessner@aristar.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, All, I'd like to know if anyone knows why modems like the WinModem from USR or Supra 288i PnP don't work with other OS's? The modem accepts commands from the host, not the other way around, so the modem cannot know what the host OS is unless there is some specific software you have to run to "open" the modem up. Is this the case? TIA, Matt From owner-freebsd-hardware Fri Jul 19 08:47:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04022 for hardware-outgoing; Fri, 19 Jul 1996 08:47:11 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04009 for ; Fri, 19 Jul 1996 08:47:07 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id IAA18234; Fri, 19 Jul 1996 08:45:31 -0700 (PDT) Message-Id: <199607191545.IAA18234@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: E00114@vnet.atea.be (Rob Schofield) cc: freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ In-reply-to: Your message of Fri, 19 Jul 96 09:43:10 +0700. Date: Fri, 19 Jul 1996 08:45:30 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Additionally, we have the question of the interrupt being Edge (it spikes >down, which latches on the interrupt controller) or level (it goes down and >stays down until the CPU has serviced it). > >I have an EISA box which allows you to say "for this device at this address, >expect an interrupt on IRQ X, level triggered" or "edge triggered". This sets >up the PIC (interrupt controller) to expect a certain type of interrupt >alright, but if the card in the slot doesn't behave like that, then >interrupts might not register with the PIC. > >The original question was really to fish for opinions - given conventional >UARTS (16550s) on an ISA card in an EISA box, can I set these two up to >appear as a multiport by setting up the interrupt controller to handle two >UARTs at different register addresses but sharing the same IRQ line? (ie. >"dupe" sio into thinking it's handling a multiport). I don't think so. If it works, it's by accident. Edge-triggered interrupts are a specific feature of the EISA design. ISA cards do not know how to do that. You need an _EISA_ board, in an EISA bus, to correctly support this. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hardware Fri Jul 19 11:57:03 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12969 for hardware-outgoing; Fri, 19 Jul 1996 11:57:03 -0700 (PDT) Received: from cbgw1.att.com (cbgw1.att.com [192.20.239.133]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA12957 for ; Fri, 19 Jul 1996 11:57:00 -0700 (PDT) Received: from aloft by cbig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id OAA11130; Fri, 19 Jul 1996 14:51:55 -0400 Received: from stargazer (stargazer.cnet.att.com) by aloft (4.1/DCS-aloft-M5.1) id AA12121; Fri, 19 Jul 96 14:55:29 EDT Received: by stargazer (4.1/DCS-aloft_client-S2.1) id AA15834; Fri, 19 Jul 96 14:55:27 EDT Date: Fri, 19 Jul 96 14:55:27 EDT From: gtc@aloft.att.com (gary.corcoran) Message-Id: <9607191855.AA15834@stargazer> To: freebsd-hardware@freebsd.org, mgessner@aristar.com Subject: Re: WinModems and FreeBSD Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Regarding: > I'd like to know if anyone knows why modems like the WinModem from USR >or Supra 288i PnP don't work with other OS's? The modem accepts >commands from the host, not the other way around, so the modem cannot >know what the host OS is unless there is some specific software you have to >run to "open" the modem up. Is this the case? The Supra 288i PNP may be a different case, but the USR WinModem I believe is one of the "controller-less" modems. That is, to save a few bucks, they removed the controller CPU from the card, and replace its functionality by a VxD - a Windows-specific Virtual device Driver. That means that the "modem" is useless without its VxD, which of course only runs on Windows. So you may as well forget about running it on any other operating system. Sorry, but you'll have to buy a "real" modem (with a controller)... Gary From owner-freebsd-hardware Fri Jul 19 13:42:59 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18068 for hardware-outgoing; Fri, 19 Jul 1996 13:42:59 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18062 for ; Fri, 19 Jul 1996 13:42:56 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0uhOBg-000wzYC; Fri, 19 Jul 96 15:38 PDT Received: from cc:Mail by ccgate.infoworld.com id AA837808823; Fri, 19 Jul 96 14:30:00 PST Date: Fri, 19 Jul 96 14:30:00 PST From: "Brett Glass" Message-Id: <9606198378.AA837808823@ccgate.infoworld.com> To: (Rob Schofield), freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It'd only be possible to implement shared IRQs on ISA if (a) The motherboard chipset can accept level-triggered interrupts; (b) Each peripheral board sharing the IRQ was rewired to be open-collector (many are implemented in VLSI, so you'd probably have to cut traces and add parts); (c) A pullup resistor was placed on the motherboard; and (d) All the software (including, possibly, the BIOS) was rewritten to work with the changed hardware. Whadda mess. --Brett From owner-freebsd-hardware Fri Jul 19 13:43:03 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18084 for hardware-outgoing; Fri, 19 Jul 1996 13:43:03 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18075 for ; Fri, 19 Jul 1996 13:43:00 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0uhOBb-000wzAC; Fri, 19 Jul 96 15:38 PDT Received: from cc:Mail by ccgate.infoworld.com id AA837808819; Fri, 19 Jul 96 13:43:43 PST Date: Fri, 19 Jul 96 13:43:43 PST From: "Brett Glass" Message-Id: <9606198378.AA837808819@ccgate.infoworld.com> To: Alex Nash , bde@zeta.org.au Cc: E00114@vnet.atea.be, freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > maybe you can tell me how an EISA/ISA box solves the IRQ sharing problem > for ISA devices. It doesn't. Only EISA devices or E-ISA devices can share IRQs. From owner-freebsd-hardware Fri Jul 19 14:26:02 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA20372 for hardware-outgoing; Fri, 19 Jul 1996 14:26:02 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA20365 for ; Fri, 19 Jul 1996 14:25:54 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id QAA20612 for ; Fri, 19 Jul 1996 16:26:51 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id QAA20605 for ; Fri, 19 Jul 1996 16:26:50 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id QAA13988; Fri, 19 Jul 1996 16:31:21 -0500 (CDT) Date: Fri, 19 Jul 1996 16:31:20 -0500 (CDT) From: Alex Nash To: Brett Glass cc: bde@zeta.org.au, E00114@vnet.atea.be, freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ In-Reply-To: <9606198378.AA837808819@ccgate.infoworld.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Brett Glass wrote: > > maybe you can tell me how an EISA/ISA box solves the IRQ sharing problem > > for ISA devices. > > It doesn't. Of course not, it was rhetorical. > Only EISA devices or E-ISA devices can share IRQs. I think you misunderstand (and why wouldn't you now that you've removed the context of my message :). The original poster wrote: ISA boxes can have hardware installed (accidentally?) with devices sharing the same IRQ, but the drivers cannot deal with it. I responded with a spiel about IRQ sharing with an ISA bus being an electrical constraint, not a driver constraint. Bruce responded with... That's why he only wanted to share them for EISA/ISA boxes :-). Now help me out if I just don't get this, but the text I had quoted was about ISA, my followup was about ISA, and then I was corrected(?) because the original poster wanted to use EISA/ISA boxes (yet I was not discussing EISA at all). I didn't understand why it was relevant that the sharing was being done on an EISA/ISA box. Alex From owner-freebsd-hardware Fri Jul 19 14:42:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21378 for hardware-outgoing; Fri, 19 Jul 1996 14:42:46 -0700 (PDT) Received: from cbgw1.att.com (cbgw1.att.com [192.20.239.133]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA21371 for ; Fri, 19 Jul 1996 14:42:41 -0700 (PDT) Received: from aloft by cbig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id RAA01471; Fri, 19 Jul 1996 17:30:25 -0400 Received: from stargazer (stargazer.cnet.att.com) by aloft (4.1/DCS-aloft-M5.1) id AA16133; Fri, 19 Jul 96 17:35:13 EDT Received: by stargazer (4.1/DCS-aloft_client-S2.1) id AA15984; Fri, 19 Jul 96 17:35:10 EDT Date: Fri, 19 Jul 96 17:35:10 EDT From: gtc@aloft.att.com (gary.corcoran) Message-Id: <9607192135.AA15984@stargazer> To: Brett_Glass@ccgate.infoworld.com, alex@fa.tdktca.com, bde@zeta.org.au Subject: Re: Multiple COM ports with same IRQ Cc: E00114@vnet.atea.be, freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> maybe you can tell me how an EISA/ISA box solves the IRQ sharing problem >> for ISA devices. > >It doesn't. Only EISA devices or E-ISA devices can share IRQs. To clarify, (correct me if I'm wrong): EISA devices, which by definition only plug into an EISA motherboard, can only share IRQs if they have "open-collector" (i.e. open-drain) drivers on the IRQ line. This allows any device on a particular IRQ to pull the line low without "fighting" any other device's IRQ driver. This capability, combined with the fact that EISA motherboards allowing changing the PIC operation to be level sensitive instead of edge-triggered, is what potentially allows EISA devices to share IRQs. One question though: The "open-collector" scheme described above (which is what is commonly used for interrupt sharing) works quite well for ACTIVE LOW interrupt signalling. But the IRQ lines on EISA (and ISA) are ACTIVE HIGH signals. Do EISA PICs also allow the active state of the bus IRQs to be changed from high to low? (I don't think so). If not, then how *is* IRQ sharing implemented on EISA devices? Gary Gary.Corcoran@lucent.com From owner-freebsd-hardware Fri Jul 19 21:34:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA12844 for hardware-outgoing; Fri, 19 Jul 1996 21:34:37 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA12837 for ; Fri, 19 Jul 1996 21:34:32 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id VAA20291; Fri, 19 Jul 1996 21:30:12 -0700 (PDT) Message-Id: <199607200430.VAA20291@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: gtc@aloft.att.com (gary.corcoran) cc: Brett_Glass@ccgate.infoworld.com, alex@fa.tdktca.com, bde@zeta.org.au, E00114@vnet.atea.be, freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ In-reply-to: Your message of Fri, 19 Jul 96 17:35:10 -0400. <9607192135.AA15984@stargazer> Date: Fri, 19 Jul 1996 21:30:09 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >One question though: The "open-collector" scheme described above (which is >what is commonly used for interrupt sharing) works quite well for >ACTIVE LOW interrupt signalling. But the IRQ lines on EISA (and ISA) >are ACTIVE HIGH signals. Do EISA PICs also allow the active state of >the bus IRQs to be changed from high to low? (I don't think so). >From the vague references I found quickly scanning through my BusLogic Technical Reference Manual, it indeed appears the state of the signal is inverted depending on which mode it is running in. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hardware Sat Jul 20 05:05:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA06579 for hardware-outgoing; Sat, 20 Jul 1996 05:05:48 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA06574 for ; Sat, 20 Jul 1996 05:05:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id VAA29911; Sat, 20 Jul 1996 21:48:28 +1000 Date: Sat, 20 Jul 1996 21:48:28 +1000 From: Bruce Evans Message-Id: <199607201148.VAA29911@godzilla.zeta.org.au> To: Brett_Glass@ccgate.infoworld.com, alex@fa.tdktca.com Subject: Re: Multiple COM ports with same IRQ Cc: E00114@vnet.atea.be, bde@zeta.org.au, freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Only EISA devices or E-ISA devices can share IRQs. >I think you misunderstand (and why wouldn't you now that you've removed >the context of my message :). The original poster wrote: > ISA boxes can have hardware installed (accidentally?) with devices > sharing the same IRQ, but the drivers cannot deal with it. >I responded with a spiel about IRQ sharing with an ISA bus being an >electrical constraint, not a driver constraint. Bruce responded with... > That's why he only wanted to share them for EISA/ISA boxes :-). >Now help me out if I just don't get this, but the text I had quoted >was about ISA, my followup was about ISA, and then I was corrected(?) >because the original poster wanted to use EISA/ISA boxes (yet I was not >discussing EISA at all). I didn't understand why it was relevant >that the sharing was being done on an EISA/ISA box. IIRC, the original poster only wanted to know about EISA systems with ISA devices and the question was to what exent EISA compensated for the shortcomings of ISA devices. I think it can easily arrange for level triggered IRQs for xx(x)50 devices because the devices naturally produce such IRQs, but it can't make shared IRQs work because it is subject to the same electrical constraints as ISA. Bruce From owner-freebsd-hardware Sat Jul 20 05:47:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13724 for hardware-outgoing; Sat, 20 Jul 1996 05:47:40 -0700 (PDT) Received: from wong.rogerswave.ca (a17b32.rogerswave.ca [204.92.17.32]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13713 for ; Sat, 20 Jul 1996 05:47:38 -0700 (PDT) Received: (from wong@localhost) by wong.rogerswave.ca (8.7.5/8.7.3) id IAA00461; Sat, 20 Jul 1996 08:45:56 -0400 (EDT) Date: Sat, 20 Jul 1996 08:45:56 -0400 (EDT) From: Ken Wong To: Bruce Evans cc: E00114@vnet.atea.be, freebsd-hardware@FreeBSD.org Subject: Re: Multiple COM ports with same IRQ In-Reply-To: <199607190254.MAA30468@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Jul 1996, Bruce Evans wrote: > >Considering the UARTS will generate edge interrupt rather than level, will > >this work? Will sio grab the "dual port" interrupt then interrogate the > >individual status regs of the UARTS? I'm not too concerned with operation > >under DOS here, so I'm only concerned with FBSD. > > 16550 UARTs just generate signals that should work with either level or > edge sensitive schemes. If the interrupts are still edge sensitive from > the 8259 PIC's point of view, then they can't be shared. ^^^^^^^^^ I thought all 8259 PIC can be programmed to use either edge or level. anyway at least mine said it does. Ken > > Bruce > > From owner-freebsd-hardware Sat Jul 20 06:21:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA15313 for hardware-outgoing; Sat, 20 Jul 1996 06:21:31 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA15308 for ; Sat, 20 Jul 1996 06:21:30 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id IAA12696; Sat, 20 Jul 1996 08:20:10 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sat, 20 Jul 96 08:20 CDT Date: Sat, 20 Jul 1996 08:20:09 -0500 (CDT) From: Alex Nash X-Sender: nash@Venus.mcs.com To: Bruce Evans cc: Brett_Glass@ccgate.infoworld.com, alex@fa.tdktca.com, E00114@vnet.atea.be, bde@zeta.org.au, freebsd-hardware@freebsd.org Subject: Re: Multiple COM ports with same IRQ In-Reply-To: <199607201148.VAA29911@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Jul 1996, Bruce Evans wrote: > IIRC, the original poster only wanted to know about EISA systems with > ISA devices and the question was to what exent EISA compensated for the > shortcomings of ISA devices. The statement I addressed from the original poster was that shared interrupts for ISA devices is a driver problem. This is simply not true, and I feel that it needs to be pointed out regardless of whether the topic was EISA or not. Alex From owner-freebsd-hardware Sat Jul 20 06:39:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA15769 for hardware-outgoing; Sat, 20 Jul 1996 06:39:49 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA15760 for ; Sat, 20 Jul 1996 06:39:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id XAA32484; Sat, 20 Jul 1996 23:10:08 +1000 Date: Sat, 20 Jul 1996 23:10:08 +1000 From: Bruce Evans Message-Id: <199607201310.XAA32484@godzilla.zeta.org.au> To: bde@zeta.org.au, wong@wong.rogerswave.ca Subject: Re: Multiple COM ports with same IRQ Cc: E00114@vnet.atea.be, freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> 16550 UARTs just generate signals that should work with either level or >> edge sensitive schemes. If the interrupts are still edge sensitive from >> the 8259 PIC's point of view, then they can't be shared. > ^^^^^^^^^ >I thought all 8259 PIC can be programmed to use either edge or level. >anyway at least mine said it does. If it is programmed for level triggered interrupts, then all devices have to generate IRQ signals that stay asserted while there is an IRQ. Some don't. I think at least MFM disk controllers usually assert IRQ and pulse it low to cause an edge. I think the 8254 clock in RATEGEN (standard FreeBSD) mode is similar. Perhaps more importantly, it must be possible to program the device to stop it interrupting. This is inconvenient for the 8254 clock. In SQWAVE (standard BIOS) mode it asserts IRQ half the time and there is no good way to stop it interrupting half the time if interrupts are level sensitive. Bruce From owner-freebsd-hardware Sat Jul 20 22:50:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA14641 for hardware-outgoing; Sat, 20 Jul 1996 22:50:43 -0700 (PDT) Received: from mccane1.mccane.com (kcx-ks9-53.ix.netcom.com [198.211.69.117]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA14620; Sat, 20 Jul 1996 22:50:33 -0700 (PDT) Received: (from root@localhost) by mccane1.mccane.com (8.7.5/8.7.3) id AAA02656; Sun, 21 Jul 1996 00:48:34 -0500 (CDT) Date: Sun, 21 Jul 1996 00:48:33 -0500 (CDT) From: Wm Brian McCane To: hardware@freebsd.org cc: hackers@freebsd.org Subject: SMP FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I know I have seen various people discussing SMP for FreeBSD (Terry Lambert is one I think). I am interested in this and was wondering what motherboards have been tested (successfully 8). I have access to a Micronics dual-133 and a Tyan dual-133/166, and want to know about compatibility issues. I am not really afraid of a BETA at this point (I already run -current, so how bad can it get 8). Any help would be appreciated. brian bmccane@ix.netcom.com