Implementation of the modify_ldt syscall. Use the sysarch() interface to do
the actual work. When USER_LDT is not defined for a kernel, sysarch returns
EOPNOTSUPP. Display a message in that case and return ENOSYS to userland.
Some reorganization of sysarch() interface:
1. Move definitions of struct i386_*_args to the header file sysarch.h,
since they are part of the sysarch API. struct i386_get_ldt_args and
i386_set_ldt_args were identical, therefore make them into one
struct i386_ldt_args. Libc should use these definitions as well.
2. Return a more sensible EOPNOTSUPP for unknown operations.
- Added new macros ED_P1_MAR(i) and ED_P1_PAR(i) that replace
`ED_P1_MAR + i' and `ED_P1_PAR + i', respectively.
- convert ED_PC_RESET and ED_PC_MISC into relative offset from
ED_PC_ASIC_OFFSET (those macros are not used in current source).
Fix the root cause of the fts buffer overflow. This is a temporary
patch to stop the core dumps while others come up with a better
reviewed patch which may also fix other problems. We do illegal
pointer arithmetic, but it should be OK since FreeBSD only supports
machines with flat address spaces.
Oh crud, did I ever screw the pooch! Rather than sync this with -stable,
I backed-out the changes in -current and didn't touch stable at all (I
thought I had my patch order reversed, not what actually happened).
AIEEE! I can't even blame the crack for this one since I broke my
crack pipe a few weeks ago. I think sleep deprivation gets the blame
for this one.
Medal for noticing this one goes to: Jim Bloom <bloom@acm.org>
This is part of an untested set of changes to the ed driver to support
the new PnP code. Since the bulk of the driver changes are not being
committed at this time, it will not affect the driver. The code is being
committed early to allow others synchronise changes.
This represents essentially a complete rewrite of the ISA PnP code. The
new system is integrated with the ISA bus code more cleanly and allows
the future addition of more enumerators such as PnPBIOS and ACPI.
This commit also enables the new pcm driver since it is somewhat tied to
the new PnP code.
Re-arrange things in the attach routines of the 3Com and RealTek PHY
drivers so that we don't clobber things or leave them uninitialized
if we abort due a failure.
peter [Wed, 1 Sep 1999 14:53:16 +0000 (14:53 +0000)]
Sigh. Serves me right for testing against a modified tree (dfr's pnp
changes). Doug changed these variables. This should fix the isa_compat.c
breakage that phk reported. (Sorry!)
* Fix a stack of warnings.
* Make it possible to type a filename to boot1 so that it is possible to
recover from fatally broken versions of /boot/loader.
* Make a start at a CD boot program (not yet functional).
peter [Wed, 1 Sep 1999 05:14:57 +0000 (05:14 +0000)]
Add a missing dependency for make_hash which could make various forms of
make -jN fail. This fixes the present problem only, not the larger one
of when those internal tools are built and the cross-compiling etc.
MFC: Catch 3.2-stable sysinstall up to 4.0-current level functionality,
bringing in DHCP support. The only thing I left out were Poul-Henning's
newfs changes since I'm not sure if he's brought the rest of that support
into -stable yet. If it turns out that this is the case, I'll MFC those
changes too.
say hello to newpcm. it is not yet enabled, requiring new pnp code from dfr
to compile successfully. further details will be provided in the commit
enabling newpcm.
Just when I thought it was safe. In the original 3c905-TX NICs, the
external NatSemi PHY chip was programmed to respond to MII address 24.
In the 3c905B ASICs, the transceiver is internal but it's still mapped
to MII address 24. But *some* 3Com 3c905B ASIC revisions map the
transceiver control registers to *all* MII addresses (0 through 31).
The miibus code probes for PHYs at all MII addresses and because of
this unusual behavior, it will attempt to map the same PHY registers
several times over, which doesn't work.
Naturally, the 3c905B NIC that I tested happened not to exhibit this
behavior.
The fix is to tweak xl_miibus_readreg() and xl_miibus_writereg()
to only respond when attempting to read from MII address 24. This
is safe to do since the 3Com documentation indicates that the PHY
and/or internal transceiver will always be mapped to address 24,
and there are no 3Com XL NICs with more than one PHY.
jdp [Tue, 31 Aug 1999 17:26:21 +0000 (17:26 +0000)]
Adjust the examples to reflect the new "src-sys-crypto" collection.
Add back "src-eBones" to "cvs-supfile" and "secure-cvs-supfile".
Even though the eBones tree is disused, it still has files in the
repository. People fetching the repository might want them.
imp [Tue, 31 Aug 1999 17:01:34 +0000 (17:01 +0000)]
Add blurb Jonathan Lemmon provided about the new TCP timer values. I
didn't document the couple day window when the units were in terms of
ticks rather than ms.
Also add note about libreadline major version retrograde motion.
tegge [Tue, 31 Aug 1999 14:18:32 +0000 (14:18 +0000)]
If integration of a buffer into a cluster write operation fails, release
the buffer instead of creating a future deadlock.
PR: 12800
Submitted by: dillon
roger [Tue, 31 Aug 1999 10:29:42 +0000 (10:29 +0000)]
Update to driver release 1.71
New Features:
Greatly improved VBI capture support. (mainly for the AleVT port)
Supports select() on /dev/vbi
Improved RISC program for RGB+VBI capture to capture both evenodd
VBI data even when only capturing even only (or odd only) video
Based on code from Juha Nurmela <Juha.Nurmela@quicknet.inet.fi>
Support for Hauppauge 627 and Temic 4006
Submitted by: Maurice Castro <maurice@atum.castro.aus.net>
markm [Tue, 31 Aug 1999 08:55:39 +0000 (08:55 +0000)]
FreeBSD District court of Appeals - TN3270 vs Ports
Judge: TN3270, you are charged with being superfluous to
requirement, and have been found guilty.
Defence, do you have any final words?
Defence lawyer: Yes,..
*!BLAM!*
Judge: Contempt of court!! That blood is disgusting! Sergeant?
Sergeant: Sah!?
Judge: Get that mess out of here.
Sergeant: Sah!!
Judge: Anyone else have anything else to say?
...
Judge: Executioner!
Executioner: My lord?
Judge: Carry out the sentence, forthwith!
Executioner: As my lord wishes...
*!BLAM!* *!BLAM!* *!BLAM!*
Judge: Any more matters for the court today?
...