Age | Commit message (Collapse) | Author |
|
- Rename one of the existing Smart Array entries (0x3237) to reflect
its name as being a Smart Array E500 adapter.
From FreeBSD
- Add a Smart Array E200i PCI id missing from ciss_pci.c, although it
has been in pcidevs for some time.
|
|
|
|
- Rename one of the existing Smart Array entries (0x3237) to reflect
its name as being a Smart Array E500 adapter.
From FreeBSD via Brad, ok jsg@
|
|
condition to determine crtical status for the sensor and apm. This makes
the critical status correspond to the flashing red battery led.
Furthermore, use ISSET macros and friends.
|
|
It provides an Ethernet transport typically over EDGE or 3G on
cellphones similar to what cdce(4) does on other phones. It is
likely to work with most of HTC's recent and coming Android based
phones but a bunch of other things (phones in particular) may use
it.
Started by me; brought to a working state by Jonathan Armani and
Fabien Romano over the past week, with some input and additions
from me.
Tested on i386 and macppc by me (HTC Hero), amd64 by Jonathan and
Fabien (HTC Hero), and by gilles@ (HTC Magic) on i386 or amd64.
It still has a few kinks to work out, but it works well enough that
I can commit this over my HTC Hero.
`commit it!' deraadt
|
|
- properly spell 'usefulness'
|
|
for the interrupt. Makes the vmstat -i output similar to what we see on
i386.
ok deraadt@, krw@
|
|
also protect the flushing of the deferred packet queue in clone_destroy
with the right spls. noticed by claudio@
|
|
|
|
|
|
ok deraadt@
|
|
handlers now checks that the spl the isr was established at is the same as
the one passed to splassert. this lets you check that isrs dont enter code
that have insufficient protection if entered from process context.
ok kettenis@
|
|
and get interrupts by otto@, no further testing due to lack of IR devices.
|
|
Currently unable to change video modes or provide any form of acceleration,
so you are stuck in a 640x400x8 mode, but at least people scared of serial
consoles will get a chance to use their Fuloongs now.
Tested by otto@ (early developments) and jasper@ (final version)
|
|
upon stumbling on a BAR which value is zero.
Found the hard way by kurt@, ok kettenis@
|
|
longers assumes all requested mappings fit in the three 64MB PCILO windows,
but will instead check whether the requested mappings can be provided by
PCILO regions or PCIHI regions (and on 2F-based systems, making sure we
only use addresses which get properly routed from CPU to PCI within the
2F crossbar).
This in turn requires early console code to abide the bus_space rules and
get its resources from bus_space_map() rather than doing PCI BAR arithmetic
by itself.
No functional change on Lemote Yeeloong and Gdium Liberty; on Lemote Fuloong
2F this allows BAR set up in PCIHI space by PMON to be mapped by kernel code
without having to compensate for the PCILO offset.
|
|
ok.
Stops cdio(1) from printing bogus TOC info.
ok marco@ beck@
|
|
|
|
ok marco deraadt
|
|
processors can display correct data. Now cpu1 on octane is correctly
reported in dmesg.
|
|
|
|
|
|
be decoupled from the nominal processor speed.
While there, make sure delay() gets a proper delay constant if invoked before
cpu0 attaches (how could I miss that when introducing struct cpu_hwinfo?!?)
|
|
|
|
devices. Original code was inspired by/copied/stolen from the macppc
apm(4), which has different semantics for battery life while charging.
|
|
"we dont' know"
|
|
generic part, ykbec(4) provides the device specific parts. Other
battery/power status drivers can easily hook to adb(4). With help
from miod@; ok matthieu@ miod@ jasper@
|
|
anyway, it's not worth fixing. Bump version number.
ok deraadt@
|
|
|
|
|
|
when computing multicast hash.
From Brad via FreeBSD
|
|
Reported by and fix tested by peters at schwertfische dot de.
|
|
what to tell the user. Silences cdio and cdrecord while probing
media.
ok dlg@ marco@ deraadt@
|
|
buffer cache first, so that all sorts of gibble doesn't end up on the disk.
ok kettenis (for the sparc/sparc64 ones, at least)
|
|
|
|
|
|
just not there.
ok jakemsr@ drahn@
|
|
Why this code, which must be executed, is not failing on disk is an utter
mystery. More investigation needed.
|
|
|
|
allowed to match on old gdium artwork, as newer artwork have nothing
connected to the usb pins, and this causes the empty bus probe to stall the
boot a few seconds.
|
|
|
|
ok deraadt@
|
|
capitilization for names.
from brad, thanks!
|
|
from Alexandr Shadchin <alexandr.shadchin at gmail.com>, thanks!
|
|
from Alexandr Shadchin <alexandr.shadchin at gmail.com>, thanks!
|
|
changed from 16 bytes to 2 bytes.
no binary change
|
|
|
|
from Windows driver via http://www.wikidrivers.com/wiki/Ralink_RT2870
|
|
|
|
|