| Age | Commit message (Collapse) | Author | Files | Lines |
|
This adds the missing TAS3004 volume control. Before, I put my ear
near the speaker (to hear audio), because I had no way to turn up the
volume. Now, the default volume is much louder, so I use sndioctl(1)
to turn it down.
Check for the model string "PowerBook5,4". This model's device tree
has compatible = "AOAKeylargo" for the audio, doesn't show the TAS3004
in the same way as other models.
|
|
for example, with locking assertions.
OK mpi@, anton@
|
|
adding more filter properties without cluttering the struct.
OK mpi@, anton@
|
|
ok tedu@ jsg@
|
|
in drivers. Terse one liners, NULLs instead of 0's, explicitly specify
all members, etc.
Nuke #ifdef notyet blocks related to the scsi_adapter in aic.
No intentional functional change.
ok tedu@
|
|
ok deraadt krw
|
|
There are no units noted here, but macppc is a 100hz platform so it's safe
to just assume 2500 milliseconds here.
ok jsg@
|
|
make the structs const so that the data are put in .rodata.
OK mpi@, deraadt@, anton@, bluhm@
|
|
This diff completely converts sys/arch/macppc to *sleep_nsec(9).
Also convert dev/thermal.c while we're down here. Unsure what that
file's driver's name is, if any.
ok kn@ visa@
|
|
|
|
|
|
ok deraadt@
|
|
ok jsg
|
|
|
|
From Christian Ludwig <christian_ludwig at genua dot de>
ok visa@
|
|
Suggested by kettenis@, ok visa@
|
|
ok millert@ krw@
|
|
|
|
|
|
Using a name with the 'db_' prefix makes it invisible from the dynamic
profiler.
ok deraadt@, kettenis@, visa@
|
|
is enough.
This flag should only be set by the stack, drivers shouldn't mess
with it.
Discussed with dlg@ and mikeb@, ok mikeb@, stsp@
|
|
this means packets are consistently counted in one place, unlike the
many and various ways that drivers thought they should do it.
ok mpi@ deraadt@
|
|
|
|
Use the same values hardcoded in sys/dev/acpi/acpi.c where possible.
OK visa@
|
|
Build testing assistance from deraadt@
|
|
|
|
methods from all audio drivers and from the audio_if structure as they
are never called.
|
|
Fixes "audio0: different play and record parameters ... " errors, and
probably other unreported errors.
help and ok landry@
|
|
Tested by and ok mglocker@
|
|
ok deraadt
|
|
|
|
|
|
hw.sensors fan values seen on macppc models with a new smu-firmware.
Help and ok kettenis
|
|
ok deraadt kettenis
|
|
|
|
59 degC require temporary values larger than 32bit signed. Therefore
bump those involved variables to int64_t and replace imin/imax with
ulmin/ulmax to get proper results.
|
|
|
|
ok kettenis
|
|
based on the temperature sensor values. A driver can register it fans or
temperature sensors there. Ported from FreeBSD.
ok deraadt kettenis
|
|
ok kettenis
|
|
ok kettenis
|
|
ok kettenis
|
|
configure fan speeds.
from mglocker@, ok kettenis@
|
|
|
|
|
|
ok beck@ deraadt@
|
|
drivers still set IFF_NOTRAILERS while others do not. Remove all usage of
the flag from the drivers which in ancient times used it (and the modern
drivers which blindly copied it from those drivers of yore).
suggested by guenther. ok mpi
|
|
there are two things shared between the network stack and drivers
in the send path: the send queue and the IFF_OACTIVE flag. the send
queue is now protected by a mutex. this diff makes the oactive
functionality mpsafe too.
IFF_OACTIVE is part of if_flags. there are two problems with that.
firstly, if_flags is a short and we dont have any MI atomic operations
to manipulate a short. secondly, while we could make the IFF_OACTIVE
operates mpsafe, all changes to other flags would have to be made
safe at the same time, otherwise a read-modify-write cycle on their
updates could clobber the oactive change.
instead, this moves the oactive mark into struct ifqueue and provides
an API for changing it. there's ifq_set_oactive, ifq_clr_oactive,
and ifq_is_oactive. these are modelled on ifsq_set_oactive,
ifsq_clr_oactive, and ifsq_is_oactive in dragonflybsd.
this diff includes changes to all the drivers manipulating IFF_OACTIVE
to now use the ifsq_{set,clr_is}_oactive API too.
ok kettenis@ mpi@ jmatthew@ deraadt@
|
|
|
|
Incoherency brought by jmc@ and schwarze@ because the SYNOPSIS of the
corresponding manual do not match its NAME.
This is one step further in the zs(4) unification... Go dokey go!
Tested by jmatthew@, ok sebastia@, deraadt@
|