summaryrefslogtreecommitdiffstats
path: root/share
Commit message (Collapse)AuthorAgeFilesLines
* Document msize which is often needed with maddr.jb2003-09-071-0/+2
|
* Hook-up the uart(4) manpage.marcel2003-09-071-0/+1
| | | | Reminded by: bmah@
* Mdoc Review:hmp2003-09-061-3/+5
| | | | | | | | * Remove extraneous .Pp in SYNOPSIS * Remove hard sentence break * Add the AUTHORS section
* The uart(4) driver is an universal driver for various UART hardware.marcel2003-09-061-0/+115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 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>
* Change /dev/rsa0 and /dev/rwt0 references to sa0 and wt0.roam2003-09-051-5/+5
| | | | | | PR: 55925 Submitted by: Michael L. Squires <mikes@siralan.org> MFC after: 1 month
* Catch up with the hardware notes: list the supported cards.roam2003-09-051-4/+32
| | | | | | PR: 55645 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> MFC after: 1 month
* Catch up with the hardware notes: list the supported cards.roam2003-09-051-4/+39
| | | | | | PR: 55643 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> MFC after: 1 month
* Catch up with the hardware notes: list the supported Compaq controllers.roam2003-09-051-1/+3
| | | | | PR: 55641 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Document the SC_NO_SUSPEND_VTYSWITCH kernel config option.roam2003-09-051-0/+7
| | | | | PR: 55562 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* o Fix a typo in rev. 1.196: ifconfig 9 -> ifconfig 8.maxim2003-09-051-1/+1
| | | | | PR: docs/56488 Submitted by: Yoshihiko Sarumaru <mistral@imasy.or.jp>
* Correct troff usage; typo fixes.jkoshy2003-09-051-9/+9
|
* Allow the PS version of this paper to be built.jkoshy2003-09-051-1/+8
|
* Make the creation of the OpenSSL whatis(1) database conditional onru2003-09-041-0/+2
| | | | NOCRYPT and NO_OPENSSL.
* Emergency backout of rev 1.152. This is a 100% guaranteed way to totallypeter2003-09-041-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | hose your system. You end up with just about everything statically linked (except for libpam.so), which then causes all the pam users to fail. eg: login, sshd, su etc all stop working because dlopen no longer works because there is no libc.so in memory anymore. gcc passes -L/usr/lib to ld. The /usr/lib/libxxx.so symlink is *not* a compatability link. It is actually the primary link. There should be no symlinks in /lib at all. Only /lib/libXX.so.Y. peter@daintree[9:27pm]/usr/bin-104> file yppasswd yppasswd: setuid ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.1.1, dynamically linked (uses shared libs), stripped peter@daintree[9:27pm]/usr/bin-105> ldd yppasswd yppasswd: libpam.so.2 => /usr/lib/libpam.so.2 (0x280d1000) peter@daintree[9:28pm]/usr/bin-106> Note no libc.so.5. Hence libpam.so.2 has unresolved dependencies. I believe this is also the cause of the recent buildworld failures when pam_krb5.so references -lcrypto stuff etc and when librpcsvc.so references des_setparity() etc. This change could not possibly have worked, unless there are other missing changes to the gcc configuration. It won't work with ports versions of gcc either.
* As ld(1) was taught to look into /lib, there's no longer a reasonru2003-09-031-4/+0
| | | | | | | for having compatibility .so symlinks. Submitted by: obrien Reviewed by: gordon
* Fix typo in the last commit.ken2003-09-031-1/+1
| | | | | Pointed out by: njl MFC after: 3 days
* Move dynamic sysctl(8) variable creation for the cd(4) and da(4) driversken2003-09-034-56/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | out of cdregister() and daregister(), which are run from interrupt context. The sysctl code does blocking mallocs (M_WAITOK), which causes problems if malloc(9) actually needs to sleep. The eventual fix for this issue will involve moving the CAM probe process inside a kernel thread. For now, though, I have fixed the issue by moving dynamic sysctl variable creation for these two drivers to a task queue running in a kernel thread. The existing task queues (taskqueue_swi and taskqueue_swi_giant) run in software interrupt handlers, which wouldn't fix the problem at hand. So I have created a new task queue, taskqueue_thread, that runs inside a kernel thread. (It also runs outside of Giant -- clients must explicitly acquire and release Giant in their taskqueue functions.) scsi_cd.c: Remove sysctl variable creation code from cdregister(), and move it to a new function, cdsysctlinit(). Queue cdsysctlinit() to the taskqueue_thread taskqueue once we have fully registered the cd(4) driver instance. scsi_da.c: Remove sysctl variable creation code from daregister(), and move it to move it to a new function, dasysctlinit(). Queue dasysctlinit() to the taskqueue_thread taskqueue once we have fully registered the da(4) instance. taskqueue.h: Declare the new taskqueue_thread taskqueue, update some comments. subr_taskqueue.c: Create the new kernel thread taskqueue. This taskqueue runs outside of Giant, so any functions queued to it would need to explicitly acquire/release Giant if they need it. cd.4: Update the cd(4) man page to talk about the minimum command size sysctl/loader tunable. Also note that the changer variables are available as loader tunables as well. da.4: Update the da(4) man page to cover the retry_count, default_timeout and minimum_cmd_size sysctl variables/loader tunables. Remove references to /dev/r???, they aren't used any longer. cd.9: Update the cd(9) man page to describe the CD_Q_10_BYTE_ONLY quirk. taskqueue.9: Update the taskqueue(9) man page to describe the new thread task queue, and the taskqueue_swi_giant queue. MFC after: 3 days
* CardBus instead of Cardbus. Add I/O Data WN-AG/CB and Prixim Skylineimp2003-09-012-12/+19
| | | | | | | 4030 cards. Special Thanks: shigeru yamamoto-san for the kind donation of I/O Data and other wireless cards
* Catch up my(4) with hardware notes by adding Myson MTD89X to list ofsimon2003-08-311-0/+2
| | | | | | | | supported devices. Submitted by: Lukas Ertl <l.ertl@univie.ac.at> PR: docs/56244 Confirmed by: driver source code
* Whitespace diff reduction between bsd.prog.mk and bsd.lib.mk outputs.ru2003-08-312-2/+19
|
* - Update the page title to include information about which cardssimon2003-08-291-3/+18
| | | | | | | | | are supported by the driver. - Use a list to specify which cards are supported. - Add the 3c592/3c597 EISA cards to the list of supported cards. PR: docs/56086 (based on) Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* document various NO* optionsphk2003-08-291-0/+29
|
* Limit testing for an up-to-date version of make(1) to the world andmarcel2003-08-281-0/+10
| | | | | | | | | | | | | | | | | | | | buildworld targets by default, but allow it to be done for all user targets by introducing a boolean option, named ALWAYS_CHECK_MAKE. This change is by no means perfect and I don't even want to claim this to be a solution. It does however address the fact that not everybody likes to see make(1) rebuilt simply because the regression test failed for some reason or other, including pilot error. It therefore serves the purpose of keeping the crowd happy until we have something better or simply reached a compromise. The reasons for changing the default behaviour are: o It avoids a negative, possibly non-intuitive option, o It's according to POLA and fond of feet, o Only buildworld is documented to do its best to be successful at reasonably cost. Reviewed by: gad, imp, obrien, peter
* Add a warning describing at least one circumstance where cvsup can hosenjl2003-08-251-0/+24
| | | | | | a local branch. Text from an email from jdp@ Reported by: simon
* Sort the lists of supported devices. No other content changes.bmah2003-08-251-10/+10
|
* In the lists of supported devices, remove "The" from the names ofbmah2003-08-251-10/+10
| | | | | devices and capitalize the words "Gigabit", "Ethernet", and "adapter" consistently.
* Catch up ti(4) with hardware notes.bmah2003-08-251-0/+2
| | | | | PR: 55637 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Add a few PC98-specific (?) devices, from the hardware notes.bmah2003-08-241-0/+2
|
* Sort device list, no other content changes.bmah2003-08-241-8/+8
|
* Add a few more PC98-specific instances of fe(4) devices, obtained frombmah2003-08-241-0/+11
| | | | the hardware notes.
* fix short weekday names in zh_CN.*ache2003-08-232-14/+14
| | | | | PR: 55895 Submitted by: Kang Liu <liukang@bjpu.edu.cn>
* Add a section on maintaining a local branch in CVS.njl2003-08-221-1/+31
| | | | MFC after: 1 day
* Fix ascii compatibilityache2003-08-211-15/+14
| | | | Submitted by: Liu Kang <liukang@bjpu.edu.cn>
* Add VT6105/VT6105M Rhine III to the list of supported chips. [1]simon2003-08-211-3/+4
| | | | | | | | | | Change the manual page title to use the device family name (Rhine), since the list of supported device id's won't fit on one line anymore. Submitted by: Lukas Ertl <l.ertl@univie.ac.at> (based on) [1] PR: docs/55639 (based on) [1] Confirmed by: driver source code [1] MFC after: 3 days
* Hook up repo-copied mac_none.4 to mac_stub.4.rwatson2003-08-213-14/+22
| | | | | | | | | | Update mac_none to reflect change in role; xref mac_stub. Update mac_stub to reflect name change, arrival in 5.1; xref mac_none. Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Add FreeBSD 5.1 and BSD/OS 5.0 to the family tree.murray2003-08-211-12/+16
|
* Catch up ep(4) with the hardware notes.simon2003-08-211-2/+22
| | | | | | | Submitted by: Lukas Ertl <l.ertl@univie.ac.at> PR: docs/55659 Confirmed by: driver source code and pccard.conf MFC after: 3 days
* Catch up fe(4) with the hardware notes.simon2003-08-211-1/+22
| | | | | | | Submitted by: Lukas Ertl <l.ertl@univie.ac.at> PR: docs/55636 Confirmed by: driver source code and pccard.conf MFC after: 3 days
* Add the SmartBridges SmartLink to the list of supported devices.simon2003-08-211-1/+2
| | | | | | | Submitted by: Lukas Ertl <l.ertl@univie.ac.at> PR: docs/55644 Confirmed by: driver source code MFC after: 3 days
* Write the short and long version of the monthmtm2003-08-201-50/+24
| | | | | | | names in Amharic instead of English. Also, remove some extra names I had previously considered including. They don't make sense since the calendar names don't match up.
* Add the IP_ONESBCAST option, to enable undirected IP broadcasts to be sent onbms2003-08-201-0/+41
| | | | | | | | | | specific interfaces. This is required by aodvd, and may in future help us in getting rid of the requirement for BPF from our import of isc-dhcp. Suggested by: fenestro Obtained from: BSD/OS Reviewed by: mini, sam Approved by: jake (mentor)
* Use PC Card instead of other variants in the driver man pages.imp2003-08-206-12/+12
|
* Catch up dpt(4) manpage with Hardware Notes (and RELENG_4 manpage?!?).bmah2003-08-191-0/+2
| | | | | PR: 55530 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Catch up asr(4) with hardware notes.bmah2003-08-191-0/+2
| | | | | PR: 55531 Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
* Add the manual page for the sab(4) driver. Driver code was originallybms2003-08-181-0/+78
| | | | | | | | obtained from NetBSD. This is the OpenBSD version of the manual page with a few fixes. Approved by: jake (mentor) Obtained from: OpenBSD
* Fix typo.obrien2003-08-181-1/+1
| | | | Submitted by: Ulrich Spoerlein <q@uni.de>
* When creating .so symlinks, use SHLIBDIR instead of LIBDIR so symlinksgordon2003-08-171-3/+2
| | | | | | | are created in the correct location. Always make them. For libraries that live in /lib, this causes a /lib/libfoo.so and a compatibility /usr/lib/libfoo.so to be created. We may want to drop the /usr/lib/libfoo.so symlink at some future point.
OpenPOWER on IntegriCloud