| Age | Commit message (Collapse) | Author |
|---|
|
from henric@ via deraadt@
|
|
ok deraadt@
|
|
breaks some onboard de(4)'s. The conventional way of getting media settings
is just fine on alpha, so let's just use this. Shrinks de(4) a bit on alpha.
While there de-inline tulip_21140_mediainit().
ok brad@
|
|
further net80211 changes. ok mickey@
|
|
ok drahn@
|
|
planetpixel dot de).
|
|
originally pointed out by Mike Silbersack on the fbsd version of the iwi
driver.
|
|
atapi_capacity_descriptor in favour of equivalent struct
scsi_direct_blk_desc. No code change. One verbiage adjustment.
|
|
- for consistency fix order of operations for MII_TICK switch case in eephy
|
|
IFF_RUNNING instead. Also, do not blindly restore flags onto an interface when
returning to the running state.
This eliminates the possibility that the kernel will bring the interface back
up after a link state change on the physical interface, even though the user
may have done an "ifconfig carpN down" in the meantime. Similarly two link
state down events on the physical interface in succession could result in us
never coming out of the INIT state.
The master/backup state is still reported via link state information, so
bgpd/ospfd, etc, should function as before.
This also addresses PR4238.
ok mpf@, ok with the idea etc henning@
|
|
Tweak the xmphy driver a little bit based on something I learned about
the built-in 1000baseX interface in the Level 1 LXT1001 chip. The Level 1
PHY comes up with the isolate bit in the control register set by default,
but it also has the autonegotiate bit set. When you tell the xmphy driver
to select IFM_AUTO mode, it sees that the autoneg bit is already on, and
thus doesn't bother updating the control register. However this means that
the isolate bit is never turned off (unless you manually select 1000baseSX
full or half duplex mode, which does result in the control register being
modified and the ISO bit being turned off).
This subtle and unusual behavioral difference stopped me from being able
to receive packets on the SMC9462TX card for several days, since isolating
the PHY disconnects it from the MAC's data interface. The fix is to omit
the 'is the autoneg big set?' test, since it doesn't really provide much
of an optimization anyway.
This commit also updates the xmphy driver to support the Jato/Level 1
internal PHY. (I'm not sure how Jato Technologies is related to Level 1:
all I know is the OUI from the PHY ID registers maps to Jato in the OUI
database.)
From FreeBSD
|
|
|
|
Control muting of both left and right channels.
|
|
|
|
|
|
|
|
scsi_mode_direct_blk_desc -> scsi_direct_blk_desc
scsi_mode_blk_desc_big -> scsi_blk_desc_big
|
|
|
|
least) before 10 byte MODE SENSE. Some older devices can't/won't
distinguish between the two and return 6 byte MODE SENSE data for 10
byte requests.
Check that at least a full header was returned.
Tested by miod@ hshoexer@ and Ed Wandasiewisz on troublesome devices.
|
|
|
|
From FreeBSD
|
|
|
|
|
|
ok brad@
|
|
|
|
|
|
(but I tend to call it ssh localhost & now when telnetd is
history). This is more localized patch, but leaves us with
a recursive lock for protecting scheduling and signal state.
Better care is taken to actually be symmetric over mi_switch.
Also, the dolock cruft in psignal can go with this solution.
Better test runs by more people for longer time has been
carried out compared to the c2k5 patch.
Long term the current mess with interruptible sleep, the
default action on stop signals and wakeup interactions need
to be revisited. ok deraadt@, art@
|
|
From RusticBSD, ok deraadt@
|
|
.ev56, .ev4, etc, in-file modifiers).
|
|
|
|
|
|
|
|
|
|
|
|
- allocate and use scribble page
- provide method to see if something has scribbled out of bounds
The gart still remains disabled by default.
From jason@
|
|
|
|
- recognize BCM5750 B1
|
|
suggested by anil some time ago.
|
|
|
|
thus it really needs to deal with the shared irqs of these devices.
This change will register two interrupts for gpioN interrupts, one at the
highest ipl and one lowest ipl. This will allow the interrupt code above
to correcly mask the interrupts generated from all gpio devices.
ok uwe@
|
|
|
|
"com at pcmcia" in RAMDISK as a workaround.
|
|
|
|
spread a few dma_sync calls in the completion sequence;
minor cleanups.
marco@ ok
|
|
|
|
apm attaches and we know what the correct state should be, also ensure that
they are set to off if the kernel apm thread fails to create.
ok toby@, marco@
|
|
|
|
|
|
|
|
for jmc@
|
