At Wed, 2 Jul 2003 13:50:07 -0500,
Ryan Underwood wrote:
>
> So, my question to alsa-devel is, what should be the proper way to do this fix?
> I could just do something like the following:
>
> ... try init ...
> else { /* if the chip remained busy, let's see if we have a Thinkpad that needs
> the chip powered on */
>
> outb(0x1c, 0x15e8);
> temp = inb(0x15e9);
> outb(temp|2, 0x15e8);
> ... try init again ...
> }
>
> But that seems a braindead solution -- we don't want to go banging random ports
> on a machine which may have other sensitive things attached there. Under
> windows 95, the 0x15e8-0x15ef is assigned to "Motherboard Resources" -- is there
> a way to determine whether this I/O range is allocated by the system in a useful
> manner instead of making guesswork?
i don't think we can retrieve this info generally. possibly readable
from somewhere in BIOS, but it's not general at all.
and, of course, the above sequence shouldn't be done as default.
i would recommend a special module option for this, as you suggested
in another mail.
Takashi
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
