summaryrefslogtreecommitdiffstats
path: root/sys (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix previous (1.258). It breaks if localX itself is an object reference.yasuoka2021-03-181-2/+5
| | | | | | found and test by Rafael Avila de Espindola ok kettenis
* When devices have claimed multiple report ids, only detach and sendjcs2021-03-171-17/+34
| | | | | | | | DVACT_DEACTIVATE to them once when walking sc_subdevs. Fixes a regression reported and tested by Edd Barrett. Input from and previous version ok anton.
* Make "ifconfig mpw0 -mplslabel" workkn2021-03-171-1/+4
| | | | | | | Code is there, noone ever used it, I guess. This makes ifconfig(8) documentation actually hold true. OK claudio
* Make iwx(4) attach to AX201 devices with PCI ID 0x34f0.stsp2021-03-171-1/+14
| | | | | | Requires Qu-c0-hr-b0-48 firmware which is available via fw_update(1). Patch by Fredrik Engberg
* regenstsp2021-03-172-2/+7
|
* Add another iwx(4) PCI device ID.stsp2021-03-171-1/+2
| | | | Based on a patch by Fredrik Engberg
* Make iwn(4) send block ack request frames with the firmware nodestsp2021-03-171-2/+5
| | | | | | | | | | | which represents the AP, rather than the firmware's broadcast node. Fixes a problem where firmware would generate bogus block ack requests with a wrong starting sequence number, shifting the receiver's block ack window out of sync with that of the firmware. Traffic would stall until enough frames were sent to wrap sequence numbers of the block ack window. ok chris@ kmos@
* Use correct rdomain when adding/deleting routeskn2021-03-172-7/+7
| | | | | | | | | | | | | | | | mpip(4) always adds and deletes routes in rdomain 0 regardless of the `tunneldomain', i.e. the `sc_rdomain' value. mpw(4) adds routes with the specified rdomain but always deletes them in rdomain 0. mpe(4) consistently uses the softc's rdomain which is tracked consistently across the various ioctls -- no fix needed. Found while reading the code and testing ifconfig(8)'s "tunneldomain" in order to document MPLS ioctls. OK claudio
* Fix bit position of ORPHAN in PS_BITS.visa2021-03-171-2/+2
|
* Add missing memory clobbers to "data" barriers.kettenis2021-03-173-11/+11
|
* Hide kernel internals from userland by wrapping more bits in _KERNEL blocks.claudio2021-03-171-1/+6
| | | | | Especially the includes of net/rtable.h and sys/queue.h are problematic. OK florian@
* Always use an allocated buffer for {Read,Write}Blocks() to makeyasuoka2021-03-172-80/+34
| | | | | | | | | efid_io() simpler. Also fixes the problem on some machines when boot from CD-ROM. It happened because the previous version passed unaligned pointers to the functions even if it is restricted by the IoAlign property of the media. idea from kettenis, work with asou ok kettenis
* Node without a "status" property should be considered enabled as well.kettenis2021-03-161-3/+3
| | | | Same change made to arm64 a week ago.
* Make sure that switching the console from serial to framebuffer workskettenis2021-03-162-22/+25
| | | | | | for framebuffer nodes under / and /chosen. Same change made to arm64 last month.
* acpi_intr_disestablish() should free its own cookie.patrick2021-03-161-1/+2
| | | | ok kettenis@
* Bump MAXTSIZ to 256MB on i386.kurt2021-03-161-2/+2
| | | | okay deraadt@
* handle theoretical case of sigfillsz not being pow2-sized on somederaadt2021-03-161-4/+8
| | | | | architecture. from miod
* Fix some correctness issues in the lowelevel kernel bringup code.kettenis2021-03-163-5/+20
| | | | | | | | | | | | | | - Make sure we install a dummy page table in TTBR0_EL1 before we change the size of the VA space in TCR_EL1. - Flush the TLB after updating TCR_EL1. - Flush TLB after installing the real kernel page table in TTBR1_EL1. - Add some barriers around TLB flushes to make it consistent with other places where we do TLB flushes. ok drahn@, patrick@
* Add code to acpiiort(4) to look up named components in the IORT andpatrick2021-03-153-4/+80
| | | | | | | map them. This makes ACPI's call to acpi_iommu_device_map() do work through acpiiort(4). ok kettenis@
* Change API of acpiiort(4). It was written as a hook before, taking thepatrick2021-03-157-33/+23
| | | | | | | | | | PCI attach args and replacing the DMA tag inside. Our other IOMMU API though takes a DMA tag and returns the old one or a new one. To have acpiiort(4) integrate better with non-PCI ACPI devices, change the API so that it is more similar to the other API. This also makes the code easier to understand. ok kettenis@
* Add acpi_iommu_device_map(), which replaces the DMA tag with one thatpatrick2021-03-155-5/+27
| | | | | | | | | is blessed with IOMMU magic, if available. This is mainly for arm64, since on amd64 and i386 the IOMMU only captures PCIe devices, as far as I know, which uses the pci_probe_device_hook(). This though is for non-PCI devices attached through ACPI. ok kettenis@
* Add the IORT structure for named components. These give us the stream idspatrick2021-03-151-5/+13
| | | | | | | used towards an smmu(4) for non-PCI devices. The references are provided as ASCII printable paths. ok kettenis@
* Clear AUTOCONF6TEMP flag when we detach inet6.florian2021-03-151-3/+3
|
* Don't put an extern variable (ppc_kvm_stolen) into vmparam.h, other instancesderaadt2021-03-152-6/+3
| | | | of this file are only doing cpp #define
* msi-map-mask is a pasto and should be iommu-map-mask.patrick2021-03-141-2/+2
| | | | | From Jared McNeill at NetBSD ok kettenis@
* regenjan2021-03-142-2/+7
|
* Add ID for Intel SSD DCjan2021-03-141-1/+2
| | | | ok jsg@
* Advertise 30-bit color support.kettenis2021-03-131-2/+5
| | | | ok matthieu@, jsg@
* We can use memory marked as EfiBootServicesCode or EfiBootServicesDatakettenis2021-03-131-3/+6
| | | | | | as well. ok drahn@, kn@
* Add WSDISPLAYIO_DEPTH_30 in order to support 30-bit color support.kettenis2021-03-121-1/+2
| | | | ok jsg@
* In ipw(4), ensure that net80211 is in ASSOC state while we are expectingstsp2021-03-121-1/+7
| | | | | | | | an assoc response from the AP during the association sequence. Otherwise net80211 would ignore the auth response, resulting in a state mismatch between firmware and net80211. A symptom of this was that WPA didn't work. Problem reported and fix tested by Ricardo Mottola
* Use RA instead of MiRA in iwn(4).stsp2021-03-122-191/+129
| | | | | | | Tested by: iwn 6200: stsp iwn 6205: cwen, Jeremy O'Brien iwn 6300: okan
* Use RA instead of MiRA in iwm(4).stsp2021-03-122-49/+66
| | | | | | | | | | | Tested by: iwm 7260: florian iwm 7265: TronDD, Aaron Miller, stsp iwm 8260: bket iwm 8265: matthieu, tracey, naddy, Dave Voutila, jcs, Mathieu Kerjouan, Matthias Schmidt, stsp iwm 9260: matthieu, phessler, Darren VanBuren iwm 9560: Uwe Werler
* Add RA, a new 11n Tx rate adaptation module for net80211.stsp2021-03-123-1/+785
| | | | | | | | | | | | | | | | | | | | | | | | | Written by Christian Ehrhardt and myself, based on ieee80211_mira.c but with significant changes. The main difference is that RA does not attempt to precisely measure actual throughput but simply deducts a loss percentage from the theoretical throughput which can be achieved by a given MCS. Unlike MiRa, RA does not use timeouts to trigger probing. Probing is triggered only by changes in measured throughput. Unlike MiRA, RA doesn't care whether a frame was part of an A-MPDU. RA simply collects statistics for individual subframes. This makes reporting very easy for drivers and seems to work well enough in practice. Another difference is that drivers can report multi-rate retries properly via ieee80211_ra_add_stats_ht(mcs, total, fail) which can be called several times before ieee80211_ra_choose() selects a new Tx rate. There is no reason any issues could not be fixed in ieee8011_mira.c but I felt it was a good moment to burn the house down and start over. And since this code diverges from how MiRA is described in the research paper applying the "MiRA" label becomes inappropriate.
* Update Spleen kernel fonts to version 1.9.0, bringing the followingfcambus2021-03-122-27/+1691
| | | | | | | improvements: - Enlarge vertical line for consistency with other small sizes (5x8 version) - Add full support for the Latin-1 Supplement Unicode block (6x12 version)
* spellingjsg2021-03-1211-27/+27
| | | | ok mpi@
* spellingjsg2021-03-1212-27/+27
|
* Kill SINGLE_PTRACE and use SINGLE_SUSPEND which has almost the same semanticmpi2021-03-124-17/+12
| | | | | | | | single_thread_set() is modified to explicitly indicated when waiting until sibling threads are parked is required. This is obviously not required if a traced thread is switching away from a CPU after handling a STOP signal. ok claudio@
* When RFC 8981 obsoleted RFC 4941 the terminology changed fromflorian2021-03-111-2/+2
| | | | | | | | | | | | | | | | | | | "privacy extensions" to "temporary address extensions" Change ifconfig(8) to output temporary after temporary addresses and add "temporary" option which is an alias for autoconfprivacy for now. Also make AUTOCONF6TEMP a positiv flag that is set by default. Previously the negative flag "INET6_NOPRIVACY" was set when privacy addresses were disabled. This makes the flags output less ugly and will allow us to disable autoconf addresses while having temporary addresses enabled in the future. More work is needed in slaacd. input benno, jmc, deraadt previous verison OK benno OK jmc, kn
* There is no need to try to attach IPv6 to an interface when theflorian2021-03-111-2/+3
| | | | | | | | AUTOCONF6 flag is already set. This is likely a leftover from when we sent router solicitations from the kernel. This was a way to trigger sending a solicitation from userland. OK kn
* If the AUTOCONF4 or AUTOCONF6 flags get enabled, force the interface up.deraadt2021-03-111-23/+34
| | | | ok florian claudio
* spellingjsg2021-03-1117-42/+42
|
* spellingjsg2021-03-11140-331/+331
|
* Add SMP support.kettenis2021-03-111-14/+99
| | | | ok patrick@
* Make sure to skip attaching disabled I2C devices. This can happen onpatrick2021-03-115-10/+35
| | | | | | hardware which include a common parent block in their device trees and only enable the components that were actually implemented, as seen on e.g. the NanoPi R4S.
* Make sure to skip attaching disabled I2C devices. This can happen onpatrick2021-03-111-2/+7
| | | | | | | | hardware which include a common parent block in their device trees and only enable the components that were actually implemented, as seen on e.g. the NanoPi R4S. ok kettenis@
* grow media a littlederaadt2021-03-111-2/+2
|
* Handle named references in acpi_getdevlist(). Fixes a regression in acpitztobhe2021-03-101-1/+11
| | | | | | caused by the reference handling change from December. ok kettenis@ patrick@
* Our ACPI namerefs are pointers to the byte structures for ACPI names.patrick2021-03-106-15/+20
| | | | | | | | | | | | These are not in a printable format, hence printing them as string is wrong. Additionally, aml_searchrel()/aml_searchname() expect the name to be passed in a printable format as well. Passing a nameref can lead to an out-of-bounds read, and the comparison can fail. Hence make sure that namerefs are passed to aml_getname() first, which returns printable strings. Note that aml_getname() uses a static buffer, so there are a few restrictions how the string can be used. ok kettenis@
* The ktrace record for recvmsg/recvfrom could contain extract bits inderaadt2021-03-101-3/+10
| | | | | msg_flags (they get set internally). Correct the record to only contain what the caller requested.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.