summaryrefslogtreecommitdiffstats
path: root/usr.sbin/sade/devices.c
Commit message (Collapse)AuthorAgeFilesLines
* Oh crud, did I ever screw the pooch! Rather than sync this with -stable,jkh1999-09-021-7/+8
| | | | | | | | | | I backed-out the changes in -current and didn't touch stable at all (I thought I had my patch order reversed, not what actually happened). AIEEE! I can't even blame the crack for this one since I broke my crack pipe a few weeks ago. I think sleep deprivation gets the blame for this one. Medal for noticing this one goes to: Jim Bloom <bloom@acm.org>
* MFC: Catch 3.2-stable sysinstall up to 4.0-current level functionality,jkh1999-09-011-8/+7
| | | | | | | bringing in DHCP support. The only thing I left out were Poul-Henning's newfs changes since I'm not sure if he's brought the rest of that support into -stable yet. If it turns out that this is the case, I'll MFC those changes too.
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* This commit adds device driver support for the Sundance Technologies ST201wpaul1999-08-211-1/+2
| | | | | | | | | | | | | PCI fast ethernet controller. Currently, the only card I know that uses this chip is the D-Link DFE-550TX. (Don't ask me where to buy these: the only cards I have are samples sent to me by D-Link.) This driver is the first to make use of the miibus code once I'm sure it all works together nicely, I'll start converting the other drivers. The Sundance chip is a clone of the 3Com 3c90x Etherlink XL design only with its own register layout. Support is provided for ifmedia, hardware multicast filtering, bridging and promiscuous mode.
* This commit adds device driver support for Adaptec Duralink PCI fastwpaul1999-07-251-1/+2
| | | | | | | | | | | | | | | | | | | | | ethernet controllers based on the AIC-6915 "Starfire" controller chip. There are single port, dual port and quad port cards, plus one 100baseFX card. All are 64-bit PCI devices, except one single port model. The Starfire would be a very nice chip were it not for the fact that receive buffers have to be longword aligned. This requires buffer copying in order to achieve proper payload alignment on the alpha. Payload alignment is enforced on both the alpha and x86 platforms. The Starfire has several different DMA descriptor formats and transfer mechanisms. This driver uses frame descriptors for transmission which can address up to 14 packet fragments, and a single fragment descriptor for receive. It also uses the producer/consumer model and completion queues for both transmit and receive. The transmit ring has 128 descriptors and the receive ring has 256. This driver supports both FreeBSD/i386 and FreeBSD/alpha, and uses newbus so that it can be compiled as a loadable kernel module. Support for BPF and hardware multicast filtering is included.
* The matcd driver is acting strange (returning a successful open evenjkh1999-07-201-1/+3
| | | | when it fails). Disable it in sysinstall for now.
* This commit adds driver support for the SysKonnect SK-984x serieswpaul1999-07-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gigabit ethernet adapters. This includes two single port cards (single mode and multimode fiber) and two dual port cards (also single mode and multimode fiber). SysKonnect is currently the only vendor with a dual port gigabit ethernet NIC. The ports on dual port adapters are treated as separate network interfaces. Thus, if you have an SK-9844 dual port SX card, you should have both sk0 and sk1 interfaces attached. Dual port cards are implemented using two XMAC II chips connected to a single SysKonnect GEnesis controller. Hence, dual port cards are really one PCI device, as opposed to two separate PCI devices connected through a PCI to PCI bridge. Note that SysKonnect's drivers use the two ports for failover purposes rather that as two separate interfaces, plus they don't support jumbo frames. This applies to their Linux driver too. :) Support is provided for hardware multicast filtering, BPF and jumbo frames. The SysKonnect cards support TCP checksum offload however this feature is not currently enabled (hopefully it will be once we get checksum offload support). There are still a few things that need to be implemeted, like the ability to communicate with the on-board LM80 voltage/temperature monitor, but I wanted to get the driver under CVS control and into -current so people could bang on it. A big thanks for SysKonnect for making all their programming info for these cards (and for their FDDI and token ring cards) available without NDA (see www.syskonnect.com).
* update fla related entries.phk1999-07-061-3/+3
|
* wcd -> acdmharo1999-07-031-2/+2
| | | | Submitted by: Ruslan Ermilov <ru@ucb.crimea.ua>
* Add bits of PAO that are non-controversial.markm1999-06-171-7/+8
| | | | Submitted by: Tatsumi HOSOKAWA
* Do a clean-up pass on error/warning messages.jkh1999-05-271-10/+7
|
* This commit adds driver support for PCI fast ethernet cards based on thewpaul1999-05-211-1/+2
| | | | | | | | | | | | | | | | | | | | | | | ADMtek AL981 "Comet" chipset. The AL981 is yet another DEC tulip clone, except with simpler receive filter options. The AL981 has a built-in transceiver, power management support, wake on LAN and flow control. This chip performs extremely well; it's on par with the ASIX chipset in terms of speed, which is pretty good (it can do 11.5MB/sec with TCP easily). I would have committed this driver sooner, except I ran into one problem with the AL981 that required a workaround. When the chip is transmitting at full speed, it will sometimes wedge if you queue a series of packets that wrap from the end of the transmit descriptor list back to the beginning. I can't explain why this happens, and none of the other tulip clones behave this way. The workaround this is to just watch for the end of the transmit ring and make sure that al_start() breaks out of its packet queuing loop and waiting until the current batch of transmissions completes before wrapping back to the start of the ring. Fortunately, this does not significantly impact transmit performance. This is one of those things that takes weeks of analysis just to come up with two or three lines of code changes.
* Add driver support for gigabit ethernet adapters based on the Alteonwpaul1999-04-061-1/+2
| | | | | | | | | | | | | | | | | | | | | | | Networks Tigon 1 and Tigon 2 chipsets. There are a _lot_ of OEM'ed gigabit ethernet adapters out there which use the Alteon chipset so this driver covers a fair amount of hardware. I know that it works with the Alteon AceNIC, 3Com 3c985 and Netgear GA620, however it should also work with the DEC/Compaq EtherWORKS 1000, Silicon Graphics Gigabit ethernet board, NEC Gigabit Ethernet board and maybe even the IBM and and Sun boards. The Netgear board is the cheapest (~$350US) but still yields fairly good performance. Support is provided for jumbo frames with all adapters (just set the MTU to something larger than 1500 bytes), as well as hardware multicast filtering and vlan tagging (in conjunction with the vlan support in -current, which I should merge into -stable soon). There are some hooks for checksum offload support, but they're turned off for now since FreeBSD doesn't have an officially sanctioned way to support checksum offloading (yet). I have not added the 'device ti0' entry to GENERIC since the driver with all the firmware compiled in is quite large, and it doesn't really fit into the category of generic hardware.
* Add an option for resetting and rescanning the probed device list, perhapsjkh1999-04-061-1/+28
| | | | | | | | to now detect that CD you just remembered to put in the drive or that pccard NIC that you've inserted (anybody can put pccardd in an mfsroot image now you know.. :) Requested by: Annelise Anderson <andrsn@andrsn.Stanford.EDU>
* Add driver support (and man page) for PCI fast ethernet cards basedwpaul1999-01-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | on the ASIX AX88140A chip. Update /sys/conf/files, RELNOTES.TXT, /sys/i388/i386/userconfig.c, sysinstall/devices.c, GENERIC and LINT accordingly. For now, the only board that I know of that uses this chip is the Alfa Inc. GFC2204. (Its predecessor, the GFC2202, was a DEC tulip card.) Thanks again to Ulf for obtaining the board for me. If anyone runs across another, please feel free to update the man page and/or the release notes. (The same applies for the other drivers.) FreeBSD should now have support for all of the DEC tulip workalike chipsets currently on the market (Macronix, Lite-On, Winbond, ASIX). And unless I'm mistaken, it should also have support for all PCI fast ethernet chipsets in general (except maybe the SMC FEAST chip, which nobody seems to ever use, including SMC). Now if only we could convince 3Com, Intel or whoever to cough up some documentation for gigabit ethernet hardware. Also updated RELNOTEX.TXT to mention that the SVEC PN102TX is supported by the Macronix driver (assuming you actually have an SVEC PN102TX with a Macronix chip on it; I tried to order a PN102TX once and got a box labeled 'Hawking Technology PN102TX' that had a VIA Rhine board inside it).
* An early Christmas present: add driver support for a whole bunch ofwpaul1998-12-041-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PCI fast ethernet adapters, plus man pages. if_pn.c: Netgear FA310TX model D1, LinkSys LNE100TX, Matrox FastNIC 10/100, various other PNIC devices if_mx.c: NDC Communications SOHOware SFA100 (Macronix 98713A), various other boards based on the Macronix 98713, 98713A, 98715, 98715A and 98725 chips if_vr.c: D-Link DFE530-TX, other boards based on the VIA Rhine and Rhine II chips (note: the D-Link and certain other cards that actually use a Rhine II chip still return the PCI device ID of the Rhine I. I don't know why, and it doesn't really matter since the driver treats both chips the same anyway.) if_wb.c: Trendware TE100-PCIE and various other cards based on the Winbond W89C840F chip (the Trendware card is identical to the sample boards Winbond sent me, so who knows how many clones there are running around) All drivers include support for ifmedia, BPF and hardware multicast filtering. Also updated GENERIC, LINT, RELNOTES.TXT, userconfig and sysinstall device list. I also have a driver for the ASIX AX88140A in the works.
* Add entries for DiskOnChip2000 Flash device.jkh1998-10-191-1/+3
| | | | Submitted by: phk
* Add driver support for PCI fast ethernet adapters based on thewpaul1998-10-181-1/+2
| | | | | | | | | RealTek 8129/8139 chipset like I've been threatening. Update kernel configs, userconfig.c, relnotes and sysinstall. No man page yet; comming soon. I consider this driver stable enough that I want to give it some exposure in -current.
* Fix typo in message.danny1998-09-301-2/+2
|
* Remove support for floppy tape installs. I'm sorry, we're outtajkh1998-09-261-2/+1
| | | | | space, and it's either this or the DOS installs. I think that the DOS installs are somehow more important. :)
* Device name cleanup for CAM.gibbs1998-09-151-6/+4
|
* Add device list entries for the tl and xl PCI ethernet devices.wpaul1998-09-131-2/+4
|
* MF22: Paul Traina's changes.jkh1998-07-181-3/+8
|
* Crank the max possible disks/slices constants way down.jkh1998-06-291-6/+6
| | | | | The probe for this sometimes makes IDE drives chatter their guts out and takes an inordinately long time in such cases..
* Merge updates from 2.2jkh1998-05-241-1/+2
|
* Make Mitsumi and Sony CDROM devs also use the `a' device. I thinkjkh1998-05-111-3/+3
| | | | | they'll have (or are having) similar problems to those described for the matcd device in PR#6576
* It was incorrect to use the `c' device for the matcd driver;jkh1998-05-111-2/+2
| | | | | | | | | | apparently, unlike the IDE or SCSI CDROM drivers, this is magically special-cased for audio CDs. This also might explain what happened with scd (Sony) CDs also since I made the same change there. A follow-up commit will fix that. Thanks, Dave! PR: 6576 Submitted by: Dave Marquardt <marquard@zilker.net>
* MF22: create raw slice entries.jkh1998-03-201-3/+9
|
* Ack, fix typo in last commit.jkh1998-03-201-2/+2
|
* My face is red - make the code for creating slices actually work now.jkh1998-03-201-3/+4
|
* 1. If device node already exists, don't gratuituously try to make itjkh1998-03-161-2/+5
| | | | | | | | again. 2. Don't create slice entries when running multi-user; it adds far too much to sysinstall's startup time. User is expected to have correct slice entries after system is installed.
* When doing "make unders", also remember to make entries forjkh1998-03-151-9/+27
| | | | any slices that exist.
* Form device names correctly with new unit# syntax.jkh1998-02-101-4/+13
|
* Totally change the way that devices are made in the MFS and subsequentlyjkh1998-02-101-143/+168
| | | | | | | | probed in sysinstall. Rather than make template devices and use up lots of inodes, also restricting the number of devices that can be dealt with, mknod all necessary devices as necessary using built-in information. This removes a number of constraints on the number and type of devices that sysinstall can see.
* MF22: match entries for wfdjkh1998-01-221-2/+2
|
* Add entry for SMC 9432TX cards (tx driver).jkh1998-01-211-1/+2
|
* Add wfd style devices to detection list (we'll have to put them on thejkh1998-01-191-1/+2
| | | | boot floppy too, of course - hope I still have enough inodes! :)
* Benign changes to support Justin's CAM code.jkh1998-01-161-1/+3
|
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Add device entries and documentation for Intel EtherExpress Pro/10 driver.jkh1997-01-171-0/+1
|
* Keep our serial ports distinct so that first device is not found forjkh1997-01-151-0/+17
| | | | | | all (closes PR#2296). Print better FTP failure diagnostics Do better media failure checking in install.
* Register SLIP/PPP devices properly again.jkh1997-01-151-19/+11
| | | | | Make the /etc resurrection more sensible for upgrade. No longer quite so annoying.
* 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.
* Add extra tweak for -current compilation and some debugging.jkh1997-01-061-2/+3
|
* Clean up device handling WRT slip and ppp devices. An incomplete transitionjkh1997-01-041-15/+31
| | | | from one convention to another had things pretty fouled up in here.
* Do something I've wanted to do for quite some time - collapse all thejkh1997-01-031-4/+1
| | | | | common layout code into some work functions and make all the layout-using routine adopt them. Also reorganize includes and generally clean up.
* Clean up some calls to close().jkh1996-12-261-6/+4
|
* Now that I've got my source tree sorted out, bring all the thingsjkh1996-12-141-1/+4
| | | | I've been committing into 2.2 directly all this time.
* Do a few things I've been threatening to do for a long time:jkh1996-12-111-22/+13
| | | | | | | | | | | | | | | | 1. Don't use the MSDOSFS code for accessing FreeBSD distribution data. Use Robert Nordier's stand-alone DOS I/O library for the purpose. It this works as well as Robert says it does, it should drastically reduce (or even eliminate) our "I can't install from my DOS partition!" calls. 2. As a result of the above, go to stdio file descriptors for all media types. 3. Taking advantage of #2, start using libftpio for FTP transfers instead of maintaining our own parallel version of the FTP transfer code. Yay! I ripped something out for a change! #1 Submitted-By: Robert Nordier <rnordier@iafrica.com>
* As Paul has just pointed out, much of my strncpy() usage was eitherjkh1996-12-091-2/+2
| | | | | | | bogus or overly complex and really needed to be done more consistently and sanely throughout - no question about it. Done. Suggested-By: Paul Traina <pst@Shockwave.COM>
OpenPOWER on IntegriCloud