| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
would only match a leap year every 400 years. The parseDWM code first
showed up in April 2000, so the first time this bug would cause any
confusion is in Feb 2004.
MFC after: 18 days
|
| |
|
|
|
|
| |
appropriate. This should be the last change to make ia64 work.
|
|
|
|
| |
Rename a few structure elements.
|
| |
|
|
|
|
| |
required fields, no matter what their value.
|
|
|
|
| |
Courtesy of: rwatson's chart presentation
|
|
|
|
|
|
|
| |
only code-change is to add a "next_time" parameter to both routines (and
that is not used yet). A later update will make "next_time" more useful.
MFC after: 20 days
|
|
|
|
|
|
| |
that the last change should have read: exim_enable="YES" in the changes listing.
Discussed with: ceri
|
|
|
|
| |
Courtesy of: USENIX hall track
|
|
|
|
|
|
|
|
| |
but has invalid 64 bit pointers for FACS and DSDT.
o Finish work to print all of the FADT and FACS.
o Resort the comment generating functions. Submitted by: marcel
Courtesy of: BSDcon back wall
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add 'enable_exim="YES"' to rc.conf(5)
- Use the default exim configuration file from the port
- When using sendmail, disable some more scripts that use sendmail specific
parameters
- Have sysinstall tweak mailer.conf(5) substitution
- Use 'N' flag for newsyslog(8)
Submitted by: Oliver Eikemeier <eikemeier@fillmore-labs.com>
Reviewed by: sheldonh, simon
Tested by: myself (trhodes) and submitter
|
| |
|
|
|
|
|
|
|
| |
is already passed in, instead of having the caller copy values from
that struct into additional parameters.
MFC after: 22 days
|
|
|
|
|
|
| |
gcc 3.3.x and -Wshadow. Just renames 'log' variables to be 'logname'.
MFC after: 22 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
written by Stuart Walsh and Duncan Barclay (with some kibbitzing by
me). I'm checking it in on Stuart's behalf.
The BCM4401 is built into several x86 laptop and desktop systems. For the
moment, I have only enabled it in the x86 kernel config because although
it's a PCI device, I haven't heard of any standalone NICs that use it. If
somebody knows of one, we can easily add it to the other arches.
This driver uses register/structure data gleaned from the Linux
driver released by Broadcom, but does not contain any of the code
from the Linux driver itself. It uses busdma.
|
|
|
|
| |
Submitted by: marcel
|
|
|
|
|
|
|
| |
Update FADT for new fields including pm_profile, pstate_cnt, and cst_cnt.
Add acpi_print_gas() for printing various address formats.
Print FACS contents.
Remove unused code.
|
|
|
|
| |
MFC after: 23 days
|
|
|
|
|
|
|
|
| |
debugging options. Initial option is '-D TN=<time>', which can be
used to see how newsyslog would work if run at the specified time.
(time format is ISO 8601, since that is already supported).
MFC after: 23 days
|
|
|
|
|
|
|
| |
negative values. Mainly done to sync this routine with OpenBSD.
Obtained from: OpenBSD
MFC after: 23 days
|
|
|
|
| |
MFC after: 23 days
|
|
|
|
|
|
| |
for invalid times, and have the caller print the error message.
MFC after: 23 days
|
|
|
|
|
|
| |
is changed. (that will come in later updates).
MFC after: 23 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rl(4) driver and put it in a new re(4) driver. The re(4) driver shares
the if_rlreg.h file with rl(4) but is a separate module. (Ultimately
I may change this. For now, it's convenient.)
rl(4) has been modified so that it will never attach to an 8139C+
chip, leaving it to re(4) instead. Only re(4) has the PCI IDs to
match the 8169/8169S/8110S gigE chips. if_re.c contains the same
basic code that was originally bolted onto if_rl.c, with the
following updates:
- Added support for jumbo frames. Currently, there seems to be
a limit of approximately 6200 bytes for jumbo frames on transmit.
(This was determined via experimentation.) The 8169S/8110S chips
apparently are limited to 7.5K frames on transmit. This may require
some more work, though the framework to handle jumbo frames on RX
is in place: the re_rxeof() routine will gather up frames than span
multiple 2K clusters into a single mbuf list.
- Fixed bug in re_txeof(): if we reap some of the TX buffers,
but there are still some pending, re-arm the timer before exiting
re_txeof() so that another timeout interrupt will be generated, just
in case re_start() doesn't do it for us.
- Handle the 'link state changed' interrupt
- Fix a detach bug. If re(4) is loaded as a module, and you do
tcpdump -i re0, then you do 'kldunload if_re,' the system will
panic after a few seconds. This happens because ether_ifdetach()
ends up calling the BPF detach code, which notices the interface
is in promiscuous mode and tries to switch promisc mode off while
detaching the BPF listner. This ultimately results in a call
to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init()
to handle the IFF_PROMISC flag change. Unfortunately, calling re_init()
here turns the chip back on and restarts the 1-second timeout loop
that drives re_tick(). By the time the timeout fires, if_re.ko
has been unloaded, which results in a call to invalid code and
blows up the system.
To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(),
which stops the ioctl routine from trying to reset the chip.
- Modified comments in re_rxeof() relating to the difference in
RX descriptor status bit layout between the 8139C+ and the gigE
chips. The layout is different because the frame length field
was expanded from 12 bits to 13, and they got rid of one of the
status bits to make room.
- Add diagnostic code (re_diag()) to test for the case where a user
has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some
NICs have the REQ64# and ACK64# lines connected even though the
board is 32-bit only (in this case, they should be pulled high).
This fools the chip into doing 64-bit DMA transfers even though
there is no 64-bit data path. To detect this, re_diag() puts the
chip into digital loopback mode and sets the receiver to promiscuous
mode, then initiates a single 64-byte packet transmission. The
frame is echoed back to the host, and if the frame contents are
intact, we know DMA is working correctly, otherwise we complain
loudly on the console and abort the device attach. (At the moment,
I don't know of any way to work around the problem other than
physically modifying the board, so until/unless I can think of a
software workaround, this will have do to.)
- Created re(4) man page
- Modified rlphy.c to allow re(4) to attach as well as rl(4).
Note that this code works for the sample 8169/Marvell 88E1000 NIC
that I have, but probably won't work for the 8169S/8110S chips.
RealTek has sent me some sample NICs, but they haven't arrived yet.
I will probably need to add an rlgphy driver to handle the on-board
PHY in the 8169S/8110S (it needs special DSP initialization).
|
| |
|
| |
|
|
|
|
| |
to be a lot cleaner.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Craig Rodrigues <rodrigc@crodrigues.org>
Not objected by: -current
|
|
|
|
|
|
|
| |
NO_TOOLCHAIN skips Compilers and Binutils
NO_USB skips USB stuff
NO_VINUM skips Vinum stuff
NO_ACPI skips ACPI stuff
|
|
|
|
|
| |
too, but I don't have time to test it, and I'm not sure it will help
much.
|
|
|
|
|
| |
of the original userland ACPI implementation. amldb is still available from
the devel/acpicatools port.
|
|
|
|
|
| |
Also clean up the output of dumped tables. Update the man page for the
new usage. Make WARNS=6 clean.
|
|
|
|
| |
depend on existing NOATM and NOINET6 conditionals.
|
|
|
|
|
|
|
|
| |
in the description of the pkg_create -i command-line option.
PR: 55477
Submitted by: Eric van Gyzen <vangyzen@stat.duke.edu>
MFC after: 5 weeks
|
|
|
|
|
|
|
|
|
|
| |
when reading/writing spool files. I intend to do a more elaborate
version, but I want to get this much in before 4.9-release. As written,
this results in no change to the object code.
Submitted by: John-Mark Gurney
Reviewed by: /sbin/md5
MFC after: 4 days
|
|
|
|
|
| |
laptops are "PC Cards" and uses said term consistantly. Allow my
foolish hobgoblins to get the better of me and become consistant.
|
|
|
|
|
|
|
|
|
| |
to ignore all PC Card devices.
Submitted by: Anders Nordby
PR: bin/37650
MFC After: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Fix up TX speed changes.
- Make mpi-350 cards sort-of work with new firmware. It RXs okay but TXs
only work for about 14 packets then fails to get an interrupt. The
TX watchdog fires. It has been reported that my hack for now doesn't
break cards with the older firmware. It appears my card has lost
the ability to RX or TX at all but other peoples cards work. I assume
it got damaged in tansport.
MFC: 1 week.
|
|
|
|
|
|
| |
installing XFree86 (version 3.3.6 and before).
Reviewed by: jhb
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
was mistakenly calling the standard isnumber() function to find out if
the given 'user' or 'group' were all numeric. This meant that only the
first character of the fields were actually checked, so a username of
(say) '3com' would look like a number, and thus get mapped to uid=3 (bin)
instead of username=3com.
This bug was introduced back in freebsd's v1.1. That initial import
almost matches netbsd's v1.9, except that an internal isnumber()
routine was removed in favor of the standard library version. The thing
is, that internal routine was checking the entire string, and not just
the first digit. In OpenBSD, isnumber() was eventually renamed to
isnumberstr() to make the distinction more obvious, and I'm going to
follow that lead.
I believe this also happens to remove the last references to isnumber()
in the entire freebsd base system.
Obtained from: OpenBSD, by a long circuitous route
MFC after: 5 days
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|