On Tue, May 25, 1999 at 09:54:31AM +0100, Doug Rabson wrote:
>
> Could you also move the source for ppc out of the i386 tree into somewhere
> architecture independant.
PLEASE ask c...@freebsd.org for a repository copy when you do this. When
you renamed nlpt.c to lpt.c, you just committed a new f
On Mon, May 24, 1999 at 10:46:41PM -0700, Mike Smith wrote:
>>
>> Someone who would help me driving ppbus, yes. I didn't have enough time
>> last months.
>
>Do you expect that the situation will improve, or do you feel you need
>to hand it over to a new maintainer?
>
The situation shall improve.
On Mon, 24 May 1999, Mike Smith wrote:
> I would add
>
> - Improve ECP/EPP performance if possible.
>
> - Add/finish bidirectional ECP printer support.
Could you also move the source for ppc out of the i386 tree into somewhere
architecture independant. If its ported to new-bus
> >> What do you do about the "ppc" device? Formerly, it needed to be "net
> >> irq ..." if the "plip" device was going to be used, but "tty irq ..."
> >> otherwise. Which one did you pick?
> >
> >It needs to flip between one or both, but I can't raise Nicolas lately,
> >so I'm starting to fear
On Thu, Apr 29, 1999 at 10:26:48PM -0700, Mike Smith wrote:
>
>> In article <19990424190901.d3a791...@spinner.netplex.com.au>,
>> Peter Wemm wrote:
>> > This shouldn't cause much in the way of trouble, but it will complain
>> > about old lint in your config files. That includes 'net/tty/bio/cam'
Garrett Wollman wrote:
> <
> said:
>
>> It seems to me that all this spl hackery would be better avoided,
>> through a userland approach that used the tun device or something
>> similar.
>
> Some people need or prefer to have dependable bounds on the latency of
> their packets.
On the lp interf
Cleaning up some old mail
<
said:
> It seems to me that all this spl hackery would be better avoided,
> through a userland approach that used the tun device or something
> similar.
Some people need or prefer to have dependable bounds on the latency of
their packets.
-GAWollman
--
Garrett
Bruce Evans wrote:
> In old mail, John Polstra wrote:
>>
>>What do you do about the "ppc" device? Formerly, it needed to be "net
>>irq ..." if the "plip" device was going to be used, but "tty irq ..."
>>otherwise. Which one did you pick?
>
> tty was picked (see isa_compat.h). Also, support for
In old mail, John Polstra wrote:
>In article <19990424190901.d3a791...@spinner.netplex.com.au>,
>Peter Wemm wrote:
>> ...
>> So: things like:
>> device sio1 at isa? tty port "IO_COM2" tty irq 3
>> become:
>> device sio1 at isa? port IO_COM2 irq3
>
>What do you do about the "ppc" device? Formerl
On Mon, 10 May 1999, Peter Jeremy wrote:
> Peter Wemm wrote:
> >If you had old "vector xxxintr", it will now cause a syntax error rather than
> >a warning.
>
> What is the new method of specifying a non-standard interrupt
> function? I have some code (currently on 2.x, but I was hoping to be
>
Peter Wemm wrote:
> If you had old "tty", "bio", "net", "cam" flags, these are obsolete and will
> now cause a syntax error rather than a warning.
>
> If you had old "vector xxxintr", it will now cause a syntax error rather than
> a warning.
This is wrong, the warnings are just the same as before
>>If you had old "vector xxxintr", it will now cause a syntax error rather than
>>a warning.
>
>What is the new method of specifying a non-standard interrupt
>function? I have some code (currently on 2.x, but I was hoping to be
>able to move it) where I have different interrupt functions within th
Peter Wemm wrote:
>If you had old "vector xxxintr", it will now cause a syntax error rather than
>a warning.
What is the new method of specifying a non-standard interrupt
function? I have some code (currently on 2.x, but I was hoping to be
able to move it) where I have different interrupt functi
On Monday, 10 May 1999 at 10:04:40 +0800, Peter Wemm wrote:
> It should be noted that config(8) is destined to die sooner or later and
> almost certainly never make it to a release branch.
I suppose this makes it almost bearable. What's coming in its place?
Greg
--
See complete headers for addre
This is late, but a few hours ago, phk chopped out some old stuff from
config(8) and removed some backwards compatability warnings.
A summary of the changes:
If you had old "tty", "bio", "net", "cam" flags, these are obsolete and will
now cause a syntax error rather than a warning.
If you had ol
> In article <19990424190901.d3a791...@spinner.netplex.com.au>,
> Peter Wemm wrote:
> > This shouldn't cause much in the way of trouble, but it will complain
> > about old lint in your config files. That includes 'net/tty/bio/cam'
> > mask indicators, and 'vector xxxintr' as well as some of the
In article <19990424190901.d3a791...@spinner.netplex.com.au>,
Peter Wemm wrote:
> This shouldn't cause much in the way of trouble, but it will complain
> about old lint in your config files. That includes 'net/tty/bio/cam'
> mask indicators, and 'vector xxxintr' as well as some of the wierder
>
> - complain if a device is specified twice (eg: 2 x psm0)
Does this work for pseudo-devices also (i.e. can bin/9931 get closed)?
Bill
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Chris Costello wrote:
> On Sat, Apr 24, 1999, Peter Wemm wrote:
> > This shouldn't cause much in the way of trouble, but it will complain
> > about old lint in your config files. That includes 'net/tty/bio/cam'
> > mask indicators, and 'vector xxxintr' as well as some of the wierder
> > workaround
On Sat, Apr 24, 1999, Peter Wemm wrote:
> This shouldn't cause much in the way of trouble, but it will complain
> about old lint in your config files. That includes 'net/tty/bio/cam'
> mask indicators, and 'vector xxxintr' as well as some of the wierder
> workarounds for the poor 'options' parsing
This shouldn't cause much in the way of trouble, but it will complain
about old lint in your config files. That includes 'net/tty/bio/cam'
mask indicators, and 'vector xxxintr' as well as some of the wierder
workarounds for the poor 'options' parsing.
So: things like:
device sio1 at isa? tty port
21 matches
Mail list logo
