This is actually a deficiency in the ppbus stuff, there is no
telling what SPL level the subdriver wants to use, so the interrupt
should actually be released back to the system when no subdrivers
are open and be grabbed the way the subdriver wants it once it
aquires the bus.
The ZIP driver would probably want splcam/splbio, the pps wants
splabsolutelynobody() (and FAST_IRQ) and plip wants splnet().
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Maxim Sobolev <[EMAIL PROTECTED]> writes:
>> Some time ago I
>> had rised this question and Bruce Evans told that this problem arise
>> because of switch to newbus.
>You misunderstood what Bruce wrote. PLIP has always been broken. It
>used to be possible to hack around the brokenness by setting the
>interrupt mask to net instead of tty. With newbus, this hack is no
>longer possible (it was never correct anyway; it broke printing).
>The problem with PLIP is that it tries to do splnet stuff in at
>spltty. If you force the parallell port driver to run at splnet, PLIP
>works but you get panics when you print because it tries to do spltty
>stuff at splnet.
>SLIP and PPPD do black magic with interrupt masks so spltty and splnet
>become essentially equivalen (or so I understand). They do this
>because they have the exact same problems as PLIP - they need to do
>splnet stuff at spltty.
>Dag-Erling Smorgrav - [EMAIL PROTECTED]
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message