From owner-freebsd-current@FreeBSD.ORG Sun Nov 25 12:46:40 2007 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 7B81A16A420 for ; Sun, 25 Nov 2007 12:46:40 +0000 (UTC) (envelope-from frank@pinky.sax.de) Received: from post.frank-behrens.de (post.frank-behrens.de [82.139.255.138]) by mx1.freebsd.org (Postfix) with ESMTP id D583B13C448 for ; Sun, 25 Nov 2007 12:46:39 +0000 (UTC) (envelope-from frank@pinky.sax.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pinky.sax.de; h=from:to:date:mime-version:subject:cc:in-reply-to:references:content-type:content-transfer-encoding:content-description; q=dns/txt; s=pinky1; t=1195994790; i=frank@pinky.sax.de; bh=nYcJictkQFlibY3vb6tnAjQDhWlowtslPifRqckOXU0=; b=ik2HwPDSwMIaK00eaDn/b3xkX5KffPfF7SHhVlWyvoB5rhQmDN/k5FwoZ1KGBag6gT5KdmOzvHedyBakxGvlbg== Received: from [192.168.20.32] (sun.behrens [192.168.20.32]) by post.frank-behrens.de (8.14.2/8.14.1) with ESMTP-MSA id lAPCkQiv088175; Sun, 25 Nov 2007 13:46:26 +0100 (CET) (envelope-from frank@pinky.sax.de) Message-Id: <200711251246.lAPCkQiv088175@post.frank-behrens.de> From: "Frank Behrens" To: FreeBSD Current Date: Sun, 25 Nov 2007 13:46:26 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <0D6858C2-3A4E-4EED-8D88-8557D3BF4443@mac.com> References: <200711231457.lANEv4KU002862@post.frank-behrens.de> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Hashcash: 1:24:071125:xcllnt@mac.com::Lnr2bkrv2qHIuuUs:3T2B X-Hashcash: 1:24:071125:freebsd-current@freebsd.org::/D/r4NWlkiHnRxr1:0000006OtZ Cc: Marcel Moolenaar Subject: Re: Can not boot 7.0-BETA3 with puc 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: Sun, 25 Nov 2007 12:46:40 -0000 Marcel, thanks for your explanation. Marcel Moolenaar wrote on 24 Nov 2007 10:20: > No, it isn't. The puc(4) driver can have different children. > Currently, it > can have 3 different children. Standard bus probing determines which > driver will attach. The puc(4) driver does not care about unit numbers > for > the simple reason that it doesn't care about which driver attaches. OK. I interpret this as: It is not puc's problem, which sio units are asssigned, it is the job for the sio driver itself. Then may I ask the question to the community: How do I setup my 7.0 configuration, that it is the same as in 6.x (POLA)? The serial devices on motherboard should be attached to sio0 and sio1, where sio0 is the console. The external PCI card with additional serial ports should be attached to subsequent sio units. When the loader uses sio0 as console and puc/sio assigns later sio0 to an external port this is definitely wrong. Anyway this stops the boot sequence. Is this an error in the sio(4) driver which was not detected until 7.0? I have in device.hints the default entries hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x10" hint.sio.0.irq="4" and the puc(4) port is assigned to sio0. Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.