Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 Sep 2002 07:30:11 +0200
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/dev/pccard pccard.c 
Message-ID:  <95960.1031117411@critter.freebsd.dk>
In-Reply-To: Your message of "Tue, 03 Sep 2002 20:40:42 MDT." <20020903.204042.23985384.imp@bsdimp.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020903.204042.23985384.imp@bsdimp.com>, "M. Warner Losh" writes:
>In message: <68113.1031052593@critter.freebsd.dk>
>            Poul-Henning Kamp <phk@critter.freebsd.dk> writes:
>: In message <200209031124.g83BOPAh090297@freefall.freebsd.org>, Poul-Henning Kam
>: p writes:
>: >phk         2002/09/03 04:24:25 PDT
>: >
>: >  Modified files:
>: >    sys/dev/pccard       pccard.c 
>: >  Log:
>: >  Drop another cookie to wet Warners appetite:
>: >  
>: >  We need to call the drivers interrupt function even though the card is not
>: >  multifunction.
>: 
>: This should make interrupt handling work on non-multifunction cards.
>
>They already work on non mfc cards.  The changes will make it work on
>more MFC cards.  most mfc cards don't implement the registers, so they
>read as 0xff and a write is a noop.  The non-mfc cards that implement
>these registers are the only ones that this fixes :-)
>
>Otherwise, how would most cards work, which aren't mfc?

I don't trust the "read as 0xff" bit in the above statement...

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95960.1031117411>