From owner-svn-src-all@FreeBSD.ORG Sun Jan 25 17:18:59 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B25A894; Sun, 25 Jan 2015 17:18:59 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0B8B4C51; Sun, 25 Jan 2015 17:18:58 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t0PHIpI3093759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2015 19:18:52 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t0PHIpI3093759 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t0PHInbv093758; Sun, 25 Jan 2015 19:18:49 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 25 Jan 2015 19:18:49 +0200 From: Konstantin Belousov To: Dag-Erling Sm??rgrav Subject: Re: svn commit: r277694 - head/sys/amd64/conf Message-ID: <20150125171849.GA42409@kib.kiev.ua> References: <201501251202.t0PC2crJ029665@svn.freebsd.org> <86lhkqq5jc.fsf@nine.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86lhkqq5jc.fsf@nine.des.no> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Sergey Kandaurov , src-committers@freebsd.org X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 17:18:59 -0000 On Sun, Jan 25, 2015 at 03:49:27PM +0100, Dag-Erling Sm??rgrav wrote: > Sergey Kandaurov writes: > > Dag-Erling Sm??rgrav writes: > > > Log: > > > Remove ISA NICs. Anyone still using these on amd64 can build their > > > own kernel. > > If so, what about i386? (I'd rather not pc98) > > There's a greater chance of ISA devices still being in use on i386 > hardware than on amd64 hardware. I've never even heard of amd64 > hardware with ISA slots, but I guess there is a remote chance that The ISA slots where almost mandatory in the Pentium IV era chipsets, and latest Pentium IV CPUs were capable to run in long mode. For Core2 times, all CPUs were amd64, and ISA slots were on almost all m/b of that time, but not all. > someone may try to use something like an ep(4) PCCARD on a modern laptop > (which is a bad example, since ep(4) is loadable, but you get the idea). > > > What about device isa in DEFAULTS? > > It's still required for atkbdc. Device ISA is required for attachment of many unavoidable platform devices, like legacy atpic, RTC, old timers, and so on. Currently the physical lines used are provided by chipset emulation of the serial LPC bus. So even if there is no physical ISA or LPC bus, ISA as the logical construct is there. Most, if not all, monitoring chips are LPC-connected. On i386, there are even more rudiments, e.g. FPU is attached as the ISA device to still detect IRQ13-style of interrupts mis-reporting.