Date: Mon, 9 Feb 1998 06:46:11 +0100 From: Eivind Eklund <eivind@yes.no> To: Luigi Rizzo <luigi@labinfo.iet.unipi.it> Cc: multimedia@FreeBSD.ORG Subject: Re: Conflict i386/isa/snd/ad1848.c and .../sound/ad1848.c Message-ID: <19980209064611.56883@follo.net> In-Reply-To: <199802090353.EAA13545@labinfo.iet.unipi.it>; from Luigi Rizzo on Mon, Feb 09, 1998 at 04:53:24AM %2B0100 References: <199802090431.FAA19991@bitbox.follo.net> <199802090353.EAA13545@labinfo.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 09, 1998 at 04:53:24AM +0100, Luigi Rizzo wrote: > > There can't presently be two files with the same name in the source > > tree. With the version of Luigi's sound driver compiled into FreeBSD, > > what ??? pathnames (absolute) are in /sys/i386/conf/files.i386, if your > file is properly patches you shouldn't have problems. Absolute pathnames aren't enough. We can't have files with the same name different places in the kernel tree; it confuse config, as well as dying when LINT is compiled, or LINT is full-scale linted using temp-files. This has been discussed several times on the mailing-lists. > > I seem to be getting the ad1848.c from the 'sound' directory, not > > snd... > > most likely this is because you left in the config file > some of the old definitions, e.g. "controller snd0" or the voxware > devices. You have to remove them since we don't support two drivers for > the same hardware, not even in a LINT kernel Yes, we do. In a LINT kernel, we do. I was this ----><----- close to breaking your driver today because of that conflict. I just discovered it because by chance have your drivers in my own personal kernel, and test-compiled that, too, before committing. It would be good if you could either contact Peter Wemm <peter@freebsd.org> about having either your file or VoxVare's file renamed (with a suitable patch for the relevant other files, like i386/conf/files.i386), or contact core about throwing out the VoxWare drivers. Otherwise, I'll have to do it - as it is, your driver risks getting broken everytime somebody do a large-scale change to the kernel. It is just pure luck that none of the option changes was hit by this. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980209064611.56883>