From owner-freebsd-arch@FreeBSD.ORG  Wed Aug 11 02:27:54 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 910BA16A4CE; Wed, 11 Aug 2004 02:27:54 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4E03943D3F; Wed, 11 Aug 2004 02:27:54 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.11/8.12.11) id i7B2Rrn2023321;
	Tue, 10 Aug 2004 21:27:53 -0500 (CDT)
	(envelope-from dan)
Date: Tue, 10 Aug 2004 21:27:53 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: Rostislav Krasny <rosti_bsd@yahoo.com>
Message-ID: <20040811022753.GD6474@dan.emsphone.com>
References: <200408091604.33984.jhb@FreeBSD.org>
	<20040811002731.46210.qmail@web14826.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040811002731.46210.qmail@web14826.mail.yahoo.com>
X-OS: FreeBSD 5.2-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: freebsd-arch@freebsd.org
Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"]
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Aug 2004 02:27:54 -0000

In the last episode (Aug 10), Rostislav Krasny said:
> unknown: <PNP0303> can't assign resources (port)
> unknown: <PNP0303> at port 0x60 on isa0
> unknown: <PNP0800> failed to probe at port 0x61 on isa0
> unknown: <PNP0a03> can't assign resources (port)
> unknown: <PNP0a03> at port 0x4d0-0x4d1 on isa0
> unknown: <PNP0c02> can't assign resources (port)
> unknown: <PNP0c02> at port 0x208-0x20f on isa0
> unknown: <PNP0501> can't assign resources (port)
> unknown: <PNP0501> at port 0x3f8-0x3ff on isa0
> unknown: <PNP0700> can't assign resources (port)
> unknown: <PNP0700> at port 0x3f2-0x3f5 on isa0
> unknown: <PNP0401> can't assign resources (port)
> unknown: <PNP0401> at port 0x378-0x37f on isa0
> unknown: <PNP0501> can't assign resources (port)
> unknown: <PNP0501> at port 0x2f8-0x2ff on isa0
> 
> P.S. What are these "unknown: <PNPXXXX>..." messages? I don't have so
> many PnP devices. And my speaker (port 0x61) is working properly. I
> even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse -p -e
> -w 23 I am a 5.2-CURRENT, test me.' :-)

PNP* devices are standard motherboard resources, like the keyboard
(PNP0303) and serial port (PNP0501).  There's a table at
http://www.plasma-online.de/english/identify/serial/pnp_id_pnp.html
that lists a lot of them.  My -current kernel correctly matches these
up to known devices, though:

$ devinfo -v | grep PNP0303
    atkbdc0 pnpinfo _HID=PNP0303 _UID=0 at handle=\_SB_.PCI0.ISA_.KBC_

-- 
	Dan Nelson
	dnelson@allantgroup.com