From alsa-devel-owner@alsa.jcu.cz  Fri Dec 11 00:12:25 1998
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id AAA03604;
	Fri, 11 Dec 1998 00:11:00 +0100
Date: Fri, 11 Dec 1998 00:11:01 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: Abramo Bagnara <abbagnara@racine.ra.it>
cc: alsa-devel@alsa.jcu.cz
Subject: Re: ES1869 driver
In-Reply-To: <36701B4A.687E73DE@racine.ra.it>
Message-ID: <Pine.LNX.3.96.981211000352.5662H-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Thu, 10 Dec 1998, Abramo Bagnara wrote:

> Jaroslav Kysela wrote:
> > 
> > On Thu, 10 Dec 1998, Abramo Bagnara wrote:
> > 
> > > Jaroslav Kysela wrote:
> > > >
> 
> > > In isapnp.c you use check_region, request_region, release_region for
> > > _PIDXR (0x279).
> > > This port is used and allocated by the second parallel port and this
> > > generates a conflict.
> > > I suppose that conflict is actually inexistant cause parallel port
> > > driver use this port for input and isapnp use it for output, but my
> > > knowledge of ISA architecture is insufficient to affirm this for sure.
> > > I don't know what's the cleaner way to handle this situation.
> > 
> > I don't know howto solve this problem too. Probably clean way should be
> > create some flag by port region which should lock READ or WRITE or BOTH
> > directions.
> 
> Perhaps you want to write a note about this for Alan or Linus or other
> appropriate discussion place.
> In the mean time I strongly suggest you to comment out check_region,
> request_region, release_region for _PIDXR.
> This is harmless and make usable your code.
> I think that many end-user will refuse to test your code if isapnp
> module not even load.

OK. Done.

> > > I get strange result from /proc/isapnp:
> > > # cat /proc/isapnp > isapnp.before
> > > # isapnp /etc/isapnp.conf
> > > # cat /proc/isapnp > isapnp.after
> > 
> > This is wrong idea mix isapnp.o module and isapnptools. Module isapnp.o
> > uses different RDP port (0x213) that isapnptools (0x203). This is why
> > you get only 0xff (nothing) from RDP port which is modified with
> > isapnptools. Port 0x203 is range for joystick port in some soundcards.
> 
> At the moment I (and many other users) MUST use isapnptools to configure
> the other
> Pnp cards. I think that it's a better solution to permit an harmless
> mixing of isapnp.o module
> and isapnptools.
> This can be achieved in this way:
> 1) change READPORT in isapnp.conf
> 2) comment request_region and release_region for isapnp_rdp (not
> check_region)
>    This avoid a fatal error in recent version of isapnptools that check
> /proc/ioports.
>    A better solution is to patch isapnptools to recognize your driver.
> 3) Change the isolation process in isapnp module to preserve current
> configuration
>    (this is a good thing in any case)

I don't like this solution - two ways - user will be confused.
I added write interface to /proc/isapnp file. Get latest CVS source, read
file alsa-driver/support/isapnp.txt and send me back your opinion(s).
I hope that isapnp.o module solve all ISA PnP things now...

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


