Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Jan 1999 23:31:37 +0000 (GMT)
From:      Doug Rabson <dfr@nlsystems.com>
To:        "Justin T. Gibbs" <gibbs@plutotech.com>
Cc:        Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, Eivind Eklund <eivind@FreeBSD.ORG>, Nicolas Souchu <nsouch@teaser.fr>, Bruce Evans <bde@zeta.org.au>, mike@smith.net.au, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG
Subject:   Re: cvs commit: src/sys/dev/ppbus if_plip.c 
Message-ID:  <Pine.BSF.4.01.9901122329140.543-100000@herring.nlsystems.com>
In-Reply-To: <199901121626.JAA07694@pluto.plutotech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Jan 1999, Justin T. Gibbs wrote:

> ><<On Tue, 12 Jan 1999 00:29:39 +0100, Eivind Eklund <eivind@FreeBSD.ORG> said:
> >
> >> I don't know how the new bus framework will like this kind of
> >> behaviour, though.
> >
> >Easy -- you just declare your device as being of type `TTY|NET' and
> >the magic just comes naturally.  (Except, of course, that this part
> >isn't implemented yet, but it should be fairly trivial to do once the
> >interrupt code is debogotified.)
> 
> Can't we have a more dynamic mechanism than that?  You don't want 
> potentially shared interrupts in extra masks unless its absolutely
> necessary (e.g. PPP is compiled into the kernel, but the net mask
> is only modified when that line discipline is (de)activated and
> only for the device interrupts that are engaged in PPP activity).

The alternative to this is to specify what type of interrupt it is when
calling SETUP_INTR, e.g.:

	BUS_SETUP_INTR(parent, dev, res, TTY|NET, myintr, myarg, &ih);

In some ways, I prefer this since it means that an 'interrupt mux' doesn't
have to play games with its driver flags depending on what kind of kids
it is multiplexing.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037



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?Pine.BSF.4.01.9901122329140.543-100000>