summaryrefslogtreecommitdiffstats
path: root/sys/conf
Commit message (Collapse)AuthorAgeFilesLines
* Alas, poor SPECFS! -- I knew him, Horatio; A filesystem of infinitephk2004-10-221-1/+0
| | | | | | | | | | | jest, of most excellent fancy: he hath taught me lessons a thousand times; and now, how abhorred in my imagination it is! my gorge rises at it. Here were those hacks that I have curs'd I know not how oft. Where be your kludges now? your workarounds? your layering violations, that were wont to set the table on a roar? Move the skeleton of specfs into devfs where it now belongs and bury the rest.
* Add dcons_os.{c,h}.simokawa2004-10-131-0/+1
|
* 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).
* Port NetBSD auxio driver. The driver was modified to use led(4) and canyongari2004-10-091-0/+2
| | | | | | | | | | | be used to announce various system activity. The auxio device provides auxiliary I/O functions and is found on various SBus/EBus UltraSPARC models. At present, only front panel LED is controlled by this driver. Approved by: jake (mentor) Reviewed by: joerg Tested by: joerg
* Since net/net_osdep.c contained only one function that could bebrooks2004-10-081-1/+0
| | | | | trivially implemented as a macro, do that and remove it. NetBSD did this quite a while ago.
* Back out v1.58... We still don't know what is causing the specifickensmith2004-10-071-1/+1
| | | | | | | | | | problem I had but it's happening in code that is messing around with register windows - I'm willing to live with that piece being sensitive to this and it looks like the other problems we had reported lately are not fixed by using -O instead of -O2. Sorry for the churn. Looks like I need a second pointy hat. Someone tells me they stack well. :-))))
* Port pbio to HEAD.imp2004-10-071-0/+1
| | | | OK'd by: dds
* Back out v1.49. Recent findings suggest sparc64 may not be ready forkensmith2004-10-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | -O2 on kernel compiles after all. While working on adding a KASSERT to sparc64/sparc64/rwindow.c I found that it was "position sensitive", putting it above a call to flushw() instead of below caused corruption of processes on the system. jake and jhb have both confirmed there is no obvious explanation for that. The exact same kernel code does not have the process corruption problem if compiled with -O instead of -O2. There have been signs of similar issues floated on the sparc64@ mailing list, lets see if this helps make them go away. Note this isn't an optimal fix as far as the file format goes, if this disgusts too many people I'll fix it the right way. Since compiling with something other than -O is a known problem this format would prevent a change to the default causing grief. And this may also help motivate finding out what the compiler is doing wrong so we can shift back to using -O2. :-) My turn for the pointy hat... One of the florescent ones... MFC after: 2 days
* Add a more verbose description for `device vlan'yar2004-10-041-0/+2
| | | | to the above comment block devoted to such descriptions.
* Hint a kernel builder that vlan needs miibus, which isn't obvious.yar2004-10-041-1/+1
|
* assign 187 to ata over ethernet for Sam's ata over ethernet driver.imp2004-10-011-0/+1
| | | | | # Yes, this is the right thing to do: we keep assignments for 4.x here # to document them, and Sam has a nearly completed driver.
* Add a new API for allocating unit number (-like) resources.phk2004-09-301-0/+1
| | | | | | | | | | | | | | | Allocation is always lowest free unit number. A mixed range/bitmap strategy for maximum memory efficiency. In the typical case where no unit numbers are freed total memory usage is 56 bytes on i386. malloc is called M_WAITOK but no locking is provided (yet). A bit of experience will be necessary to determine the best strategy. Hopefully a "caller provides locking" strategy can be maintained, but that may require use of M_NOWAIT allocation and failure handling. A userland test driver is included.
* Be consistant; make the memrange bit be part of the mem module likemarkm2004-09-281-1/+1
| | | | i386.
* Move the IA-32 trap handling from trap() to ia32_trap(). Move themarcel2004-09-251-0/+1
| | | | | ia32_syscall() function along with it to ia32_trap.c. When COMPAT_IA32 is not defined, we'll raise SIGEMT instead.
* Converge towards i386. I originally resisted creating <machine/pc/bios.h>peter2004-09-241-0/+1
| | | | | | | | | | | | because it was mostly irrelevant - except for the silly BIOS_PADDRTOVADDR etc macros. Along the way of working around this, I missed a few things. * Make syscons properly inherit the bios capslock/shiftlock/etc state like i386 does. Note that we cannot inherit the bios key repeat rate because that requires a bios call (which is impossible for us). * Give syscons the ability to beep on amd64. Oops. While here, make bios.c compile and add it to files.amd64.
* Use -O2 for the arm kernel as wellcognet2004-09-231-0/+2
|
* Use the address provided in the conf file, instead of hardcode 0xc0000000.cognet2004-09-231-1/+1
|
* Add new options :cognet2004-09-231-5/+10
| | | | | | | | PHYSADDR : Address of the physical memory KERNPHYSADDR : Physical address where the kernel starts KERNVIRTADDR : Virtual address of the kernel STARTUP_PAGETABLE_ADDR : Where to put the page table at bootstrap + Xscale specific options
* Add the possibility to specify the kernel virtual address and the kernelcognet2004-09-231-3/+7
| | | | physical address in the kernel config file, as it varies from CPU to CPU.
* Per recent HEADSUP: Disconnect (old)vinum from the kernel build.phk2004-09-234-33/+1
| | | | | | | | | | | Users should move to the new geom_vinum implementation instead. The refcount logic which is being added to devices to enable safe module unloading and the buf/vm work also in progress would require a major rework of the (old)-vinum code to comply with the new semantics. The actual source files will not be removed until I have coordinated with the geomvinum people if they need any bits repo-copied etc.
* Pass the idea of the make(1) binary to use down to newvers.sh.ru2004-09-172-2/+2
| | | | | | | | | | | | | This is necessary so source upgrades use the correct binary. MFC after: 3 days For the record: Problem spotted by Scott Long, who mentioned that source upgrades from 4.7 to recent 5.x and 6.0 are broken. Detailed analysis shows that 4.7 has a broken make(1) binary. A breakage was fixed in RELENG_4 in make/main.c,v 1.35.2.7 by imp@, though the commit log erroneously stated "MFC 1.68" while in fact it should have been spelled as "MFC 1.67".
* Attach ng_netflow to kernel build.glebius2004-09-163-0/+4
| | | | Approved by: julian (mentor)
* Typo fix.ceri2004-09-121-1/+1
|
* Add device driver support for the VIA Networking Technologieswpaul2004-09-101-0/+2
| | | | | | | | | | | | VT6122 gigabit ethernet chip and integrated 10/100/1000 copper PHY. The vge driver has been added to GENERIC for i386, pc98 and amd64, but not to sparc or ia64 since I don't have the ability to test it there. The vge(4) driver supports VLANs, checksum offload and jumbo frames. Also added the lge(4) and nge(4) drivers to GENERIC for i386 and pc98 since I was in the neighborhood. There's no reason to leave them out anymore.
* Fixed sound-related hints. (Yes, this is ambiguous but matches reality.)ru2004-09-081-14/+14
| | | | | Reviewed by: matk, cg (an earlier version) MT5 after: 3 days
* Device driver for the Cypress CY7C637xx and CY7C640/1xx families of USBdes2004-09-051-0/+1
| | | | | | | | | | | | | | | | to RS232 bridges, such as the one found in the DeLorme Earthmate USB GPS receiver (which is the only device currently supported by this driver). While other USB to serial drivers in the tree rely heavily on ucom, this one is self-contained. The reason for that is that ucom assumes that the bridge uses bulk pipes for I/O, while the Cypress parts actually register as human interface devices and use HID reports for configuration and I/O. The driver is not entirely complete: there is no support yet for flow control, and output doesn't seem to work, though I don't know if that is because of a bug in the code, or simply because the Earthmate is a read- only device.
* Refactor a bunch of scheduler code to give basically the same behaviourjulian2004-09-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | but with slightly cleaned up interfaces. The KSE structure has become the same as the "per thread scheduler private data" structure. In order to not make the diffs too great one is #defined as the other at this time. The KSE (or td_sched) structure is now allocated per thread and has no allocation code of its own. Concurrency for a KSEGRP is now kept track of via a simple pair of counters rather than using KSE structures as tokens. Since the KSE structure is different in each scheduler, kern_switch.c is now included at the end of each scheduler. Nothing outside the scheduler knows the contents of the KSE (aka td_sched) structure. The fields in the ksegrp structure that are to do with the scheduler's queueing mechanisms are now moved to the kg_sched structure. (per ksegrp scheduler private data structure). In other words how the scheduler queues and keeps track of threads is no-one's business except the scheduler's. This should allow people to write experimental schedulers with completely different internal structuring. A scheduler call sched_set_concurrency(kg, N) has been added that notifies teh scheduler that no more than N threads from that ksegrp should be allowed to be on concurrently scheduled. This is also used to enforce 'fainess' at this time so that a ksegrp with 10000 threads can not swamp a the run queue and force out a process with 1 thread, since the current code will not set the concurrency above NCPU, and both schedulers will not allow more than that many onto the system run queue at a time. Each scheduler should eventualy develop their own methods to do this now that they are effectively separated. Rejig libthr's kernel interface to follow the same code paths as linkse for scope system threads. This has slightly hurt libthr's performance but I will work to recover as much of it as I can. Thread exit code has been cleaned up greatly. exit and exec code now transitions a process back to 'standard non-threaded mode' before taking the next step. Reviewed by: scottl, peter MFC after: 1 week
* Fixed more spacing bugs.ru2004-09-031-9/+9
|
* Fix whitespace from last commit.scottl2004-09-021-1/+1
| | | | Submitted by: ru
* Hook autofs to the build.alfred2004-09-023-0/+5
|
* Turn PREEMPTION into a kernel option. Make sure that it's defined ifscottl2004-09-022-2/+8
| | | | | | FULL_PREEMPTION is defined. Add a runtime warning to ULE if PREEMPTION is enabled (code inspired by the PREEMPTION warning in kern_switch.c). This is a possible MT5 candidate.
* General modernization of coda:brooks2004-09-013-3/+1
| | | | | | | | - Ditch NVCODA - Don't use a static major - Don't declare functions extern Reviewed by: peter
* Add the mp_watchdog hooks, although it locks up my SMP test box. It mightpeter2004-08-302-0/+2
| | | | be useable to somebody.
* Kill count device support from config. I've changed the last fewpeter2004-08-3013-33/+47
| | | | | | | | | | | | | | | | | remaining consumers to have the count passed as an option. This is i4b, pc98/wdc, and coda. Bump configvers.h from 500013 to 600000. Remove heuristics that tried to parse "device ed5" as 5 units of the ed device. This broke things like the snd_emu10k1 device, which required quotes to make it parse right. The no-longer-needed quotes have been removed from NOTES, GENERIC etc. eg, I've removed the quotes from: device snd_maestro device "snd_maestro3" device snd_mss I believe everything will still compile and work after this.
* Finish the removal of the HW_WDOG option.ru2004-08-291-6/+0
| | | | Hopefully, we'll finally have the compilable LINT kernels again. ;)
* Back out previous commit, ichwd is i386-only.des2004-08-291-1/+0
|
* Remove the HW_WDOG option; it serves no purpose.des2004-08-291-1/+0
| | | | MFC after: 3 days
* Back out the two previous commits; ichwd is i386-only.des2004-08-291-6/+0
|
* Add an entry for ichwd to hopefully unbreak the LINT build.iedowse2004-08-291-0/+1
|
* 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.
* Fixed untested change.ru2004-08-281-1/+1
|
* Add the Intel ICH watchdog timer driver.netchild2004-08-281-0/+6
| | | | Approved by: des
* Change the default disposition of debug.mpsafenet from 0 to 1, whichrwatson2004-08-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | will cause the network stack to operate without the Giant lock by default. This change has the potential to improve performance by increasing parallelism and decreasing latency in network processing. Due to the potential exposure of existing or new bugs, the following compatibility functionality is maintained: - It is still possible to disable Giant-free operation by setting debug.mpsafenet to 0 in loader.conf. - Add "options NET_WITH_GIANT", which will restore the default value of debug.mpsafenet to 0, and is intended for use on systems compiled with known unsafe components, or where a more conservative configuration is desired. - Add a new declaration, NET_NEEDS_GIANT("componentname"), which permits kernel components to declare dependence on Giant over the network stack. If the declaration is made by a preloaded module or a compiled in component, the disposition of debug.mpsafenet will be set to 0 and a warning concerning performance degraded operation printed to the console. If it is declared by a loadable kernel module after boot, a warning is displayed but the disposition cannot be changed. This is implemented by defining a new SYSINIT() value, SI_SUB_SETTINGS, which is intended for the processing of configuration choices after tunables are read in and the console is available to generate errors, but before much else gets going. This compatibility behavior will go away when we've finished the last of the locking work and are confident that operation is correct.
* Have the linker provide the btext symbol when referenced. This is neededmarcel2004-08-271-0/+1
| | | | | for profiling kernels. Apparently, nobody has ever tried to build one on alpha...
* Properly document and enable the IPFIREWALL_FORWARD option.andre2004-08-271-0/+5
|
* Always compile PFIL_HOOKS into the kernel and remove the associated kernelandre2004-08-273-10/+2
| | | | | | | | | | | compile option. All FreeBSD packet filters now use the PFIL_HOOKS API and thus it becomes a standard part of the network stack. If no hooks are connected the entire packet filter hooks section and related activities are jumped over. This removes any performance impact if no hooks are active. Both OpenBSD and DragonFlyBSD have integrated PFIL_HOOKS permanently as well.
* Have the linker provide btext. It's used for profiling.marcel2004-08-251-0/+1
|
OpenPOWER on IntegriCloud