From owner-freebsd-stable  Tue Oct 21 18:51:36 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA25431
          for stable-outgoing; Tue, 21 Oct 1997 18:51:36 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25390
          for <freebsd-stable@FreeBSD.ORG>; Tue, 21 Oct 1997 18:51:15 -0700 (PDT)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00501;
	Wed, 22 Oct 1997 11:17:26 +0930 (CST)
Message-Id: <199710220147.LAA00501@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
cc: mike@smith.net.au (Mike Smith), tg@ihf.rwth-aachen.de, mark@vmunix.com,
        freebsd-stable@FreeBSD.ORG
Subject: Re: PNP and new Sound code ? 
In-reply-to: Your message of "Tue, 21 Oct 1997 09:46:40 +0100."
             <199710210846.JAA20825@labinfo.iet.unipi.it> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 Oct 1997 11:17:20 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > I don't think that would be a smart idea at all.  The most recent 
> > changes appear to have broken it on -current, and the code is certainly 
> > far far away from being ready for a production-level system.
...
> May I ask what kind of brokennes you are talking about ? If you
> refer to the message that Jordan sent out some time ago, he promptly
> took it back saying that it had nothing to do with the cancelled
> 3.0 snap.

I'm referring to this message, which I get from the most recent 
-current kernel I have built on my PnP box:

/kernel.atapi: Probing for PnP devices:
/kernel.atapi: CSN 1 Vendor ID: CTL009d [0x9d008c0e] Serial 0x0adc2c47
/kernel.atapi: This is a SB AWE64 PnP, but LDN 0 is disabled

An older kernel finds and configures the device correctly.

> This does not mean that it is unusable (maybe with minor patches,
> or a little bit more of documentation, if the one that i have
> already written is not enough) on a production system.

My point was just that in its current incarnation, it doesn't appear to 
work.  That's not a good advertisement for putting it into production.

> Just as a data point. During the last three months I have tried to
> support both the PnP and the audio driver. 

You'll have to wait until after we ship the SkYimet system and I finish 
my exams before you'll hear from me about this one, I fear.

mike