Age | Commit message (Collapse) | Author |
|
from pkg_create for over a year.
|
|
|
|
ok mcbride@ djm@
'fine from me' jmc@
|
|
This, together with an updated xorg driver makes my drm/XVideo work.
Originally from Nigel Taylor.
ok oga@ mcbride@
|
|
defines instead of using custom macros. OK deraadt@ gilles@
|
|
__STRICT_ALIGNMENT is talking about accessing of integer types; it does
not cover doubles or floats or other things
ok miod kettenis
|
|
ok kettenis drahn
|
|
This fixed "react strangely" when the pms driver probes
for a synaptic-compatible touchpad.
Tested and ok mpi@
|
|
|
|
and makes it more portable, from Havard Eidnes.
|
|
lines. Problem noticed by me, this solution from halex@.
ok halex aja
|
|
|
|
for the defaulting of the year to work in the -t and arg1 forms that were
broken by previous change
ok millert@
|
|
|
|
ok sthen@ deraadt@
|
|
the alc(4) NIC while running or the NIC not working if the cable is
not plugged in upon boot up.
From Brad; tested by matteo filippetto, Gabriel Linder and edd@
|
|
inefficient but doesn't matter with reasonable numbers of interfaces.
ok dlg@
|
|
ok mcbride
|
|
|
|
|
|
-STANDARDS tweak
ok guenther
|
|
register. The spec doesn't say we have to do this while it mentions several
times one needs to wait for FR to clear after clearing FRE. The Linux driver
doesn't wait for it either. This allows us to get rid of the AHCI_F_IGN_FR
quirk.
As a side-effect this diff will probably stop ahci(4) attaching to (some)
NVIDIA fakeRAID devices. That's good since it is consistent with what we
do for Intel fakeRAID.
ok mikeb@, jmatthew@
|
|
Previously only available via iscsictl. ok claudio@
|
|
"-v" (previously only "-vd" worked). Similar to recent ospfd commit.
ok claudio@
|
|
"ospfd -v" (previously only "-vd" worked). Feedback on earlier implementation
from henning@ blambert@ claudio@, ok claudio@
|
|
remote end closes and reopens a connection.
From Christiano F. Haesbaert, ok claudio@
|
|
|
|
|
|
ok millert@, manpage fixes jmc@
|
|
From Christiano F. Haesbaert.
|
|
struct timeval. OK guenther@
|
|
construct;
this also sidesteps what seems to be a problem with mandoc, in that
"-column -compact" seems to mess up the formatting. thus these pages should
now have their lists formatted nicely (i.e. correctly aligned and with indent
applied);
as a side note, the fact that headers are not properly marked up is another
issue which will be addressed separately (a mandoc fix is needed, i think).
i have fudged a few of these to mark up properly, since the workaround does
make sense for some pages.
as another side note, i haven;t fixed man7, as i need to prepare a separate
diff for kristaps and ingo.
|
|
ok shadchin@ some weeks ago.
|
|
128-bit long double. Diff committed on behalf of martynas@
|
|
OK mikeb@ millert@
|
|
our in-tree compiler will emit code to do this at the start of main(), other
compilers might not do that.
ok miod@
|
|
|
|
|
|
in DIO-II space, as a fat device spanning four select codes (i.e. 16MB of
memory). This is way too much for an at-most 2 Mpixel 8bit frame buffer, and
it turns out that this is because the device provides both a regular DIO-II
frame buffer (spanning two select codes) and a regular STI frame buffer
(spanning the other two select codes).
This commit introduces a straightforward sti@dio attachment to get a working
sti(4) and wsdisplay(4) in a ridiculously small number of lines; however
the console code needs some changes to avoid duplicating globals.
While there, add sti@dio support for the bootblocks, and I couldn't help
myself but clean the most rotten parts of them, and try to have them reuse
various files in sys/arch/hp300/dev instead of rolling their outdated ones.
Tested on a real 382 with the low-resolution frame buffer:
sti0 at dio0 scode 132: rev 8.02;129, ID 0x27134CB440A00499
sti0: 382V, 2048x512 frame buffer, 640x480x8 display
sti0: 8x16 font type 1, 16 bpc, charset 0-255
wsdisplay0 at sti0 mux 1: console (std, vt100 emulation)
Boot blocks updates tested on DIO-II 425t (serial/glass console), SGC 425e
(serial/glass console) and 382 (serial/glass console). And will be tested
on SGC 425t soon as well.
|
|
reading, and introduce a define for the DIO-II device size, as reported by
the device itself (in quarters of select code span, just to make things
more complicated than necessary).
|
|
there is no way we can tell models 360 and 362 apart by probing for an SGC
bus, or for a frodo(4) chip since of the `lil' black swan' 3x2 models, only
model 382 has frodo. So don't bother trying to tell models 360 and 362
apart, and use a common 36X symbol. No functional change except for useless
code removal.
|
|
back when I thought that these devices were showing both in DIO-II and SGC
spaces; but, as researched by tsutsui@netbsd, there is nothing in the SGC
bus address space (assuming there is SGC bus logic at all) on 3x2.
|
|
|
|
made working, but since this model maxes out at 8MB RAM it's close to useless).
|
|
|
|
once in SEE ALSO; also prefer Xr to Fn where relevant;
diff started by Martin Pelikan
|
|
From: william dunand <william.dunand at gmail.com>
|
|
|
|
|
|
|