summaryrefslogtreecommitdiffstats
path: root/sys/conf/kmod.mk
Commit message (Collapse)AuthorAgeFilesLines
* Fix kernel module build breakage.jkim2006-06-301-0/+2
|
* Commit the new (old) midi framework. It's based in parts on the NetBSD code,netchild2006-05-271-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | but large parts are rewritten by matk and tanimura. This is old code, it's not maintained since 2003. We also don't have a maintainer for this! Yuriy Tsibizov took it and uses it in his emu10kx driver. Since the emu10kx driver will enter the tree "soon" (some bugs have to be fixed after Yuriy return from his holidays), I add it here already. This also contains some changes to emu10k1 and cmi, so if you're lucky, you can now make some kind of use of midi with those soundcards. To all those poor souls which don't have such a card: feel free to send patches, we don't have a maintainer for this. To those which miss a specific feature in the midi code: feel free to submit patches, we don't have a maintainer for this. Oh, did I already told that it would be nice if someone would take care of it? Maintainer with midi equipment wanted! :-) If you get LOR's, submit a PR and notify multimedia@ please. If you get panics, submit a PR with a backtrace (compile the sound system into your kernel instead of using modules in this case) and notify multimedia@ please. Written by: matk, tanimura Submitted by: "Yuriy Tsibizov" <Yuriy.Tsibizov@gfk.ru> Based upon: code from NetBSD
* Rewrite of puc(4). Significant changes are:marcel2006-04-281-2/+2
| | | | | | | | | | | | | | | | | | | | o Properly use rman(9) to manage resources. This eliminates the need to puc-specific hacks to rman. It also allows devinfo(8) to be used to find out the specific assignment of resources to serial/parallel ports. o Compress the PCI device "database" by optimizing for the common case and to use a procedural interface to handle the exceptions. The procedural interface also generalizes the need to setup the hardware (program chipsets, program clock frequencies). o Eliminate the need for PUC_FASTINTR. Serdev devices are fast by default and non-serdev devices are handled by the bus. o Use the serdev I/F to collect interrupt status and to handle interrupts across ports in priority order. o Sync the PCI device configuration to include devices found in NetBSD and not yet merged to FreeBSD. o Add support for Quatech 2, 4 and 8 port UARTs. o Add support for a couple dozen Timedia serial cards as found in Linux.
* Remove dev/uart/uart_if.m from the default MFILES (in kmod.mk) andmarcel2006-02-241-1/+1
| | | | instead define MFILES appropriately for the uart(4) module build.
* ${.CURDIR} != pwd and since we use the shell version of if now we don't evenmlaier2006-02-201-1/+1
| | | | | | need to prepend it. Found-by: gallatin
* Use shell's version of if to check if the firmware really exists in themlaier2006-02-181-7/+9
| | | | | | | current directory to allow user rules to create the firmware (e.g. from a uuencoded blob). make's version of if is evaluated too early to catch this. Found-by: gallatin
* When linking make sure it succeeds.obrien2006-02-171-2/+2
|
* Fix minor inconsistancy between kernel built modules and stand-aloneimp2006-02-041-0/+2
| | | | | built buildes. I believe this gives the same flags on the command line for both.
* firmware(9) is a subsystem to load binary data into the kernel via amlaier2006-01-291-0/+28
| | | | | | | | | | specially crafted module. There are several handrolled sollutions to this problem in the tree already which will be replaced with this. They include iwi(4), ipw(4), ispfw(4) and digi(4). No objection from: arch MFC after: 2 weeks X-MFC after: some drivers have been converted
* Drop the -I/usr/include (or any of its variants) from CFLAGS.ru2005-11-291-14/+0
| | | | | | | The sys/sys/stddef.h is here for some time now to fulfil the kernel needs. It also was not reliable due to the exists(@) check: in an empty module directory, "make depend; mv .depend .depend~; make depend" ran mkdep(1) with different arguments.
* Rename the .dbg extension to .symbols, which matches "symbol-file"ru2005-10-271-5/+5
| | | | | | | gdb(1) command better, though I must admit it's confusing: these files have not only [debugging] symbols, but much more than that. Requested by: obrien
* Installing debug modules was a bad idea -- I bogusly assumed thatru2005-10-271-7/+9
| | | | | | | | our kernel linker will only load PT_LOAD segments, apparently not. Instead, produce .dbg objects from .debug objects, and install them together with non-debug objects, as described in objcopy(1). Original code by: obrien
* Refactor (some more) installation of kernel and module objects.ru2005-10-251-8/+3
| | | | | | | | | | | | | | | | | | | | | | Try to make everyone happy: David (to have debug kernels installed by default), Warner (to be able to override that), and myself (for actually making it all work and to be consistent). Now, if kernel was configured for debugging (through DEBUG=-g in the kernel config file or "config -g"), doing "make install" will install debug versions of kernel and module objects with their canonical names, kernel.debug -> /boot/kernel/kernel if_fxp.ko.debug -> /boot/kernel/if_fxp.ko Installing a kernel not configured for debugging, or debug kernel with INSTALL_NODEBUG variable defined, will install non-debug kernel and module objects. Also, restore the install.debug and reinstall.debug targets that are part of the existing API (they cause some additional gdb(1) scripts to be installed).
* Get rid of duplicate -I's in CFLAGS.ru2005-10-141-5/+1
|
* Define HAVE_KERNEL_OPTION_HEADERS when building kernel and when buildingglebius2005-10-051-1/+1
| | | | | | | | | | modules along with kernel. After this change it is possible to embrace opt_*.h includes with ifdef HAVE_KERNEL_OPTION_HEADERS. And thus, avoid editing a lot of Makefiles in modules directory each time we introduce a new opt_xxx.h. Requested by: bde
* Fix genassym.o dependencies.ru2005-09-191-1/+4
|
* Use the more readable empty() syntax.obrien2005-09-071-7/+7
|
* Revert a mistake borrowed from kern.post.mk that has just been fixed.ru2005-04-221-1/+0
|
* Add rules for building assym.s.iedowse2005-04-221-0/+14
|
* I accidently committed two 'cleandepend' when I was deciding whichobrien2005-04-191-1/+1
| | | | form was "cleaner".
* As with kernel-depend, rm the DEPENDFILE before modules-depend.obrien2005-04-181-1/+2
|
* Use comments after .endif to please make(1) with latest changes somux2005-04-111-2/+2
| | | | | that it's possible to build a kernel without getting flooded with thousands of warnings.
* Don't forget to create new-style links for module builds.imp2005-04-031-1/+6
| | | | | Forgotten by: imp@ Reminded by: nyan@
* This is the much rumoured ATA mkIII update that I've been working on.sos2005-03-301-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o ATA is now fully newbus'd and split into modules. This means that on a modern system you just load "atapci and ata" to get the base support, and then one or more of the device subdrivers "atadisk atapicd atapifd atapist ataraid". All can be loaded/unloaded anytime, but for obvious reasons you dont want to unload atadisk when you have mounted filesystems. o The device identify part of the probe has been rewritten to fix the problems with odd devices the old had, and to try to remove so of the long delays some HW could provoke. Also probing is done without the need for interrupts, making earlier probing possible. o SATA devices can be hot inserted/removed and devices will be created/ removed in /dev accordingly. NOTE: only supported on controllers that has this feature: Promise and Silicon Image for now. On other controllers the usual atacontrol detach/attach dance is still needed. o Support for "atomic" composite ATA requests used for RAID. o ATA RAID support has been rewritten and and now supports these metadata formats: "Adaptec HostRAID" "Highpoint V2 RocketRAID" "Highpoint V3 RocketRAID" "Intel MatrixRAID" "Integrated Technology Express" "LSILogic V2 MegaRAID" "LSILogic V3 MegaRAID" "Promise FastTrak" "Silicon Image Medley" "FreeBSD PseudoRAID" o Update the ioctl API to match new RAID levels etc. o Update atacontrol to know about the new RAID levels etc NOTE: you need to recompile atacontrol with the new sys/ata.h, make world will take care of that. NOTE2: that rebuild is done differently from the old system as the rebuild is now done piggybacked on read requests to the array, so atacontrol simply starts a background "dd" to rebuild the array. o The reinit code has been worked over to be much more robust. o The timeout code has been overhauled for races. o Support of new chipsets. o Lots of fixes for bugs found while doing the modulerization and reviewing the old code. Missing or changed features from current ATA: o atapi-cd no longer has support for ATAPI changers. Todays its much cheaper and alot faster to copy those CD images to disk and serve them from there. Besides they dont seem to be made anymore, maybe for that exact reason. o ATA RAID can only read metadata from all the above metadata formats, not write all of them (Promise and Highpoint V2 so far). This means that arrays can be picked up from the BIOS, but they cannot be created from FreeBSD. There is more to it than just the missing write metadata support, those formats are not unique to a given controller like Promise and Highpoint formats, instead they exist for several types, and even worse, some controllers can have different formats and its impossible to tell which one. The outcome is that we cannot reliably create the metadata of those formats and be sure the controller BIOS will understand it. However write support is needed to update/fail/rebuild the arrays properly so it sits fairly high on the TODO list. o So far atapicam is not supported with these changes. When/if this will change is up to the maintainer of atapi-cam so go there for questions. HW donated by: Webveveriet AS HW donated by: Frode Nordahl HW donated by: Yahoo! HW donated by: Sentex Patience by: Vife and my boys (and even the cats)
* Further embellish rev. 1.180: protect against -fno-strict-aliasingru2005-02-111-2/+2
| | | | | | | being already in CFLAGS (as is the case with "make buildkernel"). NB: rev. 1.180 is only needed due to a broken setting of CFLAGS in tinderbox.
* Emblish rev 1.180 to -fno-strict-alias w/-Os & -O3 also.obrien2005-02-091-1/+3
|
* Hook up the cpufreq framework, acpi_perf(4), and cpufreq(4) drivers.njl2005-02-041-1/+2
|
* Don't lose the frame pointer for PPC modules: backtrace doesn't work.grehan2005-02-021-1/+1
|
* Add required ingimp2005-01-261-1/+1
|
* Add -fno-strict-alias whenever someone is compiling with -O2,imp2005-01-261-0/+1
| | | | unconditionally.
* Generally force -Werror for modules when not compiling with icc. Thisimp2005-01-261-0/+3
| | | | has burned me for the last time.
* Modules on PPC need to be compiled with -mlongcall to get aroundgrehan2005-01-061-0/+4
| | | | | the +/-64k blr offset limitation. With gcc bug #12769 fixed, it's time to put enable this.
* Remove special case from *devs2h loop for usbimp2004-12-301-5/+21
| | | | | Move usb out of the loop since the other devs2h programs don't grok -h Add new rule for usbdevs_data.h
* Properly handle vnode_if.h dependencies, and don't forget to clean all files.ru2004-12-081-13/+12
|
* Unbreak KLDs that use VFS by accounting for changes in the generationgreen2004-12-081-7/+18
| | | | process for the vnode header files.
* Revert rev. 1.166 and remove sparc64/pci/ofw_pci_if.m from MFILES again,marius2004-12-041-1/+1
| | | | sparc64/pci/ofw_pci.h is no longer required for compiling modules.
* Sort MFILES.marcel2004-11-201-11/+9
|
* Hack around a problem with sys/tools/usbdevs2h.awk that generatesru2004-10-241-0/+4
| | | | both usbdevs.h and usbdevs_data.h. (The latter was not cleaned.)
* Back out cumulative changes from revs. 1.92-1.94: "make depend"ru2004-10-121-1/+0
| | | | | | | | followed by "make depend" shouldn't do anything. It doesn't seem to be a problem anymore, and if someone finds it to break again, please contact me so we can work on a real fix. Reviewed by: bde
* Style fixes, including:ru2004-10-121-40/+34
| | | | | | | | | | | | | | - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
* Revert the change from rev 1.168. ru convinced me that the situationjoerg2004-10-111-1/+1
| | | | | | | that was fixed by this should not normally happen, and since I did not record the traces of my failed build attempt that had been solved with that change, it's not entirely clear whether it hadn't been a pilot error on my end. In dubio pro reo. :-)
* Forcibly create symlinked headers, otherwise the build process may failjoerg2004-10-091-1/+1
| | | | if the target link already existed (e. g. -DNO_KERNELCLEAN).
* Unconditionally add `-fno-omit-frame-pointer' to CFLAGS when buildingiedowse2004-08-291-0/+3
| | | | | modules on the amd64 platform. Without this, ddb stack traces cannot follow module function calls, which makes debugging very difficult.
* Add sparc64/pci/ofw_pci_if.m to the list of MFILES so modules can usemarius2004-08-141-1/+2
| | | | | sparc64/pci/ofw_pci.h. This is a bit messy right now but (hopefully) will get better once the MI OFW PCI code has moved from sparc64/pci to dev/ofw.
* Removed COPTS support from kmod.mk and kern.pre.mk.ru2004-08-131-1/+1
| | | | COPTS support in bsd.prog.mk is preserved but discouraged.
* - Introduce an ofw_bus kobj-interface for retrieving the OFW node and amarius2004-08-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | subset ("compatible", "device_type", "model" and "name") of the standard properties in drivers for devices on Open Firmware supported busses. The standard properties "reg", "interrupts" und "address" are not covered by this interface because they are only of interest in the respective bridge code. There's a remaining standard property "status" which is unclear how to support properly but which also isn't used in FreeBSD at present. This ofw_bus kobj-interface allows to replace the various (ebus_get_node(), ofw_pci_get_node(), etc.) and partially inconsistent (central_get_type() vs. sbus_get_device_type(), etc.) existing IVAR ones with a common one. This in turn allows to simplify and remove code-duplication in drivers for devices that can hang off of more than one OFW supported bus. - Convert the sparc64 Central, EBus, FHC, PCI and SBus bus drivers and the drivers for their children to use the ofw_bus kobj-interface. The IVAR- interfaces of the Central, EBus and FHC are entirely replaced by this. The PCI bus driver used its own kobj-interface and now also uses the ofw_bus one. The IVARs special to the SBus, e.g. for retrieving the burst size, remain. Beware: this causes an ABI-breakage for modules of drivers which used the IVAR-interfaces, i.e. esp(4), hme(4), isp(4) and uart(4), which need to be recompiled. The style-inconsistencies introduced in some of the bus drivers will be fixed by tmm@ in a generic clean-up of the respective drivers later (he requested to add the changes in the "new" style). - Convert the powerpc MacIO bus driver and the drivers for its children to use the ofw_bus kobj-interface. This invloves removing the IVARs related to the "reg" property which were unused and a leftover from the NetBSD origini of the code. There's no ABI-breakage caused by this because none of these driver are currently built as modules. There are other powerpc bus drivers which can be converted to the ofw_bus kobj-interface, e.g. the PCI bus driver, which should be done together with converting powerpc to use the OFW PCI code from sparc64. - Make the SBus and FHC front-end of zs(4) and the sparc64 eeprom(4) take advantage of the ofw_bus kobj-interface and simplify them a bit. Reviewed by: grehan, tmm Approved by: re (scottl) Discussed with: tmm Tested with: Sun AX1105, AXe, Ultra 2, Ultra 60; PPC cross-build on i386
* Add acpi methods for HID/CID probing, evaluating objects, and walking thenjl2004-06-291-1/+1
| | | | | | namespace. This is to allow decoupling of attachments from ACPI where they need some functionality when ACPI is present but do not want to require ACPI to always be loaded.
* Hook acpi_quirks up to the build for kernel and modules.njl2004-06-241-0/+11
|
* Link ALTQ to the build and break with ABI for struct ifnet. Please recompilemlaier2004-06-131-0/+4
| | | | | | | | | | | | your (network) modules as well as any userland that might make sense of sizeof(struct ifnet). This does not change the queueing yet. These changes will follow in a seperate commit. Same with the driver changes, which need case by case evaluation. __FreeBSD_version bump will follow. Tested-by: (i386)LINT
* Step 1 in moving EISA devices to kobj/newbus. Use kobj methods forimp2004-06-091-1/+1
| | | | | | | | | | | | | | all of the interface between the driver and the bus. This will enable us to stop special casing eisa bus attachments in modules and treat them like we treat all other busses. In the longer run, we need to eliminate much (all?) of these interfaces and switch to using the standard bus_alloc_resource(), but that's not done right now. # I've not updated the modules to include eisa, etc, just yet Tested on: Compaq Proliant 3000/333 purchased for eisa work
OpenPOWER on IntegriCloud