Re: [Alsa-devel] [ALSA] AdLib FM card driver

[Takashi Iwai <tiwai@suse.de>]

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