Age | Commit message (Collapse) | Author |
|
machine and restore the original behavior of RTM_ADD and RTM_DELETE
by always generating one message per locally configured address.
This time, make sure the local route is removed during an address change,
since at least pppoe(4) do some funky magics with wildcard addresses that
might corrupt the routing tree, as found by naddy@
Also do not add a local route if the specified address is 0.0.0.0, to
prevent a tree corruption, as found by guenther@.
Putting this in now so that it gets tested, claudio@ agrees. Please
contact me if you find any route-related regression caused by this
change.
|
|
on linux versions before 3.11 i915_pci_probe() doesn't match valleyview
unless i915_preliminary_hw_support is specified as a module parameter.
our drm code is currently based on linux 3.8, so it seems unlikely
that the valleyview support we have works.
|
|
wreaking havoc.
from miod@
|
|
|
|
I have found that some ports call boot(9) from machine-dependent code to
reboot system. These should be changed to either:
- Sending signal to init(8) to trigger it to shutdown system cleanly, like
acpi(4) does, in cases where found problems don't prevent system from working
immediately, or
- Just doing panic(9) if the situation is severely broken.
For now, just rewrite boot() to reboot(). Actual fixes follow.
Discussed with & OK from kettenis@
|
|
that drivers can check for this flag to know they have to stop doing
any hardware access and release their reference.
While here makes the ca_activate() function optional and propagates
DVACT_DEACTIVATE to the children of a device that do not implement this
interface like it is done during suspend/resume.
ok uebayasi@, deraadt@
|
|
|
|
is the right approach
- write into _THR instead of _RBR for cnputc() as per miod's suggestion
this doesn't fix the first character that gets eaten, but it's the right way
to move forward.
with pirofti@
|
|
It was never enabled and is apparently unfinished.
ok deraadt@ krw@ claudio@ kettenis@
|
|
spotted by Kent R. Spillner <kspillner acm org>
|
|
ok tedu
|
|
ok tedu
|
|
|
|
|
|
|
|
built-ins which aren't available on vax. (A similar diff for m88k is in the
pipeline as well)
|
|
|
|
no side effect
|
|
Function renames for consistency and readability. No functional change.
|
|
|
|
it when we hibernate.
ok mlarkin@, miod@, deraadt@
|
|
|
|
real impact since this descriptor is not used in the kernel. From NetBSD.
|
|
set the 'dying' flag of a device. Such handlers are useless now that
usbd_detach() already set this flag.
Even if the purpose of this flag is questionnable on OpenBSD because
DVACT_DEACTIVATE acts as a pre-detach event, this is just a first small
step towards the simplification of the autoconf(9) device states.
This cleaning is now possible thanks to the work of pirofti@ to convert
all the USB drivers to properly use usbd_is_dying().
Discussed many times with deraadt@
|
|
workq to taskq
ok jsing@
|
|
thanks to Fred Crowson (fred () crowsons ! net) who was able
to make sure his cd would still eject when the button was pushed,
and stsp@ who lent me his macppc laptop
|
|
that usbd_detach() should only be called by the thread doing USB
bus exploration to prevent attach/detach races.
|
|
by guenther@.
While here set the dying flag of the disconnected device so that most of
the DVACT_ACTIVATE handlers can go.
|
|
and let the stack take care of the checksums for reinjected outbound
packets.
Reinjected inbound packets will continue to have their checksums
calculated manually but we can now take advantage of in_proto_cksum_out
and in6_proto_cksum_out to streamline the way their checksums are done.
help from florian@ and henning@, feedback from naddy@
ok florian@ henning@
|
|
This is needed on some (specifically HP) machines to avoid _TMP reporting
a bogus temperature value (temperatures > 4,000 degC), which causes acpitz
to automatically shut down the machine because it thinks it's floating in
lava.
Also ensure that we can accept a temperature reading of 0 degC - we were
previously interpreting 0 degC as "bad temperature data" and not attaching
the thermal zone device. Some machines have ephemeral temperature sensors
that come and go (eg in docks) and we want to make sure we attach those
even if they report back 0 degC on initialization. Fixes some machines
with "failed to read _TMP" errors.
ok deraadt, tested and verified by a few folks on tech@ who were seeing
the thermal zone shutdown isue.
|
|
Some (not all) boot(9) implementations have ancient hacks which overrides if
(curproc == NULL). This was probably made in a hope to forcibly proceed
various clean-shutdown related code, including VFS shutdown. Let's clarify
that clean-shutdown needs process context; it is impossible to cleanly shutdown
VFS from within e.g. a panic in SPL_HIGH.
OK kettenis@
|
|
|
|
bluetooth support doesn't work and isn't going anywhere. the current
design is a dead end, and should not be the basis for any future support.
general consensus says to whack it so as to not mislead the unwary.
|
|
Still work in progress, but the interrupt routine can be enabled now.
I tried to match the structure of the other drivers as close as possible:
- add octhci_intr1() routine
- modify octhci_intr() to call octhci_intr1()
- schedule the actual work for the soft interrupt
- add octhci_root_intr_{transfer,start,abort} routines
- fill in the octhci_poll() routine
- use the same style for return directives
dmesg progress:
octhci0 at iobus0 irq 56: core version 2 pass 3.5
usb0 at octhci0: USB revision 2.0
uhub0 at usb0 " octHCI root hub" rev 2.00/1.00 addr 1
|
|
accept rtadvs on that interface. the global net.inet6.ip6.accept_rtadv
sysctl just doesn't cut it, even tho the spec wants that - but in their
little absurd world, a host just has one interface by definition anyway...
the sysctlgoes away.
lots of head scratching, brain cell elemination etc from bluhm benno stsp
florian, excitement from simon and todd, ok bluhm stsp benno florian
|
|
We return earlier if the interrupt is masked.
Discussed with and okay mpi@
|
|
on the 2nd of February 2011 in NetBSD.
http://marc.info/?l=netbsd-source-changes&m=129658899212732&w=2
http://marc.info/?l=netbsd-source-changes&m=129659095515558&w=2
http://marc.info/?l=netbsd-source-changes&m=129659157916514&w=2
http://marc.info/?l=netbsd-source-changes&m=129665962324372&w=2
http://marc.info/?l=netbsd-source-changes&m=129666033625342&w=2
http://marc.info/?l=netbsd-source-changes&m=129666052825545&w=2
http://marc.info/?l=netbsd-source-changes&m=129666922906480&w=2
http://marc.info/?l=netbsd-source-changes&m=129667725518082&w=2
|
|
pipex_session_req.
|
|
|
|
ok pelikan@
|
|
|
|
require the caller to do so. lteo needs that for divert soon, and is in line
with tcp/udp and the general approach that the rest of the stack should not
need to do anything regarding the cksums but setting the "needs it" flag.
ok lteo
|
|
ok guenther
|
|
can delete 2 dozen or so lines that check to see if we've queued
up a prefix addition multiple times.
ok stsp@
|
|
|
|
Now, for kernel to "reboot" (reboot, halt, or shutdown), MD boot(9) is called
in some places. This change introduces a new MI function reboot(9) which is
simply a wrapper to call MD boot(9).
OK kettenis@ deraadt@
|
|
and specifyig the wrong DWORD count. Moreover we should not evaluate _PDC
if _OSC is present. Might not be perfect yet, but what we had previously
was uterrly and totally wrong.
ok guenther@
|
|
ok guenther
|
|
state to the socket pcb. Add an additional assert to narrow down
the panics.
OK henning@
|
|
this let it wanter off writing segment descriptors off in memory
it didnt own, which led to some pretty awesome memory corruption.
if you had a network card with a small number of tx descriptors per
packet, a lot of memory, and a heavily fragmented packet (ie, ssh)
you were basically guaranteed a confusing panic.
ok miod@
|