Age | Commit message (Collapse) | Author |
|
ok millert@, sf@, deraadt@
|
|
the following improvements:
- Character at position CB is 'E' with diaeresis, not with tilde (12x24 version)
- Character at position D6 is 'O' with diaeresis, not with tilde (12x24 version)
- Character at position DC is 'U' with diaeresis, not with tilde (12x24 version)
- Fix middle bar thickness in the upper case 'eth' character (12x24 version)
- Fix ring alignment for the 'A' and 'a' characters (16x32 and 32x64 versions)
- Fix tilde alignment in the 'o' with tilde character (32x64 version)
- Remove strain pixel on the '3' and 'k' characters (32x64 version)
OK deraadt@, mpi@
|
|
found obscure. Repair a broken WangTEK 5150ES quirks entry that
apparently suffered some damage when imported in 1995. It never made
NetBSD/FreeBSD quirk lists at all.
Some whitespace tweaking to make everything line up.
|
|
At the moment it only supports disabling the watchdog, which lets me
continue to work on the Turris Mox.
ok kettenis@
|
|
Result is a crash at power down. Skip the activate function if
attach has failed. Solution taken from ehci(4).
OK deraadt@ kettenis@
|
|
devices with quirks.
|
|
|
|
For a small proportion of frames on 8265 we have observed firmware reporting
"not encrypted" even though in Wireshark these frames appear as regular
encrypted frames (rx_pkt_status=0xc0400007 type=0x8 subtype=0x80 m_len=1542).
This causes frame drops which do not occur with software crypto.
We might try again after a firmware upgrade. There seems to be no public
record of bug fixes made by Intel between firmware versions which degrades
our development process into pure trial-and-error. We need to waste our own
time to find out information which Intel should be providing to the public.
If anyone is aware of a source of such information, please let us know.
All this is of course very disappointing.
Problem reported by and debugged with help from solene@
|
|
their "CIPHER ST150S (old drive)" devices back.
|
|
ok patrick@
|
|
If the NIC is in some error state (seen on a i219LM when em_read_phy_reg_ex()
returns at "MDI Error"), it can happen that we loop endlessly because the loop
variable is modified again somewhere down in the call stack. Use a separate
variable to make the attach fail with "Hardware Initialization Failed" instead
of hanging.
yes deraadt@
|
|
This simplifies the code and allows any block size multiple of 1ms to
be used when play and recording number of channels are not the same.
ok mpi@
|
|
This simplifies the code and allows any block size supported by the
hardware to be used.
ok mpi@
|
|
The first sets the block size in frames, which is necessarily common
to play and recording directions no matter the number of channels. The
second sets the number of blocks per buffer for the given
direction. Together, these two functions allow audio drivers to easily
set the block size, matching both playback and recording constraints.
The round_blocksize() didn't allow to do so because it returns the
block size in *bytes*. Since the driver doesn't know if it's called
for the play or for the record block size, it's impossible to
calculate the block size in all cases if play and record number of
channels are different.
ok mpi@
|
|
|
|
of soft interrupts are lower than priorities of hard interrupts.
This allows the delivery of hard interrupts while soft interrupts
are masked.
|
|
ok kettenis
|
|
|
|
So fold 'modeflags' field of st_softc into 'flags' field of same. Nuke
a bunch of dubious/obvious comments.
|
|
Nuke pointless 'quirkdata' pointer in st_softc. We use the data once at
attach time and don't need to remember where we got it from.
|
|
store the discovered quirks in st_softc's 'quirks' field.
|
|
the 'quirks' field of struct quirksdata.
|
|
Reformat quirks array the way the autoindenter likes it to minimize
the effort needed to keep diffs short.
|
|
to a logical conclusion. Start cleaning up the left overs.
First, delete the unused quirk ST_Q_BLKSIZE and simplify the one
condition referencing it in light of the fact that !ST_Q_BLKSIZE would
always be true.
|
|
|
|
mrt6_mcast6_del() out of the rtable_walk(). This avoids recursion
to prevent stack overflow. Also it allows freeing the route outside
of the walk. Now mrt6_mcast_del() frees the route only when it is
deleted from the routing table. If that fails, it must not be
freed. After the route is returned by mf6c_find(), it is reference
counted. Then we need a rtfree(), but not in the other case.
Name mrt6_mcast_add() and mrt6_mcast_del() consistently.
Move rt_timer_remove_all() into mrt6_mcast_del().
Reported-by: syzbot+af7d510593d74c825960@syzkaller.appspotmail.com
OK mpi@
|
|
This support is undocumented, only works if you're using the kernel
timezone, and breaks during a DST shift. It also preferences file systems
managed by a Windows installation: many implementations, like ours, use
UTC by default (think: phones, digital cameras).
No complaints on tech@.
"good riddance" tedu@, "Yep." deraadt@
|
|
|
|
For gettimeofday(2), always copy out an empty timezone struct. For
settimeofday(2), still copyin(9) the struct but ignore the contents.
In gettimeofday(2)'s case we have not changed the original BSD semantics:
the kernel only tracks UTC time without an offset for DST, so a zeroed
timezone struct is the correct thing to return to the caller.
Future work could move these out into libc as stubs for clock_gettime and
clock_settime(2). But, definitely a "later" thing, given that we are in
beta.
Update the manpage to de-emphasize the timezone parameters for these
syscalls.
Discussed with tedu@, deraadt@, millert@, kettenis@, yasuoka@, jca@, and
guenther@. Tested by job@. Ports input from jca@ and sthen@. Manpage
input from jca@.
ok jca@ deraadt@
|
|
|
|
|
|
ok deraadt@
|
|
ok patrick@
|
|
|
|
|
|
|
|
|
|
|
|
ok deraadt@
|
|
|
|
ok deraadt@
|
|
ok dlg@
|
|
|
|
what I had intended to write anyway.
spotted-by & ok jsg@
|
|
Tested on a BCM57412
ok jmatthew@
|
|
ok kettenis@
|
|
ok jsg
|
|
|
|
ok deraadt@
|
|
From Krystian Lewandowski.
|