| Age | Commit message (Collapse) | Author |
|---|
|
assumed in places to be the index of the widget in the widget_t
array of the codec_t, but I'm paranoid.
use it to shrink/simplify/fortify some parts. will be used more
soon.
|
|
from the individual drivers now that ether_ioctl() handles this.
Shrinks the i386 kernels by..
RAMDISK - 2176 bytes
RAMDISKB - 1504 bytes
RAMDISKC - 736 bytes
Tested by naddy@/okan@/sthen@/brad@/todd@/jmc@ and lots of users.
Build tested on almost all archs by todd@/brad@
ok naddy@
|
|
dirty on the way out so that users are forced to run fsck afterwards. The
manpage politely suggested that the filesystem be checked after growing it;
change it to say that fsck is required.
|
|
* configure widgets all in one place
* add a flag on the widget_t to let us know if the widget is not
connected; shaves a lot of connection checking code
* be sure not to add power widgets as connectable sources/sinks
* configure unconnected pins as output pins. should help some
MacBooks and be benign to other devices.
the last change has been tested by several as a separate diff. no
real functional changes otherwise.
from Alexey Suslikov. thanks!
|
|
on all (at least all tested) devices. briefly, it works like so:
group together all converters that can be reached from or can reach
a connected input or output pin. ordering in the converter groups
correlates to the association and sequence of the input/output pin.
remove lots of static converter groupings in favor of the generic
grouping method. the only static groups left are for codecs that
still have static mixer configurations.
tested by many. thanks to all who tested; this wouldn't have
happened without your support.
|
|
|
|
use it to quiet some debug messages by default, so people don't get
scared when testing completely unrelated changes when AZALIA_DEBUG
is defined.
print out ADC groupings when AZALIA_DEBUG is defined like we do for
DAC groupings.
|
|
assemblies, so allow up to 512MB of memory on MVME188 systems. Thanks maz
for the 128MB board!
|
|
|
|
|
|
(i.e. with the valid bit set in them). Found the hard way by Anders Gavare
trying his latest gxemul, proves the hardware is more permitting than one
would expect it to be...
|
|
|
|
|
|
802.11 devices.
currently it has issues scanning.
ok jsg@
|
|
not a GW3887 chip.
ok mglocker@
|
|
|
|
|
|
synopsis as a comment (since it still works if needed).
ok drahn
|
|
|
|
|
|
|
|
|
|
todo. Discussed with deraadt@ and dlg@
|
|
ok deraadt
|
|
|
|
ok deraadt@
|
|
We can now just push unwanted ones back up into the SCSI layer
with NO_CCB like other drivers.
"Please do so" deraadt@
|
|
|
|
|
|
With this in bt.conf, the HID driver should work:
# Enable all interfaces.
interface * "OpenBSD BT"
# Attach a keyboard and/or mouse, or a mobile phone emulating such things.
attach 00:02:76:08:1c:37 type hid pin "0000"
Then start btd and run btctl -f bt.conf.
|
|
|
|
Use a 1 tick timeout() to determine if the kernel even manages to get
below softclock (from an old diff by mpf). If our timeout comes late,
reduce the high water marks (to half) for all network interfaces, thus
starving them of future packet allocations for their RX rings. For a
few ticks longer, also block the high water marks from rising even if
RX ring empty conditions would prod us to do so.
Cards may start dropping some packets off the end of their smaller RX
rings, but we were not able to do the work required in any case. With
less interrupt time and mbuf movement, the system finds time to make
progress at the network queues. Userland even gets to run.
A x40 tuned to 600MHz shows no real reduction in performance. But a
soekris has a working console now.
ok dlg claudio, and art liked it too
|
|
ok dlg@
|
|
it is very confusing like this.
ok deraadt@ canacar@
|
|
watermark for mbuf cluster allocations.
this is necessary for things like bge which cannot cope with less than a
certain number of pkts on the ring.
ok deraadt@
|
|
M_CLUSTER flags from the target mbuf. Still these function are only allowed
on newly allocated buffers.
OK dlg@
|
|
We can now just push unwanted ones back up into the SCSI layer
with NO_CCB like other drivers.
|
|
We can now just push unwanted ones back up into the SCSI layer
with NO_CCB like other drivers.
|
|
fixes v6-over-v4 gifs wrt pf chatter about state linking mismatches
ok jsing claudio, tested by Ant La Porte <ant at ukbsd.org>
|
|
|
|
|
|
|
|
|
|
more readable and straightforward format. Note that there is no longer
a default GPIO device, but it has to be sepcified on the command line
always (and as Theo mentioned, newfs also does not default to /dev/sd0a...)
You must do a 'make includesi' in /usr/src before building this command or
before your next system build.
ok uwe@
|
|
configuration and device attachment/detachment to securelevel 0.
GPIO pins can now only be configured at securelevel 0. Once the
securelevel is raised, only pins that have been configured and set
for securelevel access using the GPIOPINSET ioctl are accessible.
This also adds the possibility to give GPIO pins a name.
ok uwe@
|
|
|
|
|
|
from NetBSD with mods
|
|
ok deraadt
|
|
Most bits cloned from zaurus.
|
