summaryrefslogtreecommitdiffstats
path: root/sys/modules
Commit message (Collapse)AuthorAgeFilesLines
* - Follow the lead of dcphy(4) and pnphy(4) and move the reminder of the PHYmarius2011-10-084-8/+6
| | | | | | | | | | | | | | drivers that only ever attach to a particular MAC driver, i.e. inphy(4), ruephy(4) and xlphy(4), to the directory where the respective MAC driver lives and only compile it into the kernel when the latter is also there, also removing it from miibus.ko and moving it into the module of the respective MAC driver. - While at it, rename exphy.c, which comes from NetBSD where the MAC driver it corresponds to also is named ex(4) instead of xl(4) but that in FreeBSD actually identifies itself as xlphy(4), and its function names accordingly for consistency. - Additionally while at it, fix some minor style issues like whitespace in the register headers and add multi-inclusion protection to inphyreg.h.
* Add the 9750 SATA+SAS 6Gb/s RAID controller card driver, tws(4). Manydelphij2011-10-042-0/+11
| | | | | | | | thanks for their contiued support to FreeBSD. This is version 10.80.00.003 from codeset 10.2.1 [1] Obtained from: LSI http://kb.lsi.com/Download16574.aspx [1]
* Unbreak no-ip and no-inet6 module builds with ipfw. For now continue tobz2011-09-271-1/+5
| | | | | | | | | | | build the ip_fw_pfil.c hooks and ipfw even in case of no-ip under the assumption that the private L2 hook (which hopefully eventually will be a pfil hook as well) can still be useful. Allow building the module without inet as well. Glanced at by: jhb MFC after: 3 days
* Add IPv6 support to the ng_ipfw(4) [1]. Also add ifdefs to be ableae2011-09-151-1/+15
| | | | | | | | | build it with and without INET/INET6 support. Submitted by: Alexander V. Chernikov <melifaro at yandex-team.ru> [1] Tested by: Alexander V. Chernikov <melifaro at yandex-team.ru> [1] Approved by: re (bz) MFC after: 2 weeks
* Allow the ipfw.ko module built with a kernel to honor any IPFIREWALL_*jhb2011-09-121-1/+1
| | | | | | | | | | options defined in the kernel config. This more closely matches the behavior of other modules which inherit configuration settings from the kernel configuration during a kernel + modules build. Reviewed by: luigi Approved by: re (kib) MFC after: 1 week
* Connect the vxge(4) module to the i386/amd64 build.brueffer2011-09-121-0/+3
| | | | | Catcher of stupid errors: kib Approved by: re (kib)
* Follow up to r225203 refining break-to-debugger run-time configurationrwatson2011-08-272-5/+2
| | | | | | | | | | | | improvements: (1) Implement new model in previously missed at91 UART driver (2) Move BREAK_TO_DEBUGGER and ALT_BREAK_TO_DEBUGGER from opt_comconsole.h to opt_kdb.h (spotted by np) (3) Garbage collect now-unused opt_comconsole.h MFC after: 3 weeks Approved by: re (bz)
* Fix two cases involving opt_capsicum.h and module builds:rwatson2011-08-151-1/+2
| | | | | | | | | | | | | | (1) opt_capsicum.h is no longer required in ffs_alloc.c, so remove the #include. (2) portalfs depends on opt_capsicum.h, so have the Makefile generate one if required. These affect only modules built without a kernel (i.e, not buildkernel, but yes buildworld if the dubious MODULES_WITH_WORLD is used). Approved by: re (bz) Sponsored by: Google Inc
* Add new USB 3G driver.hselasky2011-07-082-1/+36
| | | | | Submitted by: PseudoCylon <moonlightakkiy@yahoo.ca> MFC after: 14 days
* Update packet filter (pf) code to OpenBSD 4.5.bz2011-06-284-6/+70
| | | | | | | | You need to update userland (world and ports) tools to be in sync with the kernel. Submitted by: mlaier Submitted by: eri
* Add possibility to pass IPv6 packets to a divert(4) socket.glebius2011-06-271-1/+6
| | | | Submitted by: sem
* Fix make buildworld -DMODULES_WITH_WORLDuqs2011-06-233-7/+10
| | | | Sort opt_ srcs
* - Add more USB templates for various USB device classeshselasky2011-06-231-1/+8
| | | | | | | - Add basic template support for USB 3.0 - Export definition of template sysctl numbers through usb_ioctl.h MFC after: 7 days
* Fix the kgssapi so that it can be loaded as a module. Currentlyrmacklem2011-06-192-1/+4
| | | | | | | | | | | | | the NFS subsystems use five of the rpcsec_gss/kgssapi entry points, but since it was not obvious which others might be useful, all nineteen were included. Basically the nineteen entry points are set in a structure called rpc_gss_entries and inline functions defined in sys/rpc/rpcsec_gss.h check for the entry points being non-NULL and then call them. A default value is returned otherwise. Requested by rwatson. Reviewed by: jhb MFC after: 2 weeks
* Add DTrace support to the new NFS client. This is essentiallyrmacklem2011-06-183-0/+15
| | | | | | | cloned from the old NFS client, plus additions for NFSv4. A review of this code is in progress, however it was felt by the reviewer that it could go in now, before code slush. Any changes required by the review can be committed as bug fixes later.
* Rename recently added USB serial driver.hselasky2011-06-042-3/+3
| | | | | Suggested by: YongHyeon PYUN MFC after: 7 days
* Flesh out the radar detection related operations for the ath driver.adrian2011-06-011-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | This is in no way a complete DFS/radar detection implementation! It merely creates an abstracted interface which allows for future development of the DFS radar detection code. Note: Net80211 already handles the bulk of the DFS machinery, all we need to do here is figure out that a radar event has occured and inform it as such. It then drives the DFS state engine for us. The "null" DFS radar detection module is included by default; it doesn't require a device line. This commit: * Adds a simple abstracted layer for radar detection state - sys/dev/ath/ath_dfs/; * Implements a null DFS module which doesn't do anything; (ie, implements the exact behaviour at the moment); * Adds hooks to the ath driver to process received radar events and gives the DFS module a chance to determine whether a radar has been detected. Obtained from: Atheros
* Add support for new USB serial driver.hselasky2011-06-012-1/+37
| | | | | Submitted by: Lev Serebryakov, lev @ MFC after: 14 days
* L2 table code. This is enough to get the T4's switch + L2 rewritenp2011-05-301-1/+1
| | | | | | | | | | | | | | | | | | | filters working. (All other filters - switch without L2 info rewrite, steer, and drop - were already fully-functional). Some contrived examples of "switch" filters with L2 rewriting: # cxgbetool t4nex0 iport 0 dport 80 action switch vlan +9 eport 3 Intercept all packets received on physical port 0 with TCP port 80 as destination, insert a vlan tag with VID 9, and send them out of port 3. # cxgbetool t4nex0 sip 192.168.1.1/32 ivlan 5 action switch \ vlan =9 smac aa:bb:cc:dd:ee:ff eport 0 Intercept all packets (received on any port) with source IP address 192.168.1.1 and VLAN id 5, rewrite the VLAN id to 9, rewrite source mac to aa:bb:cc:dd:ee:ff, and send it out of port 0. MFC after: 1 week
* Introduce AR9287 support to the FreeBSD HAL.adrian2011-05-261-0/+6
|
* Fix a typo, it is MPDU not MDPU.bschmidt2011-05-211-1/+1
|
* Add I2C bus driver for the AMD Geode LX series CS5536 Companionbrix2011-05-152-0/+12
| | | | | | Device. Reviewed by: jhb (newbus bits only), adrian
* Disconnect sun4v architecture from the three.attilio2011-05-142-17/+1
| | | | | | | | | Some files keep the SUN4V tags as a code reference, for the future, if any rewamped sun4v support wants to be added again. Reviewed by: marius Tested by: sbruno Approved by: re
* T4 packet timestamps.np2011-05-051-0/+3
| | | | | | | | | | | | | | | Reference code that shows how to get a packet's timestamp out of cxgbe(4). Disabled by default because we don't have a standard way today to pass this information up the stack. The timestamp is 60 bits wide and each increment represents 1 tick of the T4's core clock. As an example, the timestamp granularity is ~4.4ns for this card: # sysctl dev.t4nex.0.core_clock dev.t4nex.0.core_clock: 228125 MFC after: 1 week
* - Remove attempts to implement setting of BMCR_LOOP/MIIF_NOLOOPmarius2011-05-031-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (reporting IFM_LOOP based on BMCR_LOOP is left in place though as it might provide useful for debugging). For most mii(4) drivers it was unclear whether the PHYs driven by them actually support loopback or not. Moreover, typically loopback mode also needs to be activated on the MAC, which none of the Ethernet drivers using mii(4) implements. Given that loopback media has no real use (and obviously hardly had a chance to actually work) besides for driver development (which just loopback mode should be sufficient for though, i.e one doesn't necessary need support for loopback media) support for it is just dropped as both NetBSD and OpenBSD already did quite some time ago. - Let mii_phy_add_media() also announce the support of IFM_NONE. - Restructure the PHY entry points to use a structure of entry points instead of discrete function pointers, and extend this to include a "reset" entry point. Make sure any PHY-specific reset routine is always used, and provide one for lxtphy(4) which disables MII interrupts (as is done for a few other PHYs we have drivers for). This includes changing NIC drivers which previously just called the generic mii_phy_reset() to now actually call the PHY-specific reset routine, which might be crucial in some cases. While at it, the redundant checks in these NIC drivers for mii->mii_instance not being zero before calling the reset routines were removed because as soon as one PHY driver attaches mii->mii_instance is incremented and we hardly can end up in their media change callbacks etc if no PHY driver has attached as mii_attach() would have failed in that case and not attach a miibus(4) instance. Consequently, NIC drivers now no longer should call mii_phy_reset() directly, so it was removed from EXPORT_SYMS. - Add a mii_phy_dev_attach() as a companion helper to mii_phy_dev_probe(). The purpose of that function is to perform the common steps to attach a PHY driver instance and to hook it up to the miibus(4) instance and to optionally also handle the probing, addition and initialization of the supported media. So all a PHY driver without any special requirements has to do in its bus attach method is to call mii_phy_dev_attach() along with PHY-specific MIIF_* flags, a pointer to its PHY functions and the add_media set to one. All PHY drivers were updated to take advantage of mii_phy_dev_attach() as appropriate. Along with these changes the capability mask was added to the mii_softc structure so PHY drivers taking advantage of mii_phy_dev_attach() but still handling media on their own do not need to fiddle with the MII attach arguments anyway. - Keep track of the PHY offset in the mii_softc structure. This is done for compatibility with NetBSD/OpenBSD. - Keep track of the PHY's OUI, model and revision in the mii_softc structure. Several PHY drivers require this information also after attaching and previously had to wrap their own softc around mii_softc. NetBSD/OpenBSD also keep track of the model and revision on their mii_softc structure. All PHY drivers were updated to take advantage as appropriate. - Convert the mebers of the MII data structure to unsigned where appropriate. This is partly inspired by NetBSD/OpenBSD. - According to IEEE 802.3-2002 the bits actually have to be reversed when mapping an OUI to the MII ID registers. All PHY drivers and miidevs where changed as necessary. Actually this now again allows to largely share miidevs with NetBSD, which fixed this problem already 9 years ago. Consequently miidevs was synced as far as possible. - Add MIIF_NOMANPAUSE and mii_phy_flowstatus() calls to drivers that weren't explicitly converted to support flow control before. It's unclear whether flow control actually works with these but typically it should and their net behavior should be more correct with these changes in place than without if the MAC driver sets MIIF_DOPAUSE. Obtained from: NetBSD (partially) Reviewed by: yongari (earlier version), silence on arch@ and net@
* Update carp, gre and pf module builds to be depenent on INET and/orbz2011-04-302-3/+15
| | | | | | | | | INET6_SUPPORT. Reviewed by: gnn (slightly earlier version without pf) Sponsored by: The FreeBSD Foundation Sponsored by: iXsystems MFC after: 2 weeks
* Exar driver for X3100 10GbE Server/Storage adaptersgnn2011-04-281-0/+64
| | | | | | | | Features: Jumbo frames (up to 9600), LRO (Large Receive Offload), TSO (TCP segmentation offload), RTH (Receive Traffic Hash). Submitted by: Sriram Rapuru at Exar MFC after: 2 weeks
* Sync with several changes in UFS/FFS:jhb2011-04-281-1/+1
| | | | | | | | | | | | | | | | | | | | | - 77115: Implement support for O_DIRECT. - 98425: Fix a performance issue introduced in 70131 that was causing reads before writes even when writing full blocks. - 98658: Rename the BALLOC flags from B_* to BA_* to avoid confusion with the struct buf B_ flags. - 100344: Merge the BA_ and IO_ flags so so that they may both be used in the same flags word. This merger is possible by assigning the IO_ flags to the low sixteen bits and the BA_ flags the high sixteen bits. - 105422: Fix a file-rewrite performance case. - 129545: Implement IO_INVAL in VOP_WRITE() by marking the buffer as "no cache". - Readd the DOINGASYNC() macro and use it to control asynchronous writes. Change i-node updates to honor DOINGASYNC() instead of always being synchronous. - Use a PRIV_VFS_RETAINSUGID check instead of checking cr_uid against 0 directly when deciding whether or not to clear suid and sgid bits. Submitted by: Pedro F. Giffuni giffunip at yahoo
* Introduce AR9130 (HOWL) WMAC support to the FreeBSD HAL.adrian2011-04-281-5/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The AR9130 is an AR9160/AR5416 family WMAC which is glued directly to the AR913x SoC peripheral bus (APB) rather than via a PCI/PCIe bridge. The specifics: * A new build option is required to use the AR9130 - AH_SUPPORT_AR9130. This is needed due to the different location the RTC registers live with this chip; hopefully this will be undone in the future. This does currently mean that enabling this option will break non-AR9130 builds, so don't enable it unless you're specifically building an image for the AR913x SoC. * Add the new probe, attach, EEPROM and PLL methods specific to Howl. * Add a work-around to ah_eeprom_v14.c which disables some of the checks for endian-ness and magic in the EEPROM image if an eepromdata block is provided. This'll be fixed at a later stage by porting the ath9k probe code and making sure it doesn't break in other setups (which my previous attempt at this did.) * Sprinkle Howl modifications throughput the interrupt path - it doesn't implement the SYNC interrupt registers, so ignore those. * Sprinkle Howl chip powerup/down throughout the reset path; the RTC methods were * Sprinkle some other Howl workarounds in the reset path. * Hard-code an alternative setup for the AR_CFG register for Howl, that sets up things suitable for Big-Endian MIPS (which is the only platform this chip is glued to.) This has been tested on the AR913x based TP-Link WR-1043nd mode, in legacy, HT/20 and HT/40 modes. Caveats: * 2ghz has only been tested. I've not seen any 5ghz radios glued to this chipset so I can't test it. * AR5416_INTERRUPT_MITIGATION is not supported on the AR9130. At least, it isn't implemented in ath9k. Please don't enable this. * This hasn't been tested in MBSS mode or in RX/TX block-aggregation mode.
* - Add shim to simplify migration to the CAM-based ATA. For each new adaXmav2011-04-261-0/+1
| | | | | | | | | device in /dev/ create symbolic link with adY name, trying to mimic old ATA numbering. Imitation is not complete, but should be enough in most cases to mount file systems without touching /etc/fstab. - To know what behavior to mimic, restore ATA_STATIC_ID option in cases where it was present before. - Add some more details to UPDATING.
* Fix the experimental NFS client so that it does not boguslyrmacklem2011-04-252-2/+34
| | | | | | | | | | | | | | set the f_flags field of "struct statfs". This had the interesting effect of making the NFSv4 mounts "disappear" after r221014, since NFSMNT_NFSV4 and MNT_IGNORE became the same bit. Move the files used for a diskless NFS root from sys/nfsclient to sys/nfs in preparation for them to be used by both NFS clients. Also, move the declaration of the three global data structures from sys/nfsclient/nfs_vfsops.c to sys/nfs/nfs_diskless.c so that they are defined when either client uses them. Reviewed by: jhb MFC after: 2 weeks
* - Removed duplicate {_bxe} definition.davidch2011-04-251-1/+0
| | | | MFC after: One week
* - Added bxe(4) driver for i386 and amd64. Currently untested on otherdavidch2011-04-251-0/+4
| | | | | | CPU architectures. MFC after: One week
* Instead of allocating memory for all the keys at device attach,pjd2011-04-211-0/+1
| | | | | | | | | | | create reasonably large cache for the keys that is filled when needed. The previous version was problematic for very large providers (hundreds of terabytes or serval petabytes). Every terabyte of data needs around 256kB for keys. Make the default cache limit big enough to fit all the keys needed for 4TB providers, which will eat at most 1MB of memory. MFC after: 2 weeks
* Add firmware images for the 6000 series g2a and g2b adapters.bschmidt2011-04-203-1/+13
|
* Update iwn(4) firmware blobs:bschmidt2011-04-203-3/+3
| | | | | | - bump iwn1000fw to 39.31.5.1 - bump iwn5000fw to 8.83.5.1 - bump iwn6050fw to 41.28.5.1
* Fix make buildworld -DMODULES_WITH_WORLD after r220454.uqs2011-04-191-0/+1
|
* Remove missing include directory in preparation for addingbrucec2011-04-161-1/+1
| | | | -Wmissing-include-dirs to CWARNFLAGS.
* Merge ACPICA 20110413.jkim2011-04-151-1/+1
|
* Remove mii(4) dependency and unneeded headers.yongari2011-04-131-1/+1
| | | | Reviewed by: davidch
* Bring over the antenna diversity logic support for Kite.adrian2011-04-131-0/+1
| | | | | Again, this is just the code ported from ath9k and included in the build, it isn't yet enabled.
* Add the initial AR9285 PHY glue for supporting antenna diversity.adrian2011-04-131-1/+1
| | | | This code isn't currently used anywhere; it's just linked into the build.
* Fix make buildworld -DMODULES_WITH_WORLD on i386uqs2011-04-092-2/+2
|
* Stripped '32' suffix from linux systrace module name on i386.art2011-04-081-0/+5
| | | | Approved by: avg
* Fix buildworld -DMODULES_WITH_WORLDuqs2011-04-051-1/+1
|
* Add missing include.adrian2011-04-021-1/+1
| | | | Reported by: Ulrich Sporlein <uqs@spoerlein.net>
* Add support for executing the FreeBSD 1/i386 a.out binaries on amd64.kib2011-04-011-0/+1
| | | | | | | | | | | | | | | In particular: - implement compat shims for old stat(2) variants and ogetdirentries(2); - implement delivery of signals with ancient stack frame layout and corresponding sigreturn(2); - implement old getpagesize(2); - provide a user-mode trampoline and LDT call gate for lcall $7,$0; - port a.out image activator and connect it to the build as a module on amd64. The changes are hidden under COMPAT_43. MFC after: 1 month
* Allow multiple modules within sys/modules/cxgbe. The first one is if_cxgbe.np2011-04-012-11/+18
| | | | MFC after: 3 days
* ath_ahb shouldn't be compiled normally; it is atheros chip specific.adrian2011-03-311-1/+0
| | | | Remove it from here; users can compile it manually if needed.
* Break out the ath PCI logic into a separate device/module.adrian2011-03-314-1/+85
| | | | | | | | | Introduce the AHB glue for Atheros embedded systems. Right now it's hard-coded for the AR9130 chip whose support isn't yet in this HAL; it'll be added in a subsequent commit. Kernel configuration files now need both 'ath' and 'ath_pci' devices; both modules need to be loaded for the ath device to work.
OpenPOWER on IntegriCloud