��,219924
76
184
415
99
248
227
221
188
492
350
167
167
265
243
280
132
441
528
202
391
216
391
164
186
103
138
185
381
161
453
453
184
155
174
263
122
258
279
2338
179
172
1143
230
243
174
1039
464
619
109
232
535
1345
659
172
133
181
323
644
607
170
235
165
375
502
243
149
262
189
189
189
189
294
498
365
283
185
309

K 10
svn:author
V 2
np
K 8
svn:date
V 27
2011-03-23T17:33:04.585052Z
K 7
svn:log
V 93
MFC r219883:

Fix an error while constructing the table that maps context id -> egress
queue

END
K 10
svn:author
V 2
jh
K 8
svn:date
V 27
2011-03-23T17:56:38.977514Z
K 7
svn:log
V 323
Recognize "ro", "rdonly", "norw", "rw" and "noro" as equal options in
vfs_equalopts(). This allows vfs_sanitizeopts() to filter redundant
occurrences of these options. It was possible that for example both "ro"
and "rw" options became active concurrently.

PR:		kern/133614
Discussed on:	freebsd-hackers
MFC after:	1 month

END
K 10
svn:author
V 7
attilio
K 8
svn:date
V 27
2011-03-23T18:08:54.790459Z
K 7
svn:log
V 4
MFC

END
K 10
svn:author
V 7
attilio
K 8
svn:date
V 27
2011-03-23T19:05:34.568006Z
K 7
svn:log
V 151
Improve deadlock robustness: force intimate polling functions to skip
locking when possible.

In this case RX_LOCK'ing in if_lem.

Reported by:	rstone

END
K 10
svn:author
V 7
attilio
K 8
svn:date
V 27
2011-03-23T19:12:48.714322Z
K 7
svn:log
V 130
Improve deadlock robustness: force intimate polling functions to skip
locking when possible.

In this case RX_LOCK'ing in if_igb.

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-23T19:30:47.203081Z
K 7
svn:log
V 128
 - Fix rebuild_lba field usage -- it should be per-volume.
 - Add safety belt against touching volumes in RAID level migration.

END
K 10
svn:author
V 8
hselasky
K 8
svn:date
V 27
2011-03-23T19:41:44.750392Z
K 7
svn:log
V 91
Comply with style(9).

Reported by:	gavin
MFC after:	14 days
Approved by:	thompsa (mentor)

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T20:55:29.033625Z
K 7
svn:log
V 396
MFC: r219335

- Allocate the DMA memory shared between the host and the controller as
  coherent.
- Add some missing bus_dmamap_sync() calls. This includes putting such
  calls before calling reply handlers instead of calling bus_dmamap_sync()
  for the request queue from individual reply handlers as these handlers
  generally read back updates by the controller.

Tested on amd64 and sparc64.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T20:56:56.413221Z
K 7
svn:log
V 254
MFC: r219336

- Allocate the DMA memory used for the work area as coherent as at least
  the ataahci(4) and atamarvell(4) drivers share it between the host and
  the controller.
- Spell some zeros as BUS_DMA_WAITOK when used as bus_dmamem_alloc() flags.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T20:58:12.354915Z
K 7
svn:log
V 72
MFC: r219337

Add missing bus_dmamap_sync() calls for the work DMA map.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T20:59:20.738012Z
K 7
svn:log
V 72
MFC: r219338

Add missing bus_dmamap_sync() calls for the work DMA map.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T21:04:56.586041Z
K 7
svn:log
V 169
MFC: r219567

Sync licenses and the corresponding RCS IDs with NetBSD, mainly switching
the licenses of Matthew R. Green and the TNF to 2-clause.

Obtained from:	NetBSD

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T21:06:19.326674Z
K 7
svn:log
V 147
MFC: r219060

- Allocate the DMA memory shared between the host and the controller as
  coherent.
- Update a comment to no longer reference Alpha.

END
K 10
svn:author
V 5
edwin
K 8
svn:date
V 27
2011-03-23T21:22:03.229760Z
K 7
svn:log
V 185
Please welcome the Brazilian calendar in the FreeBSD base.

For now, calendar.brazilian points to pt_BR.ISO8859-1

Submitted by:	Renato Tambellini <rtsanch@gmail.com>
MFC after:	1 week

END
K 10
svn:author
V 7
yongari
K 8
svn:date
V 27
2011-03-23T22:06:09.795381Z
K 7
svn:log
V 36
Remove unused DMA map/tag in softc.

END
K 10
svn:author
V 7
delphij
K 8
svn:date
V 27
2011-03-23T22:08:01.449760Z
K 7
svn:log
V 344
humanize_number(3) multiply the input number by 100, which could cause an
integer overflow when the input is very large (for example, 100 Pi would
become about 10 Ei which exceeded signed int64_t).

Solve this issue by splitting the division into two parts and avoid the
multiplication.

PR:		bin/146205
Reviewed by:	arundel
MFC after:	1 month

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T22:33:29.849546Z
K 7
svn:log
V 432
MFC: r219339, r219532

- Remove clause 3 and 4 from TNF licenses. [1]
- Add the _RF_X committed in r212998 (merged to stable/8 in r213478) also
  to the tables in the sparc64 reloc.c in order reduce differences between
  the kernel and the userland source. This results in no functional change
  though.
- Consistently abbreviate the names of the relocations.
- End sentences with dots.
- Fix whitespace.

Obtained from:	NetBSD [1]

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-23T22:35:18.683632Z
K 7
svn:log
V 106
MFC: r219608

Remove the advertising clause from the UCB license according to the
July 22, 1999 addendum.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-23T23:48:44.625418Z
K 7
svn:log
V 295
Make the ar2133ForceBias() call controllable at runtime.

At least one AR5416 user has reported measurable throughput drops
with this option. For now, disable it and make it a run-time
twiddle. It won't take affect until the next radio programming
trip though (eg channel scan, channel change.)

END
K 10
svn:author
V 3
kib
K 8
svn:date
V 27
2011-03-24T00:42:07.054805Z
K 7
svn:log
V 123
MFC r219713:
Implement the usertime and systime keywords for ps, printing the
corresponding times reported by getrusage().

END
K 10
svn:author
V 2
np
K 8
svn:date
V 27
2011-03-24T01:03:01.489867Z
K 7
svn:log
V 299
Do not over-allocate MSI interrupts for the case where each ingress
queue has its own interrupt.  If the exact number that we need is not a
power of 2 and we're using MSI, then switch to interrupt multiplexing.

While here, replace the magic numbers with something more readable.

MFC after:	3 days

END
K 10
svn:author
V 2
np
K 8
svn:date
V 27
2011-03-24T01:13:28.195690Z
K 7
svn:log
V 73
T3C initialization should setup the parity fence too.

MFC after:	1 week

END
K 10
svn:author
V 2
np
K 8
svn:date
V 27
2011-03-24T01:16:48.637030Z
K 7
svn:log
V 95
t3_free_sge_resources should be given the number of qsets it needs to free.

MFC after:	1 week

END
K 10
svn:author
V 2
bz
K 8
svn:date
V 27
2011-03-24T01:24:35.532554Z
K 7
svn:log
V 12
IFC @219944

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-24T04:57:35.142633Z
K 7
svn:log
V 43
Fix a completely wrong variable reference.

END
K 10
svn:author
V 8
hselasky
K 8
svn:date
V 27
2011-03-24T07:59:21.684984Z
K 7
svn:log
V 88
Fix typo.

Reported by:	Garrett Cooper
MFC after:	14 days
Approved by:	thompsa (mentor)

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T08:37:48.554343Z
K 7
svn:log
V 288
MFgraid/head r217827:
Change BIO_GETATTR("GEOM::kerneldump") API to make set_dumper() called by
consumer (geom_dev) instead of provider (geom_disk). This allows any geom
insert it's code into the dump call chain, implementing more sophisticated
functionality then just disk partitioning.

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T08:56:12.567709Z
K 7
svn:log
V 69
MFgraid/head r218174:
Add simple in-kernel API for controlling leds.

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T09:12:03.423710Z
K 7
svn:log
V 360
MFH      r219477, r219582, r219583, r219593, r219619, r219622, r219634,
r219635, r219643, r219644, r219645, r219659, r219665, r219746, r219752,
r219754, r219755, r219759, r219774, r219777, r219778, r219784, r219797,
r219800, r219826, r219838, r219866, r219867, r219871, r219872, r219874,
r219881, r219890, r219908, r219909, r219910, r219921, r219923, r219929.

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T09:12:54.353465Z
K 7
svn:log
V 360
MFH      r219477, r219582, r219583, r219593, r219619, r219622, r219634,
r219635, r219643, r219644, r219645, r219659, r219665, r219746, r219752,
r219754, r219755, r219759, r219774, r219777, r219778, r219784, r219797,
r219800, r219826, r219838, r219866, r219867, r219871, r219872, r219874,
r219881, r219890, r219908, r219909, r219910, r219921, r219923, r219929.

END
K 10
svn:author
V 4
bapt
K 8
svn:date
V 27
2011-03-24T12:04:42.942835Z
K 7
svn:log
V 91
Fix confusion between a-characters and d-characters

Submitted by:	avg
Approved by:	cognet

END
K 10
svn:author
V 2
ru
K 8
svn:date
V 27
2011-03-24T12:35:09.933623Z
K 7
svn:log
V 64
It's possible to unmount multiple items at once, make it clear.

END
K 10
svn:author
V 4
bapt
K 8
svn:date
V 27
2011-03-24T12:35:59.325331Z
K 7
svn:log
V 81
Really fix the confusion, sorry for noise

Submitted by:	avg
Approved by:	cognet

END
K 10
svn:author
V 7
pluknet
K 8
svn:date
V 27
2011-03-24T13:18:09.917626Z
K 7
svn:log
V 166
MFC r218741:

Bump dummynet module version to meet dummynet schedulers' requirements,
and thus unbreak loading dummynet.ko via /boot/loader.conf.

Approved by:	luigi

END
K 10
svn:author
V 2
ru
K 8
svn:date
V 27
2011-03-24T13:52:59.803710Z
K 7
svn:log
V 31
Discourage from using "cp -r".

END
K 10
svn:author
V 3
pjd
K 8
svn:date
V 27
2011-03-24T14:12:41.960306Z
K 7
svn:log
V 165
Properly print characters larger than 127.

Submitted by:	noordsij <noordsij@cs.helsinki.fi>
Reviewed by:	Eric Schrock <eric.schrock@delphix.com>
MFC after:	1 month

END
K 10
svn:author
V 4
nyan
K 8
svn:date
V 27
2011-03-24T15:09:36.857280Z
K 7
svn:log
V 185
MFi386: the part of 219452

  - bunch of variables are turned into uint8_t.
  - the setting and reading of "fmt" in load() is removed.
  - buf in printf() is made static to save space.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-24T15:27:15.797116Z
K 7
svn:log
V 2241
Fix a WME corner case found by the FreeBSD 802.11n testing crew.

The symptom: sometimes 11n (and non-11n) throughput is great.
Sometimes it isn't. Much teeth gnashing occured, and much kernel
bisecting happened, until someone figured out it was the order
of which things were rebooted, not the kernel versions.
(Which was great news to me, it meant that I hadn't broken if_ath.)

What we found was that sometimes the WME parameters for the best-effort
queue had a burst window ("txop") in which the station would be allowed
to TX as many packets as it could fit inside that particular burst
window. This improved throughput.

After initially thinking it was a bug - the WME parameters for the
best-effort queue -should- have a txop of 0, Bernard and I discovered
"aggressive mode" in net80211 - where the WME BE queue parameters
are changed if there's not a lot of high priority traffic going on.
The WME parameters announced in the association response and beacon
frames just "change" based on what the current traffic levels are.
So in fact yes, the STA was acutally supposed to be doing this higher
throughput stuff as it's just meant to be configuring things based on
the WME parameters - but it wasn't.

What was eventually happening was this:

* at startup, the wme qosinfo count field would be 0;
* it'd be parsed in ieee80211_parse_wmeparams();
* and it would be bumped (to say 10);
* .. and the WME queue parameters would be correctly parsed and set.

But then, when you restarted the assocation (eg hostap goes away and
comes back with the same qosinfo count field of 10, or if you
destroy the sta VIF and re-create it), the WME qosinfo count field -
which is associated not to the VIF, but to the main interface -
wouldn't be cleared, so the queue default parameters would be used
(which include no burst setting for the BE queue) and would remain
that way until the hostap qosinfo count field changed, or the STA
was actually rebooted.

This fix simply cleares the wme capability field (which has the count
field) to 0, forcing it to be reset by the next received beacon.

Thanks go to Milu for finding it and helping me track down what was
going on, and Bernard Schmidt for working through the net80211 and
WME specific magic.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-24T16:06:54.760697Z
K 7
svn:log
V 84
Flip back HT/40 and Short-GI (for 40mhz operation). These are now verified to work.

END
K 10
svn:author
V 7
pluknet
K 8
svn:date
V 27
2011-03-24T16:06:57.057082Z
K 7
svn:log
V 76
Add missing resource limits:
- RLIMIT_NPTS
- RLIMIT_SWAP

MFC after:	1 week

END
K 10
svn:author
V 6
marcel
K 8
svn:date
V 27
2011-03-24T16:56:33.925900Z
K 7
svn:log
V 1046
Add necessary address space mapping. The Altix architecture has distinct
address spaces for PCI devices and CPUs. That is, the S-Hub translates
addresses on the FSB and coming from CPUs to addresses valid on the PCI bus.
This is abstracted and implemented in FreeBSD by having the handle contain the
CPU address, while the resource itself describes the PCI bus address. Since
devices are mapped when resources are activated and the bus handle is derived
from that, have the SGI PCI bus driver handle the activation of resources
instead of passing it up to the nexus.

Note that the Altix architecture allows for IRQ values larger than 255 even
though the intline register in the PCI configuration space does not. FreeBSD
also doesn't support it by virtue of having an IRQ resource space that's
limited. On my machines the IRQ values are within bounds so I'm not going to
worry about this detail. It may very well be theoretical.

With this change the bge(4) driver attaches properly. The one thing stopping
us from netbooting is... interrupts...

END
K 10
svn:author
V 3
uqs
K 8
svn:date
V 27
2011-03-24T17:09:24.762349Z
K 7
svn:log
V 137
MFH r219209: Unbreak .Aq for non-ASCII output like -Tps or -Tutf8.

PR:		gnu/154822
Submitted by:	Dominic Fandrey <kamikaze@bsdforen.de>

END
K 10
svn:author
V 3
uqs
K 8
svn:date
V 27
2011-03-24T17:09:37.542809Z
K 7
svn:log
V 150
MFH r219209: Unbreak .Aq for non-ASCII output like -Tps or -Tutf8.

PR:             gnu/154822
Submitted by:   Dominic Fandrey <kamikaze@bsdforen.de>

END
K 10
svn:author
V 5
trasz
K 8
svn:date
V 27
2011-03-24T17:20:24.004608Z
K 7
svn:log
V 80
Make "LOGIN" and "CLASS" columns width scale properly instead of wasting space.

END
K 10
svn:author
V 3
jhb
K 8
svn:date
V 27
2011-03-24T18:40:11.318817Z
K 7
svn:log
V 946
Fix some locking nits with the p_state field of struct proc:
- Hold the proc lock while changing the state from PRS_NEW to PRS_NORMAL
  in fork to honor the locking requirements.  While here, expand the scope
  of the PROC_LOCK() on the new process (p2) to avoid some LORs.  Previously
  the code was locking the new child process (p2) after it had locked the
  parent process (p1).  However, when locking two processes, the safe order
  is to lock the child first, then the parent.
- Fix various places that were checking p_state against PRS_NEW without
  having the process locked to use PROC_LOCK().  Every place was already
  locking the process, just after the PRS_NEW check.
- Remove or reduce the use of PROC_SLOCK() for places that were checking
  p_state against PRS_NEW.  The PROC_LOCK() alone is sufficient for reading
  the current state.
- Reorder fill_kinfo_proc() slightly so it only acquires PROC_SLOCK() once.

MFC after:	1 week

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T19:11:05.098767Z
K 7
svn:log
V 371
MFgraid/head r217014:
Make `geom XXX list` and `geom XXX status` outputs more consistent:
Add -a options to print all geoms, not only ones with providers.
Add -g option for `status` to report geom's names, not provider's.
Make `status` by default report provider's status (if present), not geom's.
Make `status` report consumer's statuses, not only "synchronized" field.

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T19:23:42.239200Z
K 7
svn:log
V 526
MFgraid/head r218212, r218257:
Introduce new type of BIO_GETATTR -- GEOM::setstate, used to inform lower
GEOM about state of it's providers from the point of upper layers.
Make geom_disk use led(4) subsystem to illuminate states in such fashion:
FAILED - "1" (on), REBUILD - "f5" (slow blink), RESYNC - "f1" (fast blink),
ACTIVE - "0" (off).
LED name should be set for each disk via kern.geom.disk.%s.led sysctl.
Later disk API could be extended to allow disk driver to report this info
in custom way via it's own facilities.

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T19:50:34.781300Z
K 7
svn:log
V 17
MFbase @r219970.

END
K 10
svn:author
V 5
trasz
K 8
svn:date
V 27
2011-03-24T20:15:42.542194Z
K 7
svn:log
V 137
Add proper width calculation for time fields (time, cputime and usertime).
This fixes the ugly overflow in "ps aux" output for "[idle]".

END
K 10
svn:author
V 3
pjd
K 8
svn:date
V 27
2011-03-24T20:28:09.380218Z
K 7
svn:log
V 442
Checking file access on size change is bogus. The checks are done earlier by
VFS where we know if this is truncate(2) or ftruncate(2). If this is the
latter we should depend on the mode the file was opened and not on the current
permission.

PR:		standards/154873
Reported by:	Mark Martinec <Mark.Martinec@ijs.si>
Discussed with:	Eric Schrock <eric.schrock@delphix.com>
Discussed with:	Mark Maybee <Mark.Maybee@Oracle.COM>
MFC after:	1 month

END
K 10
svn:author
V 3
mav
K 8
svn:date
V 27
2011-03-24T21:31:32.702736Z
K 7
svn:log
V 1251
MFgraid/head:
Add new RAID GEOM class, that is going to replace ataraid(4) in supporting
various BIOS-based software RAIDs. Unlike ataraid(4) this implementation
does not depend on legacy ata(4) subsystem and can be used with any disk
drivers, including new CAM-based ones (ahci(4), siis(4), mvs(4), ata(4)
with `options ATA_CAM`). To make code more readable and extensible, this
implementation follows modular design, including core part and two sets
of modules, implementing support for different metadata formats and RAID
levels.

Support for such popular metadata formats is now implemented:
Intel, JMicron, NVIDIA, Promise (also used by AMD/ATI) and SiliconImage.

Such RAID levels are now supported:
RAID0, RAID1, RAID1E, RAID10, SINGLE, CONCAT.

For any all of these RAID levels and metadata formats this class supports
full cycle of volume operations: reading, writing, creation, deletion,
disk removal and insertion, rebuilding, dirty shutdown detection
and resynchronization, bad sector recovery, faulty disks tracking,
hot-spare disks. For Intel and Promise formats there is support multiple
volumes per disk set.

Look graid(8) manual page for additional details.

Co-authored by:	imp
Sponsored by:	Cisco Systems, Inc. and iXsystems, Inc.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T00:03:21.932765Z
K 7
svn:log
V 563
Bring over interrupt mitigation changes from ath9k.

* The existing interrupt mitigation code didn't mitigate anything - the
  per-packet TX/RX interrupts are still occuring. It's possible this
  worked for the AR5416 but not any later chipsets; I'll investigate and
  update as needed.

* Set both the RX and TX threshold registers whilst I'm at it.

This is verified to work on the AR9220 and AR9160. I'm leaving it off
by default in case it's truely broken, but I need to have it enabled
when doing 11n testing or interrupt loads exceed 10,000 interrupts/sec.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T00:05:26.049929Z
K 7
svn:log
V 77
Add some more AR_PCU_MISC_MODE2 register settings - these are SOWL or later.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T00:06:19.686302Z
K 7
svn:log
V 38
oops, commited the wrong file change.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T00:06:58.318662Z
K 7
svn:log
V 86
The right commit - add a couple more AR_PCU_MISC_MODE2 register bits -
SOWL specific.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T00:40:08.540685Z
K 7
svn:log
V 227
Flip ANI on for the AR5416 and later chips. I haven't verified it on
the AR9285 so I'll leave it off for that.

Ath9k sources indiciate that one of the ANI modes interferes with
RIFS detection, so match ath9k and disable that.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T00:45:24.994529Z
K 7
svn:log
V 548
After discussion with Felix Fietkau (nbd) about the ath9k Merlin LNA bit
settings, it seems that our defines are backwards and don't match what
is in the EEPROM documentation or internal driver.

The ath9k code used to have a bitfield here, rather than a uint8_t, and
there were #defines used to swap the order based on the endian of the
platform - this wasn't because of nybble or bit ordering of the
underlying host but because of what the compiler was doing.

This may be the reason for the backwards field numbers, as ath9k had
similar issues.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T04:15:30.917437Z
K 7
svn:log
V 511
Re-disable the setting of 2040/shortgi bits for now.

This seems to work fine for STA but not HT/20 AP mode.

Further discussion with net80211 people will need to take place
to ensure that the right flags are set based on the negotiated
capabilities of the remote peer, rather than whatever the local
parameters are.

Sending short-gi frames in 20mhz may work on some chips but
it certainly isn't supported on anything currently supported
by the HAL; and sending HT40 frames in HT20 mode just plain
won't work.

END
K 10
svn:author
V 5
kevlo
K 8
svn:date
V 27
2011-03-25T05:01:13.855019Z
K 7
svn:log
V 76
Fix panic while associating access point.
While here, add the SMC SMCWUSB-G

END
K 10
svn:author
V 8
hselasky
K 8
svn:date
V 27
2011-03-25T10:11:21.529232Z
K 7
svn:log
V 137
Fix initialisation order with regard to debug prints.

Reported by:	Luiz Otavio O Souza
MFC after:	14 days
Approved by:	thompsa (mentor)

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T10:53:13.769573Z
K 7
svn:log
V 70
I broke periodic adc calibrations - so restore them to working order.

END
K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2011-03-25T10:55:25.133778Z
K 7
svn:log
V 279
After discussing with Bernhard, the "right" way in net80211 to check
the channel width is ni->ni_chw, which is set to the negotiated channel
width. ni->ni_htflags is the capability, rather than the negotiated
value.

Teach both the TX path and the sample rate module about this.

END
K 10
svn:author
V 3
kib
K 8
svn:date
V 27
2011-03-25T10:57:57.317328Z
K 7
svn:log
V 409
Fix file leakage in the freebsd32_ioctl routines.

Code inspection shows freebsd32_ioctl calls fget for a fd and calls
a subroutine to handle each specific ioctl.  It is expected that the
subroutine will call fdrop when done.  However many of the subroutines
will exit out early if copyin encounters an error resulting in fdrop
never being called.

Submitted by:	John Wehle <john feith com>
MFC after:	3 days

END
K 10
svn:author
V 3
kib
K 8
svn:date
V 27
2011-03-25T11:05:28.856069Z
K 7
svn:log
V 150
Remove unneccessary panics, that can be easily triggered by user.
The copyin() function handles NULL as well as any other pointer.

MFC after:	3 days

END
K 10
svn:author
V 3
kib
K 8
svn:date
V 27
2011-03-25T11:43:49.748672Z
K 7
svn:log
V 57
Fully emulate MDIOCLIST for compat32.

MFC after:	1 week

END
K 10
svn:author
V 3
kib
K 8
svn:date
V 27
2011-03-25T11:52:31.012748Z
K 7
svn:log
V 169
Implement compat32 MEMRANGE_GET and MEMRANGE_SET. This is needed to
run 32bit Xorg server with VESA driver.

Submitted by:	John Wehle <john feith com>
MFC after:	1 week

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T12:46:08.577569Z
K 7
svn:log
V 94
MFC: r219543

Allocate the DMA memory shared between the host and the controller as
coherent.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T12:47:01.766568Z
K 7
svn:log
V 94
MFC: r219544

Allocate the DMA memory shared between the host and the controller as
coherent.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T12:48:06.301473Z
K 7
svn:log
V 94
MFC: r219545

Allocate the DMA memory shared between the host and the controller as
coherent.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T12:48:56.495577Z
K 7
svn:log
V 94
MFC: r219545

Allocate the DMA memory shared between the host and the controller as
coherent.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T12:50:50.264483Z
K 7
svn:log
V 198
MFC: r219547

- Allocate the DMA memory shared between the host and the controller as
  coherent.
- Constify the ti_devs table.
- Don't bother to set if_mtu to ETHERMTU, ether_ifattach() does that.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T12:53:09.445722Z
K 7
svn:log
V 402
MFC: r219548

Allocate the sound buffer DMA memory coherent. While NetBSD typically
also does this for sound drivers it's probably not necessary for all
combinations of controllers and drivers. However, given that our sound
drivers completely lack bus_dmamap_sync(9) calls this at least serves
as a workaround when enabling use of the IOMMU streaming buffers on
sparc64 and generally for arm and mips.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T13:03:13.189700Z
K 7
svn:log
V 269
MFC: r219340, r219531, r219533

- Add support for TLS relocations.
- Emitt an error when encountering an unsupported and in case of the
  kernel also for unaligned relocations.
- Fix R_SPARC_HIX22 and R_SPARC_LOX10 relocations. Apparently these are
  hardly ever used.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T13:08:19.432734Z
K 7
svn:log
V 187
MFC: r219780

In case reading PCIR_MINGNT fails don't use it for calculating the
latency. This is more or less a theoretical problem though as it
typically indicates way bigger problems.

END
K 10
svn:author
V 6
marius
K 8
svn:date
V 27
2011-03-25T13:09:57.317544Z
K 7
svn:log
V 90
MFC: r219782

On Serengeti-class machines the OFW root isn't the parent of the CPU
nodes.

END
K 10
svn:author
V 3
kib
K 8
svn:date
V 27
2011-03-25T14:00:36.017316Z
K 7
svn:log
V 216
Add O_CLOEXEC flag to open(2) and fhopen(2).
The new function fallocf(9), that is renamed falloc(9) with added
flag argument, is provided to facilitate the merge to stable branch.

Reviewed by:	jhb
MFC after:	1 week

END