Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751028AbWC0NtR (ORCPT ); Mon, 27 Mar 2006 08:49:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751029AbWC0NtQ (ORCPT ); Mon, 27 Mar 2006 08:49:16 -0500 Received: from ns.suse.de ([195.135.220.2]:55223 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1751023AbWC0NtQ (ORCPT ); Mon, 27 Mar 2006 08:49:16 -0500 Date: Mon, 27 Mar 2006 15:49:11 +0200 Message-ID: From: Takashi Iwai To: Rene Herman Cc: Clemens Ladisch , ALSA devel , Adrian Bunk , Linux Kernel Subject: Re: [Alsa-devel] [ALSA] AdLib FM card driver In-Reply-To: <4427E560.4080702@keyaccess.nl> References: <442710A1.5030207@keyaccess.nl> <20060327083113.GB2521@turing.informatik.uni-halle.de> <4427E560.4080702@keyaccess.nl> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta25) (eggplant) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1942 Lines: 48 At Mon, 27 Mar 2006 15:15:12 +0200, Rene Herman wrote: > > Clemens Ladisch wrote: > > > Rene Herman wrote: > > >> I also stuck a very tiny HOWTO in ALSA-Configuration.txt, assuming > >> quite a few people would have no idea how to operate the thing, > >> even if they do happen across a card. Is it okay there? > > > > It should probably go into a seperate file below Documentation/. > > Probably. Documentation/sound/alsa/adlib.txt is ofcourse okay but I saw > a few other remark type things in ALSA-Configuration as well. Seeing as > how it's very small, and given the tendency of Documentation/ to not be > updated alongside code itself, I thought I'd try to get away with just > keeping things in the one file... Yes, it's not so big, so could be embedded in that file. > > I think at least the port address for the first card should be > > defaulted to 0x388. > > No, you never want to autoprobe ISA due to the non-discoverability of > the old non-PnP ISA bus. If you just start poking at addresses you might > touch something sensitive. The generic example of this is screwing over > a Novell NIC and while there are still some ALSA drivers that do ISA > autoprobing (es1688, es18xx, gus, opti9xx, sb8, sb16) this has been > verboten in the tree in general for some time now. > > Hardcoding addresses and probing there might be a bit more userfriendly > but people who install an 8-bit ISA AdLib FM in this day and age are > likely not the type to care deeply about userfriendlyness anyway... > > Note lastly that the adlib_card OSS driver also needed the address > passed in. OK, we'd need an autoprobe if the old system were capable, but it's not the case. Takashi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/