| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add cpu_rootconf and cpu_dumpconf so that configuring these
two devices can be better controlled by the MI configuration
code.
machdep.c:
MD initialization code for the new callout interface.
trap.c:
Add support for printing out whether cam interrupts are masked
during a panic.
|
|
|
|
| |
Clean up the match routines so that they return const char *
|
| |
|
| |
|
|
|
|
| |
Guard against scheduling more than one callout.
|
|
|
|
|
| |
Add kern/subr_autoconf.c as a standard file as it contains the bulk of
the code for performing interrupt driven configuration.
|
| |
|
|
|
|
|
|
| |
look too great with 'more' etc.
Approved by: dyson (with a minor grumble :-)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
plus the previous changes to use the zone allocator decrease the useage
of malloc by half. The Zone allocator will be upgradeable to be able
to use per CPU-pools, and has more intelligent usage of SPLs. Additionally,
it has reasonable stats gathering capabilities, while making most calls
inline.
|
|
|
|
|
|
| |
the normal CS4326 except that it's had it's ID's tweaked for some reason)
Also mark the device as alive in the attach routine so that the pnp system
doesn't think the attach failed.
|
| |
|
|
|
|
| |
kern_descrip.c when the user does an fcntl(.., F_SETFL, ...).
|
|
|
|
| |
via PT_INTERP (usually /usr/libexec/ld-elf.so.1).
|
|
|
|
|
|
|
| |
possible. (This is not really a typographical improvement in the
case of the K6 it seems, but AMD appearantly want it too look
that way). Also if bootverbose, dump some more info about the
chip.
|
|
|
|
|
|
|
|
|
|
|
| |
of multiple PCI IDE controllers(Dyson), and some updates and cleanups from
John Hood, who originally made our IDE DMA stuff work :-).
I have run tests with 7 IDE drives connected to my system, all in DMA
mode, with no errors. Modulo any bugs, this stuff makes IDE look
really good (within it's limitations.)
Submitted by: John Hood <cgull@smoke.marlboro.vt.us>
|
|
|
|
|
| |
Other ways around this might be to #define KERNEL in dset.c for the
"i386/isa/pnp.h" include.
|
| |
|
|
|
|
| |
revisions 1.60 and 1.182, respectively.
|
|
|
|
|
|
|
|
| |
rather than extracting the diff from Mark's patch, but it turns out that
I was freeing one allocation twice due to a previous cut/paste braino.
My botch, not Mark's.
Pointed out by: Mark Valentine <mv@pobox.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
internal modems. Currently detects a USR modem, and a couple Supra
modems... vendor id's for sio capabile cards welcomed...
document new option EXTRA_SIO that will increase sio's internal data
structures to support X more serial ports... these are used by the
PnP part of sio for attaching... If you don't have it specified, it
will default to 2... This is defaulted to 0 if you don't have PnP
compiled into your kernel...
also document that if you set the PnP flags (pnp x flags y) to 0x1 that
the modem will be refused to be recognized by the sio driver... this
is for people that want the traditional isa driver to probe and attach
the modem... (for keeping legacy sio numbering)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
these structs for conflics...
it still exist that two PnP cards can colide, but this is up to the user
to make sure it doesn't happen...
other modifications to pnp.c to format output properly, and hide more
output behind bootverbose flag...
fix some bugons in pnp.h that would of made it difficult for inclusion
in external programs (for import of pnpinfo)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. ffs_alloc() actually allowed writing one block less one frag (normally
7 frags or 7/8 blocks) beyond the limit.
2. freebufspace() gives the free space in frags, but `size' is in bytes,
so the change results in approximately `size' fragments too many being
reserved.
3. ffs_realloccg() has the same bug but wasn't changed.
PR: 3398
Submitted by: bde
Eyeballed by: phk
|
| |
|
|
|
|
|
|
|
| |
a trap.
PR: 3104
Reviewed by: phk
Submitted by: Dan Walters hannibal@cyberstation.net
|
|
|
|
|
|
| |
PR: 3398
Reviewed by: phk
Submitted by: Wolfram Schneider <wosch@apfel.de>
|
|
|
|
|
|
| |
freed.
Submitted by: Mark Valentine <mark@linus.demon.co.uk>
|
| |
|
|
|
|
|
|
| |
hide more verbosity behind bootverbose
make it so that it doesn't emit as many warnings durning compiling...
|
| |
|
|
|
|
|
|
|
|
| |
that I've done this properly, it does work though :) )...
a few minor fixes to code
part-Submitted-by: Luigi
|
| |
|
|
|
|
|
|
| |
device).
Submitted by: Andre.Albsmeier@mchp.siemens.de (Andre Albsmeier)
|
|
|
|
|
|
|
|
| |
number of dma overruns/underruns for systems under heavy dma load.
As a side effect, broken enhanced floppy controllers that sometimes
don't detect dma overruns/underruns will give less errors.
Reviewed by: j@uriah.heep.sax.de (J Wunsch)
|
|
|
|
| |
revisions 1.59 and 1.101, respectively.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sorted some declarations.
Fixed missing __P(())'s.
Removed `timeout_func_t (pointer to timeout function) typedef. It was
mainly used in bogus casts. The more useful `timeout_t' (timeout function)
typedef should be used instead.
Cleaned up callout declarations and comments.
|
|
|
|
|
|
|
|
|
|
|
| |
extern in <sys/malloc.h> and it should not have been staticized for
the !(KMEMSTATS || DIAGNOSTIC) case.
Fixed the !(KMEMSTATS || DIAGNOSTIC) case. The MALLOC() and FREE()
macros are evil, but code generally doesn't allow for this and some code
involving else clauses did not compile.
Finished staticization.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
or a partition is larger than the slice.
Now `disklabel -Brw sdX auto' should fail properly on sliced disks
without partition of type 165, e.g., on zip disks with the factory
default formatting. Previously it set a bogus in-core label for
the compatibility slice and used this to corrupt the MBR (the slice
has offset 0 and size 0, but setting the label in effect corrupted
its size to nonzero).
`disklabel -Brw sdX auto' already failed properly on normally (not
dangerously dedicated) sliced disks _with_ partition of type 165,
because the compatibility slice has a nonzero offset so the MBR
remained inaccessible when the size was corrupted.
This bug only affected in-core labels. On-disk labels are checked
carefully when they read and written.
|
|
|
|
| |
I'm going to try migrate back, while keeping the newer code.
|
|
|
|
| |
Stylistic nits and a blunder, from bde.
|
|
|
|
|
|
|
| |
Hide the bogus FDC ``chip type'' display behind a (mostly) undocumented
option, since people started to trust the bogus claim. Once we're going
to handle 2.88 MB controllers, we have to redo the chip detection, by
now just leave it hidden.
|
|
|
|
| |
Reviewed by: wollman
|
|
|
|
|
|
|
|
|
| |
A couple of stylistic nits from Bruce.
If your libc contains version 1.11 or 1.12 of getcwd.c, (ie: if
you recompiled libc one of the last couple of days):
>>> Recompile LIBC before you boot a new kernel <<<
A new libc will deal with both old and new kernels.
|