| Age | Commit message (Collapse) | Author |
|---|
|
signal sensor that reflects the status of the receiver.
tested by and ok ckuethe
|
|
ifdef netbsd block in drm code, but oga@ says he'll remove
it soon...
OK art@, oga@;
|
|
|
|
before returning rt_tables[id][af2rtafidx[af]. when you created tables
and left a hole (0 and 2 exist, 1 does not) it is possible to hit that
case. issue found & ok claudio
|
|
when it is in fact only used to delete the state key when the number of
attached states (in a tailq) drops to zero, we can as well test for the
queue beeing empty.
this is a leftover from some early version that did things differently.
ok ryan
|
|
set the flags and quirks for a device. Should fix weird issues where
the device after an ATAPI device gets marked as ATAPI. First reported
on misc@ by Daniel Wade, who also provided some useful testing.
ok dlg@
|
|
on umass interfaces, and add Huawei E220.
From rivo nurges <rix@estpak.ee>.
And add another device while here.
|
|
|
|
Reported on misc@ by Denis Doroshenko <denis.doroshenko@gmail.com>
|
|
tested by maja@
|
|
|
|
contiguous 64MB DIMMs in a single 128MB one) are not reported as memory at
offset zero, but actually as duplicates of the first entry (which always
matches real memory).
If the DIMMs are set up in decreasing sizes, as recommanded by SGI, the
first entry will be configured at offset zero, so the existing code would
run fine.
If, however, you order your DIMMs in a different order, the first entry
might not be at offset zero, so the kernel will mess up its memory
information, which will cause random effects from simply misreported memory
sizes, to the inability to boot.
Fix this by strengthening the check for an empty bank.
Problem reported by Jason Bergstrom (bergie, bergie dot net), analysis
and fix by me.
|
|
tested by maja@
|
|
|
|
ok miod@
|
|
|
|
one thing of note, fifofs changes in that its bmap now
sets the runp too 0, but that was an oversight in the
old code.
ok art@
|
|
|
|
|
|
spotted by drahn
|
|
on drugs; ok kettenis@
|
|
|
|
filedesc struct and associated fdcopy operation on kernel thread
creation. Instead, kernel threads share and bump reference count
on proc0's filedesc.
ok thib@, "definitely makes sense" art@
|
|
Parts from NetBSD;
OK blambert@;
tested by johan@, sthen@ and a few others.
|
|
|
|
are done with network byte ordering now. OK norby@
|
|
get a timestamp of when the datagram was accepted (by udp(4), for
example) rather than having to take a timestamp with gettimeofday(2)
when recv(2) returns - possibly several hundreds of microseconds later.
May be of use to those interested in precision network timing schemes
or QoS for media applications. Tested on alpha, amd64, i386 and sparc64.
manpage suggestions from jmc, ok deraadt
|
|
|
|
|
|
sigexit the process in this case.
|
|
|
|
flavours. Add another frame buffer ID to recognize it, so that it gets
skipped correctly.
I am quite sure it has an SGC PROM in addition to the DIO PROM, but I don't
have the hardware to check...
|
|
|
|
|
|
ok drahn@
|
|
|
|
|
|
|
|
|
|
|
|
ok jakemsr@
|
|
|
|
|
|
works, even if the boot loader is configured to use serial console.
after the changes jsing and i made, the initial probe of the serial port
was failing since the default base addres for the port is invalid. cos of
that the kernel would only ever consider the glass console for use. this
fixes it by reprobing the serial port if we get any config for it from the
boot loader.
advice on aesthetics from miod@
advice and ok from kettenis@
|
|
Discussed with claudio@ dlg@ laurent@
Remember to enable MPLS vith sysctl(8).
sysctl -w net.mpls.enable=1
ok claudio@ dlg@ laurent@
|
|
If it exists assume that the boot loader has provided a pointer to the end
of the symbol table. If it does not exist fall back to the previous
behaviour and expect that pointers to the symbol table have been provided
directly after the kernel.
ok miod@
|
|
NetBSD code it was based on did/does, now we have it.
This makes detecting sis 96x work properly without having to
do silly things like adding host bridges in the list. Of
course we wouldn't be in this mess in the first place if sis
designed their chips properly instead of reusing the same
pci id.
Add 964/965 devices while here.
Tested by todd@ on a machine with 965.
|
|
|
|
ok deraadt
|
|
|
