Age | Commit message (Collapse) | Author |
|
waste of 128KB of kvm.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
diff from Sepherosa Ziehau (DragonFly); The firmware TIM element template
was initialized wrong.
Though, our ieee80211_alloc_beacon() routine calculates it's own TIM
element, which now results in having two TIMs in an acx(4) beacon.
Would it be an idea to introduce a ieee80211_alloc_beacon() flag to
turn the TIM element off? Because fiddling out the TIM element in the
driver for cases in which the firmware calculates its own TIM is
a bit ugly ...
ok claudio@
|
|
|
|
(s6_addr16[1] filled)
ok dhartmei
|
|
reuses IPv4 signature file (assuming that TCP code is shared among IPv4/v6).
mcbride ok.
|
|
errors to userland: make all cpu_setperf functions return void.
Tested by many, ok gwk@
|
|
|
|
in a much more recent Marvell Linux sk98lin driver.
From brad@.
ok me and kettenis (via mglocker)
|
|
|
|
|
|
|
|
|
|
While there, fix a typo.
ok gwk
|
|
- change the defs of LHS, RHS, DST and DST2 to be AML_*.
Noted by Marco S Hyman on misc@, these allow ACPI to be compiled into
RAMDISK kernels. Suggestion for AML_ rename (to avoid name clash with
TIMEZONE's DST, which was noted by someone else a while ago, but I
forget who) from jordan@.
ok marco@, jordan@
|
|
ok otto@
|
|
hardware checksum could be mangled with 28 byte or less IP packets.
>From tsutsui@NetBSD
Tested by otto@ brad@ and Han Boetes <han at mijncomputer dot nl>
Tested by maja@ with the 8139C+ chipset
Tested on amd64/i386/sparc64
ok mglocker@ brad@ otto@
|
|
-- bus_space(9) does the endian switch for us -- and finaly change one
letoh32() to letoh16(). The last one being by far the nastiest one.
OK mglocker@
|
|
|
|
using the new NO_CCB result. Currently a no-op since no driver produces
that result.
ok dlg@ marco@ deraadt@
|
|
drop it. im guessing at some point we'll want to use each port, knowing
where they are can help.
|
|
|
|
ahci_port structs for it.
|
|
ccb lists. this is missing handling of the dmamem each port needs to
manage, but that can wait till i figure out how it fits together. insane
stuff.
|
|
|
|
|
|
and ahci_pwrite. these will use an io handle into a window of the
controllers register space that can be created with bus_space_subregion,
and which is stored in the ahci_port struct.
|
|
per port rather than as a big list for the whole controller. the softc
has an array of pointers to a struct that manages all the shizz relevant to
a particular port. when we map the controllers ports, we'll allocate these
as needed.
if the port isnt implemented, we leave its pointer in the softc null and
use that to decide if a drive might be there or not, rather than lookup up
the PI register all the time. a comparison has to null has to be cheaper
than doing bit operations, surely.
|
|
|
|
introduced by myself at h2k6, thanks mickey@ and toby@ for turning me in
the direction of a corrupt PCB.
|
|
deraadt@
|
|
P2P is commonly used in relation to peer to peer networks, PTP is used
in various protocols for layer 2 point to point links (ie., full
duplex ethernet links).
note that the newly added brconfig commands [-]p2p and [-]autop2p will
change to [-]ptp and [-]autoptp.
suggested by Andrew Thompson (thompsa@freebsd.org)
|
|
|
|
|
|
this is a tiny ABI change, but it is better for a handfull of reasons
|
|
inetrrupt routing information.
ok deraadt@
|
|
|
|
than fall through to the bits that do cleanup when an error occurs.
|
|
to address. instead make them simply offsets from the start of a ports
register space, which is something we can easily set up with
bus_space_subregion. this should make the code a lot easier to read later
on.
|
|
mechanism to figure out if a port is usable or not later on.
|
|
this stuff isnt endearing me to ata at all, and apparently ahci is a good
ata controller. the command path looks way more complicated than it needs
to be (or maybe i am used to really good scsi controllers, i dont know). a
lot of the terminology seems annoyingly different just for the sake of
being different. i mean, what is the advantage of calling a scatter gather
lement a "physical region descriptor table"? noone else calls it that.
there's a lot of weird stuff in here.
blah.
|
|
arc, which got it from mpi, which got it from ami. grange is right, we
should look at pushing it back up into the bus_dma api somewhere.
|
|
|
|
|
|
|