Fix a long-standing bug where I used a 'break;' instead of a 'continue;';
you had to have multiple ISA boards in non-PnP mode with an 'unknown' board
with a lower MAC address to find this one. Since I have 4 3c5x9 boards
in my test box I was somewhat confused when this happened. :)
Make the messages printed by ep_isa_identify() a little more consistent;
we'll only see them in verbose boot mode but it makes me feel better if
they look nice.
Also, while I'm here, add a mechanism to catch unknown board IDs that
are likely to be 3c509s and allow them to be attached.
PR: kern/16304
Submitted by: Kelly Yancey <kbyanc@posi.net>
the receive code so that it correctly chains receive descriptors together
and handles the case that only a part of a packet is done at the time
we get here.
the string "FreeBSD". Use the .Fx macro instead. Also did some
minor re-wording/formatting to work around a deficiency with
the .Fx macro when it comes to puncuation characters other than
periods and commas.
tells that tun unit to prepend a four byte address family to packets
queued for tunread() and to expect a four byte address family at the
front of data received by tunwrite().
We queue any protocol received from the interface for tunread(), but
only accept INET, INET6, IPX and NETATALK from tunwrite(). There is
support for Xerox's NS stuff, but AFAICT config(8) doesn't ever
define NS.
Oh why did I select a first project that needed to touch release/Makefile..
The fact that my release-building Alpha panics on me does not help either :(
From "Alexander N. Kabaev" <ak03@gte.com>:
The problem is that default builtin_setjmp implementation does not restore
any registers except for stack pointers when doing nonlocal jump. This
means, that every platform, that needs to store/restore some other state
between jumps, has to provide appropriate definitions for
builtin_setjmp_setup and builtin_setjmp_receiver RTL expansions.
Every plaftorm which needs to do some additional processing at setjmp
receive point, such as restoring additional information previously saved by
builtin_setjmp_setup, can provide definition for builtin_setjmp_receiver
RTL expansion. [That is what the previous commit does.] The i386 code
compiled with -fpic option requires the value of the PIC register (EBX) to
be restored in order to function properly. One should not provide
expansion for builtin_setjmp_setup because GCC documentation explicitly
states that values should be recalculated if possibe, rather than stored in
setjmp buffer and proper value for EBX can easlity be determined from the
current EIP contents.
