Date: Thu, 11 Feb 1999 22:50:37 +0100 From: Nicolas Souchu <nsouch@teaser.fr> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: Mike Smith <mike@smith.net.au>, Bill Fenner <fenner@parc.xerox.com>, hackers@FreeBSD.ORG, wpaul@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Regarding tcpdump and plip Message-ID: <19990211225037.40571@breizh.prism.uvsq.fr> In-Reply-To: <xzpk8xs5zfm.fsf@flood.ping.uio.no>; from Dag-Erling Smorgrav on Mon, Feb 08, 1999 at 10:59:57PM %2B0100 References: <xzp90e9brl4.fsf@flood.ping.uio.no> <199902080148.RAA09054@dingo.cdrom.com> <19990208195855.56187@breizh.prism.uvsq.fr> <xzpsocg63t5.fsf@flood.ping.uio.no> <19990208222829.53422@breizh.prism.uvsq.fr> <xzpk8xs5zfm.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 08, 1999 at 10:59:57PM +0100, Dag-Erling Smorgrav wrote:
>
>Nicolas Souchu <nsouch@teaser.fr> writes:
>> On Mon, Feb 08, 1999 at 09:25:26PM +0100, Dag-Erling Smorgrav wrote:
>> > Better yet, let's rip it out of -current (I have an lpt-less src/sys
>> > tree just waiting to be committed), and stick an #error in -stable's
>> > lpt.c saying "This driver is deprecated, use ppbus instead". That way,
>> > we give everybody advance warning without risking a botched commit
>> > and/or people complaining that their kernel has inexplicably failed to
>> > build.
>> Ok. Is UPDATING only a -current resource or may it be updated in 3.1?
>
>I don't know, I was planning to just notify Warner Losh and let him
>fix src/UPDATING.
>
>> > In any case, does anybody mind if I go ahead and remove the lpt driver
>> > from -current, say, tomorrow?
>> Don't forget GENERIC.. this patch or whatelse.
>
>Don't worry, I've patched GENERIC, LINT, files.i386 and the PicoBSD
>kernels, and removed lpt.c and lpt.4. I'll still have to track down
>references to the driver in the documentation though.
lpt.4 also? nlpt.4 refers to it. I'll have to complete nlpt.4.
Shouldn't we have moved nlpt to lpt to keep the ages dated tags?
>
>> "This supposes slip/ppp is statically configured for plip", would add Bruce.
>
>What are the consequences of just setting the interrupt mask to net in
>all cases? Does one still need slip? Is it wrong to do so when plip is
>not compiled in?
So, you choosed 'net'. But it won't work better than 'tty' if ppp is not
statically configured. And for a basic configuration, printer may not work
with interrupts :(
Or we should add the ppp trick as in net/ppp_tty.c. I was waiting for some
new stuff for interrupt configuration to update ppc.c. -wollman was working
on it in the past. I don't know if it's terminated.
/*
* Make sure that the soft net "engine" cannot run while spltty code is
* active. The if_ppp.c code can walk down into b_to_q etc, and it is
* bad if the tty system was in the middle of another b_to_q...
*/
tty_imask |= softnet_imask; /* spltty() block spl[soft]net() */
net_imask |= softtty_imask; /* splimp() block splsofttty() */
net_imask |= tty_imask; /* splimp() block spltty() */
update_intr_masks();
Enclosed with splhigh().
>
>DES
>--
>Dag-Erling Smorgrav - des@flood.ping.uio.no
>
--
nsouch@teaser.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990211225037.40571>