From owner-freebsd-current Sat May 1 0:17:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4883014E38 for ; Sat, 1 May 1999 00:17:07 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA96423; Sat, 1 May 1999 08:17:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 1 May 1999 08:17:25 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" Cc: Steve Kargl , John Polstra , dwhite@resnet.uoregon.edu, current@freebsd.org Subject: Re: PCM In-Reply-To: <28697.925524873@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Apr 1999, Jordan K. Hubbard wrote: > > It must be something that entered the tree late yesterday afternoon or > > an interaction between devices. > > Same here... > > FreeBSD 4.0-CURRENT #0: Wed Apr 28 23:21:40 PDT 1999 > jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY > ... > pcm0 at port 0x220 irq 5 drq 1 flags 0x13 on isa0 > pcm0: interrupting at irq 5 > > And I'm using this right now to listen to an mp3 of a Loggins and > Messina album, so it must work. :-) > > One thing I did notice which *is* kinda new, as of this last kernel, > is this: > > smbus0: on bti2c0 > smb0: on smbus0 > bktr0: interrupting at irq 17 > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner. > devclass_alloc_unit: npx0 already exists, using next available unit number > > I'm pretty sure that npx0 does not "already exist" in this context, > leading me to believe that the message is actually being intermingled > with another probe's test or something is very odd here. :) Do you have 'npx0 at isa?' in your config file by any chance? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message