summaryrefslogtreecommitdiffstats
path: root/usr.sbin/sade/devices.c
Commit message (Collapse)AuthorAgeFilesLines
* Don't use fake 'c' or 'a' BSD partitions for CD-ROM devices. This fixesjhb2002-11-271-5/+5
| | | | | | | sysinstall to create /cdrom entries in /etc/fstab that just use the raw CD-ROM device /dev/cd0, etc. Approved by: re
* Also test for type efi everywhere we currently test for type fat.marcel2002-11-131-1/+1
| | | | | | | With this change there's no a priori difference between EFI and FAT partitions. With this change and the corresponding change to libdisk, we can create EFI partitions, just like regular FAT partitions.
* debugMsg() should end with "\n".kuriyama2002-11-011-1/+1
|
* Add lge(4) to the list of drivers. It was present in 4-stable but not injhb2002-07-021-0/+1
| | | | -current.
* Fix /dev/acdNc minor device number. This bug prevents installing FreeBSDmatusita2002-03-301-1/+1
| | | | | | | | | from CD-ROM in 4-stable. Note that in 5-current, we use devfs so this change (hopefully) shouldn't change anything. I'll MFC to 4-stable later. Tested with: FreeBSD/i386, 4.5-STABLE-20020330-JPSNAP
* Add wireless devices to device_names array. Now that ifconfig can setmurray2002-03-171-0/+3
| | | | | | | session IDs, and sysinstall can load modules from the MFSROOT, it should be possible to install FreeBSD over a wireless link. MFC after: 2 weeks
* Close all open file descriptors before restarting sysinstall.murray2001-09-301-0/+2
| | | | | PR: bin/30737 Submitted by: Alexey V. Neyman <alex.neyman@auriga.ru>
* Add device driver support for the Broadcom BCM570x family of gigabitwpaul2001-09-271-0/+1
| | | | | | | | | | | | | | ethernet controllers. This adds support for the 3Com 3c996-T, the SysKonnect SK-9D21 and SK-9D41, and the built-in gigE NICs on Dell PowerEdge 2550 servers. The latter configuration hauls ass: preliminary measurements show TCP speeds of over 900Mbps using only normal size frames. TCP/IP checksum offload, jumbo frames and VLAN tag insertion/stripping are supported, as well as interrupt moderation. Still need to fix autonegotiation support for 1000baseSX NICs, but beyond that, driver is pretty solid.
* You were knocked senseless by the Boomerang, spun around by the Cyclone,wpaul2001-07-231-0/+1
| | | | | | | | | | | | | | | | | | blown over by the Hurricane and had a house dropped on you by the Tornado. Now it's time to have your parade rained on by... the Typhoon! This commit adds driver support for 3Com 3cR990 10/100 ethernet adapters based on the Typhoon I and Typhoon II chipsets. This is actually a port of the OpenBSD driver with many hacks by me. No Virginia, there isn't any support for the hardware crypto yet. However there is support for TCP/IP checksum offload and VLANs. Special thanks go to Jason Wright, Aaron Campbell and Theo de Raadt for squeezing enough info out of 3Com to get this written, and for doing most of the hard work. Manual page is included. Compiled as a module and included in GENERIC.
* Introduce DEVICE_INIT, DEVICE_GET, and DEVICE_SHUTDOWN macros. As thedd2001-07-021-1/+1
| | | | | | | | | names suggest, they perform methods on Device's. In addition, they check that the pointer passed to them is valid; if it isn't, they pretend that the action failed. This fixes some crashes due to NULL dereferences (e.g., PR 26509). Approved by: jkh (some time ago)
* Add support for gigabit ethernet cards based on the NatSemi DP83820wpaul2001-05-111-0/+1
| | | | | | | | | | | | | | | | | | | and DP83821 gigabit ethernet MAC chips and the NatSemi DP83861 10/100/1000 copper PHY. There are a whole bunch of very low cost cards available with this chipset selling for $150USD or less. This includes the SMC9462TX, D-Link DGE-500T, Asante GigaNIX 1000TA and 1000TPC, and a couple cards from Addtron. This chip supports TCP/IP checksum offload, VLAN tagging/insertion. 2048-bit multicast filter, jumbograms and has 8K TX and 32K RX FIFOs. I have not done serious performance testing with this driver. I know it works, and I want it under CVS control so I can keep tabs on it. Note that there's no serious mutex stuff in here yet either: I need to talk more with jhb to figure out the right way to do this. That said, I don't think there will be any problems. This driver should also work on the alpha. It's not turned on in GENERIC.
* Moved the snc driver position before the sn driver.nyan2000-12-091-1/+3
| | | | Submitted by: Tomokazu HARADA <tkhara@osk4.3web.ne.jp>
* Added Intel Gigabit Ethernet card to device menu.hosokawa2000-11-071-0/+1
|
* Add the ATA RAID device 'ar'.sos2000-10-291-0/+1
|
* Added NEC PC-9801-83, 84, PC-9801-103, 104, PC-9801N-25 and PC-9801N-J02Rnyan2000-10-021-0/+1
| | | | | | | | support which use National Semiconductor DP8393X (SONIC) as ethernet controller. Currently, this driver is used on only PC-98. Submitted by: Motomichi Matsuzaki <mzaki@e-mail.ne.jp> Obtained from: NetBSD/pc98
* add ``xe'' driversanpei2000-09-221-0/+1
| | | | Approved by: jkh
* Add a new driver for the AMD PCnet/FAST, FAST+ and Home PCI adapters.wpaul2000-09-201-0/+1
| | | | | | | | | | | | | | Previously, these cards were supported by the lnc driver (and they still are, but the pcn driver will claim them first), which is fine except the lnc driver runs them in 16-bit LANCE compatibility mode. The pcn driver runs these chips in 32-bit mode and uses the RX alignment feature to achieve zero-copy receive. (Which puts it in the same class as the xl, fxp and tl chipsets.) This driver is also MI, so it will work on the x86 and alpha platforms. (The lnc driver is still needed to support non-PCI cards. At some point, I'll need to newbusify it so that it too will me MI.) The Am79c978 HomePNA adapter is also supported.
* Teach sysinstall about 'aac'.msmith2000-09-131-0/+1
|
* Remove device type field - there are no block devices left.jkh2000-08-221-41/+32
|
* Ugh. Back out local changes that crept in with my last commit. :(jhb2000-07-141-1/+0
|
* MFS: (yes, from -stable) Note that current.FreeBSD.org is a 5.0 snap serverjhb2000-07-141-0/+1
| | | | now, and replace the releng3 3.0 snap entry with releng4.
* Replace phk's commit with code from my local tree which I happenjkh2000-07-051-1/+3
| | | | to like better (it's commented and easier to read).
* Ignore all md disks, installing on them would be particularly pointless.phk2000-07-041-2/+6
| | | | Its not fatal to find hardware we don't know.
* - Remove obsolete PC-card boot.flp hack. It was for making both PC-cardnyan2000-06-051-0/+6
| | | | | | | | | | | | | | boot.flp and plain boot.flp. - Clean up crunchgen related routine. - Add PC-98 support. TODO: o Documentation o Fix some messages for PC-98 o Decrease the size of fixit.flp to 1.2MB o I18N (See: http://www.jp.FreeBSD.org/BootAsia/index.html) No response from jkh
* Remove all of the block devices, correct major numbers to point to themsmith2000-05-251-21/+13
| | | | | corresponding character devices. This is (currently) untested, but should be correct.
* Teach sysinstall about 'twe' disks. Note that this is currentlymsmith2000-05-251-0/+1
| | | | | untested, and with the current state of flux surrounding the death of bdevs other things here may need to change.
* Add Compaq Arraysjlemon2000-03-081-0/+2
|
* Make sysinstall use the new debug.boothowto OID. It will now gojkh2000-02-251-9/+28
| | | | | | | | straight into debug mode if you boot -v. Also conditionalize some annoying debugging output now that we have this ability. Partially submitted by: msmith Approved by: jkh [to make certain wise-acres happy ;)]
* Added sn driver to network interface menu.hosokawa2000-01-151-0/+1
|
* Add device driver support for USB ethernet adapters based on the CATCwpaul2000-01-141-0/+1
| | | | | | | | | | | | | | | | USB-EL1202A chipset. Between this and the other two drivers, we should have support for pretty much every USB ethernet adapter on the market. The only other USB chip that I know of is the SMC USB97C196, and right now I don't know of any adapters that use it (including the ones made by SMC :/ ). Note that the CATC chip supports a nifty feature: read and write combining. This allows multiple ethernet packets to be transfered in a single USB bulk in/out transaction. However I'm again having trouble with large bulk in transfers like I did with the ADMtek chip, which leads me to believe that our USB stack needs some work before we can really make use of this feature. When/if things improve, I intend to revisit the aue and cue drivers. For now, I've lost enough sanity points.
* Add device driver support for USB ethernet adapters based on thewpaul2000-01-051-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Kawasaki LSI KL5KUSB101B chip, including the LinkSys USB10T, the Entrega NET-USB-E45, the Peracom USB Ethernet Adapter, the 3Com 3c19250 and the ADS Technologies USB-10BT. This device is 10mbs half-duplex only, so there's miibus or ifmedia support. This device also requires firmware to be loaded into it, however KLSI allows redistribution of the firmware images (I specifically asked about this; they said it was ok). Special thanks to Annelise Anderson for getting me in touch with KLSI (eventually) and thanks to KLSI for providing the necessary programming info. Highlights: - Add driver files to /sys/dev/usb - update usbdevs and regenerate attendate files - update usb_quirks.c - Update HARDWARE.TXT and RELNOTES.TXT for i386 and alpha - Update LINT, GENERIC and others for i386, alpha and pc98 - Add man page - Add module - Update sysinstall and userconfig.c
* This commit adds device driver support for the ADMtek AN986 Pegasuswpaul1999-12-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | USB ethernet chip. Adapters that use this chip include the LinkSys USB100TX. There are a few others, but I'm not certain of their availability in the U.S. I used an ADMtek eval board for development. Note that while the ADMtek chip is a 100Mbps device, you can't really get 100Mbps speeds over USB. Regardless, this driver uses miibus to allow speed and duplex mode selection as well as autonegotiation. Building and kldloading the driver as a module is also supported. Note that in order to make this driver work, I had to make what some may consider an ugly hack to sys/dev/usb/usbdi.c. The usbd_transfer() function will use tsleep() for synchronous transfers that don't complete right away. This is a problem since there are times when we need to do sync transfers from an interrupt context (i.e. when reading registers from the MAC via the control endpoint), where tsleep() us a no-no. My hack allows the driver to have the code poll for transfer completion subject to the xfer->timeout timeout rather that calling tsleep(). This hack is controlled by a quirk entry and is only enabled for the ADMtek device. Now, I'm sure there are a few of you out there ready to jump on me and suggest some other approach that doesn't involve a busy wait. The only solution that might work is to handle the interrupts in a kernel thread, where you may have something resembling a process context that makes it okay to tsleep(). This is lovely, except we don't have any mechanism like that now, and I'm not about to implement such a thing myself since it's beyond the scope of driver development. (Translation: I'll be damned if I know how to do it.) If FreeBSD ever aquires such a mechanism, I'll be glad to revisit the driver to take advantage of it. In the meantime, I settled for what I perceived to be the solution that involved the least amount of code changes. In general, the hit is pretty light. Also note that my only USB test box has a UHCI controller: I haven't I don't have a machine with an OHCI controller available. Highlights: - Updated usb_quirks.* to add UQ_NO_TSLEEP quirk for ADMtek part. - Updated usbdevs and regenerated generated files - Updated HARDWARE.TXT and RELNOTES.TXT files - Updated sysinstall/device.c and userconfig.c - Updated kernel configs -- device aue0 is commented out by default - Updated /sys/conf/files - Added new kld module directory
* In retrospect, msgNotify() should leave its contents on the screenjkh1999-12-171-0/+1
| | | | | longer to give the user something to look at while things are happening. Change it to do so and insert the appropriate screen saves elsewhere.
* Remove references to ze and zp drivers.phk1999-12-101-2/+0
|
* Remove sysinstall knowledge of the wd based devices..sos1999-12-081-6/+0
|
* Add the if_dc driver and remove all of the al, ax, dm, pn and mx driverswpaul1999-12-041-5/+1
| | | | | | | | which it replaces. The new driver supports all of the chips supported by the ones it replaces, as well as many DEC/Intel 21143 10/100 cards. This also completes my quest to convert things to miibus and add Alpha support.
* Add support for the AMI MegaRAID and Mylex drivers to sysinstall.msmith1999-11-271-0/+4
| | | | | There are reports that installs to these controllers still don't work, but this is at least one step closer.
* Add devices from the ATA driver (ad, acd, afd, ast).sos1999-11-091-1/+6
|
* Spruce up the ADMtek driver: conver to newbus, miibus and add supportwpaul1999-09-221-1/+1
| | | | | | | | | | | | | | | for the AN985 "Centaur" chip, which is apparently the next genetation of the "Comet." The AN985 is also a tulip clone and is similar to the AL981 except that it uses a 99C66 EEPROM and a serial MII interface (instead of direct access to the PHY registers). Also updated various documentation to mention the AN985 and created a loadable module. I don't think there are any cards that use this chip on the market yet: the datasheet I got from ADMtek has boxes with big X's in them where the diagrams should be, and the sample boards I got have chips without any artwork on them.
* This commit adds driver support for PCI fast ethernet NICs based onwpaul1999-09-061-0/+1
| | | | | | | | | | | | | | | | the Davicom DM9100 and DM9102 chipsets, including the Jaton Corporation XPressNet. Datasheet is available from www.davicom8.com. The DM910x chips are still more tulip clones. The API is reproduced pretty faithfully, unfortunately the performance is pretty bad. The transmitter seems to have a lot of problems DMAing multi-fragment packets. The only way to make it work reliably is to coalesce transmitted packets into a single contiguous buffer. The Linux driver (written by Davicom) actually does something similar to this. I can't recomment this NIC as anything more than a "connectivity solution." This driver uses newbus and miibus and is supported on both i386 and alpha platforms.
* This commit adds driver support for the Silicon Integrated Systemswpaul1999-09-051-0/+1
| | | | | | | | | | | | SiS 900 and SiS 7016 PCI fast ethernet chipsets. Full manuals for the SiS chips can be found at www.sis.com.tw. This is a fairly simple chipset. The receiver uses a 128-bit multicast hash table and single perfect entry for the station address. Transmit and receive DMA and FIFO thresholds are easily tuneable. Documentation is pretty decent and performance is not bad, even on my crufty 486. This driver uses newbus and miibus and is supported on both the i386 and alpha architectures.
* 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>
OpenPOWER on IntegriCloud