From owner-freebsd-current@FreeBSD.ORG Mon Sep 15 20:13:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EEBC106564A for ; Mon, 15 Sep 2008 20:13:14 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout017.mac.com (asmtpout017.mac.com [17.148.16.92]) by mx1.freebsd.org (Postfix) with ESMTP id 15F818FC18 for ; Mon, 15 Sep 2008 20:13:13 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from vghiya-t60.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp017.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0K790096B6TY7N30@asmtp017.mac.com>; Mon, 15 Sep 2008 13:13:11 -0700 (PDT) Message-id: <3B9B5EED-6627-43F8-A5FC-7B2C7B2D38ED@mac.com> From: Marcel Moolenaar To: John Baldwin In-reply-to: <200809151522.08679.jhb@freebsd.org> Date: Mon, 15 Sep 2008 13:13:10 -0700 References: <48CE59C2.9060307@icyb.net.ua> <48CE91AB.3000200@icyb.net.ua> <9D0F7169-9461-4F32-9420-702BED840A20@mac.com> <200809151522.08679.jhb@freebsd.org> X-Mailer: Apple Mail (2.928.1) Cc: freebsd-current@freebsd.org, Andriy Gapon Subject: Re: sio => uart: one port is gone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 20:13:14 -0000 On Sep 15, 2008, at 12:22 PM, John Baldwin wrote: > On Monday 15 September 2008 12:55:33 pm Marcel Moolenaar wrote: >> >> On Sep 15, 2008, at 9:47 AM, Andriy Gapon wrote: >> >>> on 15/09/2008 19:41 Marcel Moolenaar said the following: >>>> So, if you compile acpi(4) as a module, you must compile all >>>> it's depending drivers as modules as well. Or you compile acpi >>>> into the kernel... >>> >>> I understand the logic, but OTOH uart can work without acpi too, so >>> it's not a strict dependency. >> >> Well, yes. That's what's causing your "problem". You compile a >> kernel without acpi but with uart. As such, uart will be built >> without acpi support. uart does indeed work without acpi. >> >> The problem is that people then load the acpi module at runtime >> and expect uart to work with acpi. That's not going to fly. If >> one builds uart as a module, all possible support is included >> and it works as expected. >> >>> Also, this (acpi dependency) doesn't seem to be documented. >> >> It's standard behaviour. > > The problem is that right now we ship with acpi.ko as a module by > default and > have the loader auto-load acpi.ko IFF the machine supports ACPI. Well, don't do that then. Just have the device probe check if acpi is supported and attach if yes. -- Marcel Moolenaar xcllnt@mac.com