| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
compatibility routine, go ahead and accept that as 'success'. A
properly written compatible driver should return < 0 for both the
compat match and compat probe routines, so this will wind up doing the
right thing.
|
| |
|
|
|
|
|
| |
reach me directly), but more importantly, breaks compiles on
non-FreeBSD platforms.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/usr/include/osreldate.h doesn't exist on the system. While this
could be worked around by saying something like 'make includes
OSLRELDATE=0' when this file doesn't exist, it is just as easy to
provide a fallback when the file we know we depend on doesn't exist.
While this doesn't make all targets work w/o a
/usr/include/osreldate.h, because some of the FreeBSD bootstrap tools
use this file. 'make includes' however does work.
Noticed by: peter, obrien (and likely others)
Pointy hat to: imp (for suggesting a method that depended on /usr/include)
|
| |
|
| |
|
|
|
|
| |
Requested by: bde
|
|
|
|
|
|
| |
comment and thus compiled.
Submitted by: bde
|
|
|
|
| |
Cosmetics.
|
| |
|
|
|
|
|
|
| |
This will get rid of the warnings issued at shutdown (that seems to
worry alot of users), but will also no flush cache on lots of
devices that can, but doesn't set the right support bits...
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
devices and capitalize the words "Gigabit", "Ethernet", and "adapter"
consistently.
|
|
|
|
|
| |
PR: 55637
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
|
|
|
|
|
|
|
| |
Without this option it is not possible to omit the driver from the
configuration file and successfully build a kernel.
This option is specific to alpha.
|
|
|
|
|
|
|
|
| |
implementations. Use those on platforms that don't have MD
headers. Remove the ia64 MD header. We're going to use the C
implementation there.
Suggested by: bde
|
|
|
|
|
|
|
| |
its mbufs aligned on TX.
PR: 53656, 42714
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
here. Trim devices from the remaining fe(4) section as the manpage
now covers all of them.
While here, remove a comment that instructs developers on how to add
specific instances of devices, since we're moving away from that now.
|
| |
|
|
|
|
| |
the hardware notes.
|
|
|
|
| |
respected or at least shut the warning up.
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by: Tor Egge <Tor.Egge@cvsup.no.freebsd.org>
|
|
|
|
| |
Also some minor style cleanups.
|
|
|
|
| |
Also some minor style cleanups.
|
|
|
|
| |
Also some minor style cleanups.
|
| |
|
|
|
|
| |
Use these in our i386, amd64, and alpha platforms.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Restructure the way ATA/ATAPI commands are processed, use a common
ata_request structure for both. This centralises the way requests
are handled so locking is much easier to handle.
The driver is now layered much more cleanly to seperate the lowlevel
HW access so it can be tailored to specific controllers without touching
the upper layers. This is needed to support some of the newer
semi-intelligent ATA controllers showing up.
The top level drivers (disk, ATAPI devices) are more or less still
the same with just corrections to use the new interface.
Pull ATA out from under Gaint now that locking can be done in a sane way.
Add support for a the National Geode SC1100. Thanks to Soekris engineering
for sponsoring a Soekris 4801 to make this support.
Fixed alot of small bugs in the chipset code for various chips now
we are around in that corner anyways.
|
|
|
|
| |
Submitted by: Pavlin Radoslavov <pavlin@icir.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
bus tag is to allow bus space accesses prior to having newbus
fully initialized, such as would be the case for console drivers.
Since barriers are a fundamental part of bus space accesses, not
allowing them on fake tags would defeat the purpose of these tags.
We use the barrier function normally associated with nexus. This
is the barrier used when subordinates haven't defined a barrier
themselves.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o The following additional configuration attributes of a jail can be
controlled from rc.conf:
- mounting devfs(5)
- mounting fdescfs(5)
- mounting procfs(5)
- custom devfs(8) ruleset
If no ruleset is specified, the default jail ruleset is used.
o The output of executing /etc/rc in the jail is now redirected
to /dev/null. Instead, the hostname of the jail is echoed if
the jail(8) command exited successfully. If the output is wanted
it can probably be redirected to a file (/var/run/$jail maybe)
instead of /dev/null.
Submitted by: Scot W. Hetzel <hetzels@westbend.net>
with modifications by Jens Rehsack <rehsack@liwing.de>
and me.
|
|
|
|
|
|
| |
from 3770 real down to 1250 real.
Submitted by: jake
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
support stripped out and minimally renamed to owi. This driver
attaches to lucent cards only. This is designed to aid in the testing
of fixes to the wi driver for lucent cards. It is supported only as a
module (you cannot compile it into your kernel). You cannot have the
wi driver in your kernel (or loaded as a moudle) to use the owi
module.
I've not connected it to build, as this module is currently for
debugging purposes. This is for developers only at the present time.
If we can't get lucent support fixed by 5.2 code freeze, then we'll
re-evaulate this support level. Please use this to fix the lucent
support in dev/wi. This will be removed from the system when lucent
support has been fixed in dev/wi.
Note to developers: Do not connect this to the build, make it possible
to build into the kernel or otherwise 'integrate' this into system
without checking with me first. This is for debugging purposes only.
If this doesn't work for you, I don't want to hear about it unless you
are fixing the wi driver :-)
|
| |
|
|
|
|
|
| |
- Use the values in the video info for the font size and width instead
of second guessing.
|