summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Introduce arguments the standard way. In .Ar command ..., ... is not ancharnier2003-09-071-4/+4
| | | | argument, command is.
* Remove duplicate #include. Do not \n terminate errx() arg.charnier2003-09-071-2/+3
|
* Add FBSDID. Use errx() instead of fprintf()/exit(). Call exit() at the endcharnier2003-09-071-92/+44
| | | | of usage() and make the code aware of that.
* The .Fn function. Dot terminate sentences. Use .Bd/.Ed instead of .Ar tocharnier2003-09-071-25/+35
| | | | emphasize examples of source definition file.
* clock.c:bde2003-09-073-5/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | Quick fix for calling DELAY() for ddb input in some (atkbd-based) console drivers. ddb must not use any normal locks, but DELAY() normally calls getit() which needs clock_lock. One problem with using normal locks in ddb is that deadlock is possible, but deadlock on clock_lock is unlikely becaluse clock_lock is bogusly recursive, apparently just to hide the problem of ddb using it. The i8254 clock hardware has mostly write-only registers so it is important for it to use a lock that gives exclusive access. (atkbd hardware is also unfriendly to reentrant software but that problem is more local and already solved.) I mostly saw the symptoms of the bug caused by unlocking in getit() running cpu_unpend(). cpu_unpend() should not be called while in ddb and Debugger() calls for failing assertions about this caused a breakpoint within ddb. ddb must also not call getit() because ddb may be being used to step through clock initialization code that has stopped or otherwise mangled the clock. If the clock is stopped, then getit() always returns the same value and DELAY() takes forever if it trusts getit(). The quick fix is implement DELAY(n) as (n * timer_freq / 1000000) inb(0x84)'s if ddb is active. machdep.c: Don't permit recursion on clock_lock.
* - No need to create libfoo.so -> libfoo.so.X symlinks in /lib,ru2003-09-072-3/+9
| | | | | | | | | | | | as it was decided that our toolchain will revert to looking for libraries in /usr/lib only. - Make /usr/lib/libfoo.so -> /lib/libfoo.so.X symlinks absolute so that they still work if /usr is symlinked. - Remove stale /usr/lib/libfoo.so.X libraries during install. Discussed with: gordon, obrien, peter
* Replace a reference to non existant mount_ffs(8) by a reference to mount(8).charnier2003-09-071-1/+1
|
* Moved stop/start code for other CPUs to near the beginning/end ofbde2003-09-071-41/+41
| | | | | | | kdb_trap(). Stopping the other CPUs acts like locking them out, but it wasn't done early enough or held long enough to prevent concurrent accesses to shared data. In particular, the saved regs could be clobbered.
* Eliminate the need in uname(1) during install.ru2003-09-071-2/+2
|
* Restored non-egregious casts so that this file compiles on i386's withbde2003-09-071-3/+4
| | | | 64-bit longs again.
* Only evaluate CVS version once, when necessary.ru2003-09-071-3/+3
| | | | Eliminates the need in sed(1) during install.
* Only evaluate CVS version once, when necessary.ru2003-09-071-4/+3
| | | | Eliminates the need in sed(1) during install.
* Restored a non-egregious cast so that this file compiles on i386'sbde2003-09-071-1/+1
| | | | | | | | | | | | | with 64-bit longs again. This was fixed in rev.1.42 but the fix rotted non-fatally in rev.1.105 and fatally in rev.1.137. Many more non-egregrious casts are strictly required for conversions from semi-opaque types to pointers, but we avoid most of them by using types that are almost certain to be compatible with uintptr_t for representing pointers (e.g., vm_offset_t). Here we don't really want the u_longs, but we have them because a.out.h and its support code doesn't use typedefs (it uses unsigned in V7 and unsigned long in FreeBSD) and is too obsolete to fix now.
* Implement sed(1) commands using the make(1)'s RE variable modifier.ru2003-09-071-3/+3
| | | | (This almost eliminates the need of a sed(1) during installworld.)
* Don't escape names in MLINKS: this won't work with bsd.man.mk,v 1.53.ru2003-09-071-1/+1
|
* Return EINVAL if the contested bit is not set on the umtx passed totjr2003-09-071-1/+2
| | | | _umtx_unlock() instead of firing a KASSERT.
* Fix testing of arith_assign() value for $((a=15)).schweikh2003-09-071-1/+1
| | | | Submitted by: Enache Adrian <enache@rdslink.ro>
* Use KERN_PROC_PROC instead of KERN_PROC_ALL when enumerating processes sotjr2003-09-071-7/+4
| | | | | that we kill each process once, not once for every thread it owns. This avoids "No such process" warnings when killing threaded processes.
* make sure we really don't have a tty when installing rules. This preventsjmg2003-09-071-3/+3
| | | | | | | a flush command from asking a question (you can't see): If there is no tty associated with the process, this is implied. MFC after: 1 day
* Add support for the Coda 6.x venus<->kernel interface. This extendstjr2003-09-0727-686/+806
| | | | | | | | | | | | | | FIDs to be 128-bits wide and adds support for realms. Add a new CODA_COMPAT_5 option, which requests support for the old Coda 5.x interface instead of the new one. Create a new coda5.ko module that supports the 5.x interface, and make the existing coda.ko module use the new 6.x interface. These modules cannot both be loaded at the same time. Obtained from: Jan Harkes & the coda-6.0.2 distribution, NetBSD (drochner) (CODA_COMPAT_5 option).
* Now that PC98 has it's own MD file, use uart_cpu_${MACHINE}.c andmarcel2003-09-071-2/+1
| | | | not uart_cpu_${MACHINE_ARCH}.c.
* MFp4: Revamped GENERIC (and hints). This is some much more pleasantmarcel2003-09-072-118/+84
| | | | to look at...
* Replace the ttyd[0-3] entries with ttyu[0-3]. The former are themarcel2003-09-071-8/+8
| | | | | | device special files created by sio(4). The latter are the device special files created by uart(4). As of this moment sio(4) is not supported on ia64... by me, that is :-)
* Replace sio(4) with uart(4). Remove the sio(4) hints and only addmarcel2003-09-072-9/+5
| | | | | those hints used by uart(4) for the determination of the serial console in the absence of the HCDP table.
* msync(2) should be declared MP-safe.alc2003-09-076-7/+7
|
* Fix build breakage caused by the inclusion of <ddb/ddb.h> whilemarcel2003-09-071-1/+2
| | | | | | building a module. Inclusion of option files (opt_ddb.h in this case) is not possible for modules. The inclusion of opt_ddb.h in this header is questionable.
* Turning on warning for static LDT allocation.davidxu2003-09-071-4/+0
|
* Add proper pc98 MD files. Add a commented out cbus attachment forimp2003-09-072-1/+3
| | | | | uart because that depends on the cbus implementation that nyan-san and I came up with after the CBUG meeting and not yet ready for the tree.
* add i8251imp2003-09-071-0/+1
|
* Better stab at MD code for pc98. The 8251 stuff is a total lieimp2003-09-074-0/+976
| | | | | | (ns8250 copied and s/ns8250/i8251/g), but there for linkage purposes. Real code to follow, once I get past some boot issues on my pc98 boxes with recent current.
* Document msize which is often needed with maddr.jb2003-09-071-0/+2
|
* Add uart(4). Shuffle the information about sio(4) flags and optionsmarcel2003-09-071-20/+39
| | | | | so that it's clear whicfh flags/options are used by both sio(4) and uart(4) and which flags/options are specific to sio(4).
* Hook-up the uart(4) manpage.marcel2003-09-071-0/+1
| | | | Reminded by: bmah@
* Keep up with minor changes to NetBSD. Consider a variable empty whenimp2003-09-071-1/+1
| | | | | | not define. Obtained From: NetBSD (rev 1.18; sjg)
* Mdoc Review:hmp2003-09-061-3/+5
| | | | | | | | * Remove extraneous .Pp in SYNOPSIS * Remove hard sentence break * Add the AUTHORS section
* Hook-up the uart(4) driver to the build. For a detailed descriptionmarcel2003-09-0610-2/+33
| | | | | | | | | | | | | | | of what uart(4) is and/or is not see the initial commit log of one of the files in sys/dev/uart (or see share/man/man4/uart.4). Note that currently pc98 shares the MD file with i386. This needs to change when pc98 support is fleshed-out to properly support the various UARTs. A good example is sparc64 in this respect. We build uart(4) as a module on all platforms. This may break the ppc port. That depends on whether they do actually build modules. To use uart(4) on alpha, one must use the NO_SIO option.
* The uart(4) driver is an universal driver for various UART hardware.marcel2003-09-0625-0/+6017
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It improves on sio(4) in the following areas: o Fully newbusified to allow for memory mapped I/O. This is a must for ia64 and sparc64, o Machine dependent code to take full advantage of machine and firm- ware specific ways to define serial consoles and/or debug ports. o Hardware abstraction layer to allow the driver to be used with various UARTs, such as the well-known ns8250 family of UARTs, the Siemens sab82532 or the Zilog Z8530. This is especially important for pc98 and sparc64 where it's common to have different UARTs, o The notion of system devices to unkludge low-level consoles and remote gdb ports and provides the mechanics necessary to support the keyboard on sparc64 (which is UART based). o The notion of a kernel interface so that a UART can be tied to something other than the well-known TTY interface. This is needed on sparc64 to present the user with a device and ioctl handling suitable for a keyboard, but also allows us to cleanly hide an UART when used as a debug port. Following is a list of features and bugs/flaws specific to the ns8250 family of UARTs as compared to their support in sio(4): o The uart(4) driver determines the FIFO size and automaticly takes advantages of larger FIFOs and/or additional features. Note that since I don't have sufficient access to 16[679]5x UARTs, hardware flow control has not been enabled. This is almost trivial to do, provided one can test. The downside of this is that broken UARTs are more likely to not work correctly with uart(4). The need for tunables or knobs may be large enough to warrant their creation. o The uart(4) driver does not share the same bumpy history as sio(4) and will therefore not provide the necessary hooks, tweaks, quirks or work-arounds to deal with once common hardware. To that extend, uart(4) supports a subset of the UARTs that sio(4) supports. The question before us is whether the subset is sufficient for current hardware. o There is no support for multiport UARTs in uart(4). The decision behind this is that uart(4) deals with one EIA RS232-C interface. Packaging of multiple interfaces in a single chip or on a single expansion board is beyond the scope of uart(4) and is now mostly left for puc(4) to deal with. Lack of hardware made it impossible to actually implement such a dependency other than is present for the dual channel SAB82532 and Z8350 SCCs. The current list of missing features is: o No configuration capabilities. A set of tunables and sysctls is being worked out. There are likely not going to be any or much compile-time knobs. Such configuration does not fit well with current hardware. o No support for the PPS API. This is partly dependent on the ability to configure uart(4) and partly dependent on having sufficient information to implement it properly. As usual, the manpage is present but lacks the attention the software has gotten.
* Enhance puc(4) to support uart(4). This includes:marcel2003-09-067-77/+336
| | | | | | | | | | | | | | | | | | | | | | | | | o Introduce PUC_PORT_TYPE_UART so that we can attach to uart(4), o Introduce port sub-types (eg PUC_PORT_UART_NS8250, PUC_PORT_UART_Z8530) to handle different hardware and determine resource sizes. o Introduce two new IVARs: PUC_IVAR_SUBTYPE and PUC_IVAR_REGSHFT. Both are used by uart(4) to get sufficient information to talk to the HW. o Introduce PUC_FLAGS_ALTRES to tell puc(4) to try memory mapped I/O if I/O port space cannot be allocated, or vice versa. o Have ports of type PUC_PORT_TYPE_COM attach to uart(1) if attaching to sio(4) fails (due to not having the sio driver). o Put struct puc_device_description in struct puc_softc instead of having a pointer to a device description in the softc. This allows us to create device descriptions on the fly without having to use malloc() or otherwise have them staticly defined. o Move puc_find_description() from puc.c to puc_pci.c as it's specific to PCI. o Add EBUS and SBUS frontends for use on sparc64. Note that the P in puc stands for PCI, so we kinda mess things up here. It's too soon to worry about it though. We'll know what to do about it in time. NOTE: This commit changes the behaviour of puc(4) to not quieten the device probe and attach for child devices. The uart(4) driver provides additional device description that is valuable to have.
* add fast swi taskqueue spinlock to the order_list so witness doesn't complainsam2003-09-061-0/+1
| | | | Submitted by: Tor Egge <Tor.Egge@cvsup.no.freebsd.org>
* correct fast swi taskqueue spinlock name to be different from the sleep locksam2003-09-061-1/+1
| | | | Submitted by: Tor Egge <Tor.Egge@cvsup.no.freebsd.org>
* Giant is no longer required by pipe_destroy_write_buffer(). Reducealc2003-09-061-9/+7
| | | | unnecessary white space from pipe_destroy_write_buffer().
* Trim the twe(4) device list; the twe(4) manual page is more up-to-date.simon2003-09-062-26/+0
|
* Bzero the right number of bytes.phk2003-09-061-1/+1
| | | | Found by: Juergen Buchmueller <pullmoll@stop1984.com>
* Baud rate capability is `br', not `ba'.hmp2003-09-061-1/+1
| | | | | PR: docs/56426 Submitted by: FUJISHIMA Satsuki <sf@FreeBSD.ORG>
* New release notes: PIM support, amd-6.0.9, GNU Readline 4.3, GNU Sortbmah2003-09-062-0/+32
| | | | 2.1, ISC DHCP client 3.0.1rc12.
* Trim isp(4), vx(4), and stg(4) device lists.bmah2003-09-062-150/+2
|
* Catch up isp.4 manpage with hardware notes.bmah2003-09-061-0/+4
| | | | | PR: 55558 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Remove hard sentence breaks.hmp2003-09-061-9/+10
|
* Add stg(4) manpage and hook up to the section 4 manpage build.bmah2003-09-062-0/+71
| | | | | PR: 55605 Submitted by: Bob Bishop <rb@gid.co.uk>
* Trim the device lists for tl(4), aue(4), and kue(4) after recentbmah2003-09-062-312/+10
| | | | | manpage catchup updates. The nearby axe(4) and rue(4) lists appear to be in sync with the manpages so trim those too.
OpenPOWER on IntegriCloud