From owner-freebsd-questions  Mon Feb 16 15:12:02 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA00600
          for freebsd-questions-outgoing; Mon, 16 Feb 1998 15:12:02 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from subcellar.mwci.net (subcellar.mwci.net [205.254.160.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00492
          for <questions@freebsd.org>; Mon, 16 Feb 1998 15:11:18 -0800 (PST)
          (envelope-from jwalt@mwci.net)
Received: from firewall.mwci.net (firewall.mwci.net [205.254.160.134])
	by subcellar.mwci.net (8.8.8/8.8.5) with SMTP id RAA23843
	for <questions@freebsd.org>; Mon, 16 Feb 1998 17:11:15 -0600 (CST)
Date: Mon, 16 Feb 1998 17:11:15 -0600 (CST)
From: Jesse Walters <jwalt@mwci.net>
To: questions@FreeBSD.ORG
Subject: Luigi Rizzo's pnp mod (fwd)
Message-ID: <Pine.BSF.3.96.980216171023.11679A-100000@firewall.mwci.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	I emailed Luigi about this but he is understandably very busy,
hopefully this list can help me out.
	I am trying to get my awe32 pnp working and I need to install
Rizzo's pnp support. I copyed the pnp.c and pnp.h to /sys/i386/isa and I
ran from / patch </temp/patches.225  When I entered the first patch
/sys/i386/i386/autoconf.c it came back with an error hunk #1 failed.  Then
when I ran the patch for /sys/i386/i386/userconfig.c it worked fine.
Again, though at /sys/i386/conf/files.i386 it said 
hunk#1 failed at 67
hunk#2 failed at 217
	I am not very good at c so I don't know how to add them manually.
I am running 2.2.5(nov '97).  If anyone can walk me through the proccess
or attach the two files autoconf.c and files.i386 with the patches already
installed for a 2.2.5 system I would appriciate it.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message