summaryrefslogtreecommitdiffstats
path: root/sys/tools
Commit message (Collapse)AuthorAgeFilesLines
* $Id$ -> $FreeBSD$ (some mangled and/or hidden ones)peter1999-08-282-2/+2
|
* $Id$ -> $FreeBSD$peter1999-08-283-3/+3
|
* This commit adds support for the NetBSD MII abstraction layer andwpaul1999-08-212-0/+294
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MII-compliant PHY drivers. Many 10/100 ethernet NICs available today either use an MII transceiver or have built-in transceivers that can be programmed using an MII interface. It makes sense then to separate this support out into common code instead of duplicating it in all of the NIC drivers. The mii code also handles all of the media detection, selection and reporting via the ifmedia interface. This is basically the same code from NetBSD's /sys/dev/mii, except it's been adapted to FreeBSD's bus architecture. The advantage to this is that it automatically allows everything to be turned into a loadable module. There are some common functions for use in drivers once an miibus has been attached (mii_mediachg(), mii_pollstat(), mii_tick()) as well as individual PHY drivers. There is also a generic driver for all PHYs that aren't handled by a specific driver. It's possible to do this because all 10/100 PHYs implement the same general register set in addition to their vendor-specific register sets, so for the most part you can use one driver for pretty much any PHY. There are a couple of oddball exceptions though, hence the need to have specific drivers. There are two layers: the generic "miibus" layer and the PHY driver layer. The drivers are child devices of "miibus" and the "miibus" is a child of a given NIC driver. The "miibus" code and the PHY drivers can actually be compiled and kldoaded as completely separate modules or compiled together into one module. For the moment I'm using the latter approach since the code is relatively small. Currently there are only three PHY drivers here: the generic driver, the built-in 3Com XL driver and the NS DP83840 driver. I'll be adding others later as I convert various NIC drivers to use this code. I realize that I'm cvs adding this stuff instead of importing it onto a separate vendor branch, but in my opinion the import approach doesn't really offer any significant advantage: I'm going to be maintaining this stuff and writing my own PHY drivers one way or the other.
* Add a vnode argument to VOP_BWRITE to get rid of the last vnodemckusick1999-06-161-46/+1
| | | | | operator special case. Delete special case code from vnode_if.sh, vnode_if.src, umap_vnops.c, and null_vnops.c.
* Declare static __inline functions as __inline in their forwardbde1999-02-281-13/+8
| | | | | | | | declaration. Fixed some comments. Fixed a staticization botch.
* Make the vnode opv vector construction fully dynamic. Previously wepeter1998-11-101-38/+2
| | | | | | | | | | | | | | | | | | | | leaked memory on each unload and were limited to items referenced in the kernel copy of vnode_if.c. Now a kernel module is free to create it's own VOP_FOO() routines and the rest of the system will happily deal with it, including passthrough layers like union/umap/etc. Have VFS_SET() call a common vfs_modevent() handler rather than inline duplicating the common code all over the place. Have VNODEOP_SET() have the vnodeops removed at unload time (assuming a module) so that the vop_t ** vector is reclaimed. Slightly adjust the vop_t ** vectors so that calling slot 0 is a panic rather than a page fault. This could happen if VOP_something() was called without *any* handlers being present anywhere (including in vfs_default.c). slot 1 becomes the default vector for the vnodeop table. TODO: reclaim zones on unload (eg: nfs code)
* VOP_STRATEGY grows an (struct vnode *) argumentjulian1998-07-041-31/+1
| | | | | | as the value in b_vp is often not really what you want. (and needs to be frobbed). more cleanups will follow this. Reviewed by: Bruce Evans <bde@freebsd.org>
* Use __inline instead of inline to prevent pedantic compiler warnings.bde1997-12-191-4/+4
|
* Removed unused #includes.bde1997-10-281-2/+1
|
* 3 lines of code and updates to a number of comments.phk1997-09-101-1/+11
| | | | | Reviewed by: phk Submitted by: Terry Lambert <tlambert@primenet.com>
* Back out part 1 of the MCFH that changed $Id$ to $FreeBSD$. We are notpeter1997-02-221-1/+1
| | | | ready for it yet.
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Another mega commit to staticize things.phk1995-12-141-3/+3
|
* Don't #include vm stuff in vnode_if.[ch]. Enough vm stuff (abde1995-12-061-6/+1
| | | | | | | | | single typedef) is now declared in <sys/types.h>. This is the first of 4 commits that will remove some excessive includes of vm*.h and user.h. The total speed improvement isn't as large as I first thought. `make depend; make' for LINT only improved from 2180 seconds to 2108 seconds user time.
* Second batch of cleanup changes.phk1995-10-291-2/+2
| | | | | This time mostly making a lot of things static and some unused variables here and there.
* Generate prototypes for VOP functions. I decided to keep the old-stylebde1995-09-111-1/+26
| | | | | | definitions even though the functions are inline. If vnode_if.h was compiled by a non-ANSI compiler, then `inline' would be defined away, so vnode_if.h might compile correctly.
* Added VOP_GETPAGES/VOP_PUTPAGES and also the "backwards" block countdyson1995-09-041-1/+6
| | | | for VOP_BMAP. Updated affected filesystems...
* Removed my special-case hack for VOP_LINK and fixed the problem with thedg1995-08-011-39/+1
| | | | | | | wrong vp's ops vector being used by changing the VOP_LINK's argument order. The special-case hack doesn't go far enough and breaks the generic bypass routine used in some non-leaf filesystems. Pointed out by Kirk McKusick.
* The generated VCALL always uses the first vp which in the case of /link/dg1995-07-071-1/+39
| | | | | | | | | might not be handled by the same FS as the directory (e.g. special device files)...so it must be special-cased. This bug is seen when doing "ln /dev/console /dev/foo" or equivilent and first appeared after I fixed the argument order of VOP_LINK. YUCK! There really needs to be a way of specifying what vp to use in the VCALL; doing this could fix the strategy and bwrite special-cases, too.
* Added $Id$dg1994-08-021-0/+1
|
* BSD 4.4 Lite Kernel Sourcesrgrimes1994-05-241-0/+433
OpenPOWER on IntegriCloud