Age | Commit message (Collapse) | Author |
|
Only the BCM5700-BCM5704 adapters had TBI interfaces for fibre
and anyting newer uses the MII interface.
From Brad.
|
|
as they're FastE chipsets. So ifconfig media doesn't list
GigE for FastE-only capable PHY.
From Brad.
|
|
|
|
Integrated graphics and add some 3rd gen Core i[357] ids.
Also change Tigerpoint to NM10 while here.
ok kettenis@
|
|
tested to boot multiuser.
|
|
ok jsing
|
|
timeout', instead of being stuck with a non-progressing request. This lets
the nonexistent LUNs of the Insite Floptical probe (as non-existing)
correctly.
Step two of Floptical support, now if only the loading mechanism would unjam
I could try some real I/O with it...
|
|
controller, but other brands (jmicron and intel have been tested)
don't like something in the sleep process so they just lock up.
|
|
devices which advertize themselves as non-SCSI2-aware, since this command
appeared in the SCSI-2 specification.
This makes the Insite Floptical work when connected to a controller which
correctly handles spontaneous deselection (which happens when a non-zero
lun on said floptical device is addressed), such an esp(4) but not wdsc(4).
This is step one of getting Floptical devices working on SGI systems.
feedback and ok krw@
|
|
to build X at -O2 nowadays, as well as an increasing number of ports.
Based upon a diff from Brad, with a few values stripped down to fit within
the sun4/4c virtual address space limitation. Discussed with deraadt@
|
|
reported pressure is non-null. Fix the use of ALPS touchpads with recent
(>1.6) xf86-input-synaptics drivers, issue reported by janis at cieti lv.
Tested by yasuoka@ and janis, ok shadchin@
|
|
sparc floppies to fit again.
|
|
Ported from a DragonFly BSD commit by Constantine A. Murenin:
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/245ec76bc1613b22cf282526fa9931e4c16e4237
Tested on a Lanner FW-7539 appliance.
ok mlarkin mikeb haesbaert henning
|
|
_4ltol() and _lto4l() to bha, the only place they were used.
ok dlg@
|
|
used by Solaris for virtual ports (NPIV), and booting from thos is not
supported by OBP. Simplify the code accordingly.
|
|
NL_{ARG,LANG,MSG,SET,TEXT}MAX with newer POSIX.
Hide {FLT,DBL}_{DIG,MAX,MIN} and {PASS,TMP,NL_N}_MAX with newer XPG.
Make _POSIX_NGROUPS_MAX and _POSIX_OPEN_MAX conditional on the POSIX
version, like _POSIX_TZNAME_MAX already is.
Add some more _POSIX_* and _XOPEN_* 'specified' limits.
ok kettenis@
|
|
1) demote by 32 on the first bulk update to prevent failovers w/o having
a full state table;
2) don't do any demotion adjustments on the link up event and undemote
when bulk update finishes (or times out) preventing a race between
nodes getting a link state update asynchronously.
With phessler; tested by phessler and Kapetanakis Giannis. Thanks!
Looked through by henning and dlg. Now the correct version.
|
|
|
|
ok dlg@
|
|
reminded by jsg@
|
|
|
|
in RFC4302 and RFC4303. Right now only software crypto engine is
capable of doing it.
Replay check was rewritten to implement algorithm described in the
Appendix A of RFC4303 and the window size was increased to 64.
Tested against OpenBSD, Linux (strongswan) and Windows.
No objection from the usual suspects.
|
|
|
|
ok kettenis@
|
|
reported memory but end beyond it, such as > 1GB DIMMs in bank 0.
Also, currently restrict physical memory usage to 1.5GB - there seems to be a
bogus 32 bit truncation happening in the IP30 specific codepath, which in turns
ends up causing the low memory alias region (and thus, the exception vectors
and the NMI handler) to be overwritten, which I can't find from code inspection
(does anyone has 2GB of Octane memory to spare?)
Both issues reported and fix/workaround tested by Florentijn van Kampen,
thanks!
|
|
1) demote by 32 on the first bulk update to prevent failovers w/o having
a full state table;
2) don't do any demotion adjustments on the link up event and undemote
when bulk update finishes (or times out) preventing a race between
nodes getting a link state update asynchronously.
With phessler; tested by phessler and Kapetanakis Giannis. Thanks!
Looked through by henning and dlg.
|
|
|
|
to the public; from broadcom/linux via brad
|
|
from Brad, ok jmatthew mikeb.
- Have the SB700 attach routine properly call the IDE to AHCI
function and migrate the ATI_SBX00_SATA_1 PCI id to using
the SB700 attach routine. The SB600 routine was being used
because it does the proper call. This just makes it so all
of the SB700 controllers use the same attach routine, especially
incase any other workarounds/errata type things come up or
not setting SB600 things for SB700.
- Have the Hudson-2 attach routine set the AHCI_F_IPMS_PROBE
flag to resolve the issue with Port Multiplier support. The
SB700 attachment function was being used because it was
setting the flag. This also fixes the other Hudson-2 AHCI
controllers so they won't experience the same issue.
|
|
the prototype-scsi_link's SDEV_2NDBUS flag rather than against its
scsibus field. First, the scsibus field hasn't even been initialized
when device_register() is called so it's always 0 anyway; second, the
path number is supposed to be locally scoped to a single device
whereas the scsibus field is a global scsibus(4) device number.
The existing code only happened to work because all of the dual-port
fibre-channel adapters we currently support attach as two devices with
one scsibus each rather than a single device with two scsibuses, so we
would never see anything but "fp@0".
Initial investigation and diff by jmatthew after my SCSI cleanups at
c2k11 broke sparc64's ability to boot from isp(4); newer version from
me based on discussion with krw and kettenis.
tested and ok kettenis
|
|
|
|
needed by hand.
|
|
much of the kernel world when it did not need to
|
|
MI float.h which pulls in and defines the values that are needed from
there, and repair sys/limits.h so that it defines the values it needs
as well (depending on POSIX version, XPG version, etc). guenther has
a more exact selection of that coming for limits.h.
this also fixes a few mistakes for the vax.
reviewed by kettenis and guenther.
|
|
from david hill; ok henning
|
|
CAVEATS: Assumes that a new socket can't have any of the
FCNTLFLAGS set on it, which _is_ true, currently... (guenther@)
Okay guenther@, deraadt@.
|
|
all the symbols that POSIX says they must and fewer that they can't and,
most importantly, to not require a specific ordering of headers.
ports testing by naddy@
ok millert@ deraadt@
|
|
"Why is this not commited yet?" says miod
|
|
all the goop it needs by itself
ok millert
|
|
R5000SC processor modules; these sport an up to 512KB, physically indexed,
write-through L2 cache which is not connected to the canonical external cache
interface of these processors (hence requiring specific code to drive it).
The cache is enabled early and disabled before returning to ARCBios (for very
nasty things happen otherwise).
Tested on R5000SC, will be tested on R4600SC soon.
|
|
handling of a partial last line in IOSyncDCache. No functional change.
|
|
size being not larger than 4KB, use Hit operations on the pa instead of Index
operations on the va for each set in the SyncDCachePage routine, when running
with such a cache.
|
|
smallest possible size; and on kernels with 16KB pages, where no virtual
aliasing happens, use Hit operations on the pa instead of index operations
on the va for all sets in the SyncDCachePage routine.
Tested by mikeb@ on IP32 and myself on IP27/28/30/35
|
|
|
|
``-upper_bound % upper_bound''. Simplifies the code and makes it the
same on both ILP32 and LP64 architectures, and also slightly faster on
LP64 architectures by using a 32-bit remainder instead of a 64-bit
remainder.
Pointed out by Jorden Verwer on tech@
ok deraadt; no objections from djm or otto
|
|
cache lines and sizes are already there, after all.
The ConfigCache cache routine is responsible for filling these function
pointers; cache routine invocation macros are updated to use the cpu_info
fields, but may still be overriden in <machine/cpu.h> on platforms where
only one set of cache routines is used.
|
|
which will be easier to maintain on the long run. Be sure to rm cache_r*.d in
your kernel compile directories after updating.
|
|
in cp0_set_config() for consistency.
|
|
NULL-terminated.
Part of a larger diff from Gerhard Roth
|
|
first and last qTD pointers to NULL because only iTDs will be used.
Part of a larger diff from Gerhard Roth
|