summaryrefslogtreecommitdiffstats
path: root/sys/pc98
Commit message (Collapse)AuthorAgeFilesLines
* Remove the KDTRACE option again because of the complaints about havingjb2006-11-041-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | it as a default. For the record, the KDTRACE option caused _no_ additional source files to be compiled in; certainly no CDDL source files. All it did was to allow existing BSD licensed kernel files to include one or more CDDL header files. By removing this from DEFAULTS, the onus is on a kernel builder to add the option to the kernel config, possibly by including GENERIC and customising from there. It means that DTrace won't be a feature available in FreeBSD by default, which is the way I intended it to be. Without this option, you can't load the dtrace module (which contains the dtrace device and the DTrace framework). This is equivalent to requiring an option in a kernel config before you can load the linux emulation module, for example. I think it is a mistake to have DTrace ported to FreeBSD, but not to have it available to everyone, all the time. The only exception to this is the companies which distribute systems with FreeBSD embedded. Those companies will customise their systems anyway. The KDTRACE option was intended for them, and only them.
* Build in kernel support for loading DTrace modules by default. Thisjb2006-11-041-0/+3
| | | | | | | | | | | | | | adds the hooks that DTrace modules register with, and adds a few functions which have the dtrace_ prefix to allow the DTrace FBT (function boundary trace) provider to avoid tracing because they are called from the DTtrace probe context. Unlike other forms of tracing and debug, DTrace support in the kernel incurs negligible run-time cost. I think the only reason why anyone wouldn't want to have kernel support enabled for DTrace would be due to the license (CDDL) under which DTrace is released.
* Remove the KSE option now that it's in DEFAULTS on these arches/machines.jb2006-10-261-1/+0
| | | | | | | | | The 'nooption' kernel config entry has to be used to turn KSE off now. This isn't my preferred way of dealing with this, but I'll defer to scottl's experience with the io/mem kernel option change and the grief experienced over that. Submitted by: scottl@
* Add 'options KSE' to the kernel config DEFAULTS on all arches/machinesjb2006-10-261-0/+3
| | | | | | | | | | | except sun4v. This change makes the transition from a default to an option more transparent and is an attempt to head off all the compliants that are likely from people who don't read UPDATING, based on experience with the io/mem change. Submitted by: scottl@
* Make KSE a kernel option, turned on by default in all GENERICjb2006-10-262-0/+5
| | | | | | | kernel configs except sun4v (which doesn't process signals properly with KSE). Reviewed by: davidxu@
* Move "device splash" back to MI NOTES and "files", it's MI.ru2006-10-231-2/+0
|
* Mechanically kill redundant nodevice/nooption/nomakeoption, i.e.,ru2006-10-231-1/+0
| | | | | those that do not exist in MI NOTES or switched on/off in the MD NOTES.
* - MFi386: Remove 'device io'.nyan2006-10-201-12/+0
| | | | | - Remove duplicate options. - 'nomakeoption ATKBD_DFLT_KEYMAP' is not needed anymore.
* Move more MD devices and options out of MI NOTES.des2006-10-201-11/+2
|
* Remove references to pccard.confimp2006-10-191-1/+1
|
* - Remove SCHED_ULE from GENERIC to better avoid foot-shooting bysimon2006-10-051-1/+0
| | | | | | | | | | | unsuspecting users. - Add a comment in NOTES about experimental status of SCHED_ULE. - Make warning about experimental status in sched_ule(4) a bit stronger. Suggested and reviewed by: dougb Discussed on: developers MFC after: 3 days
* Use Calendrical Calculations from subr_clock.c instead of home copy&pasted.phk2006-10-022-184/+46
|
* Second part of a little cleanup in the calendar/timezone/RTC handling.phk2006-10-023-26/+0
| | | | | | | | | | | Split subr_clock.c in two parts (by repo-copy): subr_clock.c contains generic RTC and calendaric stuff. etc. subr_rtc.c contains the newbus'ified RTC interface. Centralize the machdep.{adjkerntz,disable_rtc_set,wall_cmos_clock} sysctls and associated variables into subr_clock.c. They are not machine dependent and we have generic code that relies on being present so they are not even optional.
* First part of a little cleanup in the calendar/timezone/RTC handling.phk2006-10-023-0/+3
| | | | | | Move relevant variables to <sys/clock.h> and fix #includes as necessary. Use libkern's much more time- & spamce-efficient BCD routines.
* Remove the no longer relevant or correct bootinfo sysctls.phk2006-09-301-3/+0
|
* Fix our ioctl(2) implementation when the argument is "int". Newru2006-09-271-0/+26
| | | | | | | | | | | | | ioctls passing integer arguments should use the _IOWINT() macro. This fixes a lot of ioctl's not working on sparc64, most notable being keyboard/syscons ioctls. Full ABI compatibility is provided, with the bonus of fixing the handling of old ioctls on sparc64. Reviewed by: bde (with contributions) Tested by: emax, marius MFC after: 1 week
* Added COMPAT_FREEBSD6 option.ru2006-09-261-0/+1
|
* Fix style nits. No md5 changes in .o's. ;-)jkim2006-09-081-2/+2
|
* Add pc98 specific code to adjust the firmware geometry when it differsimp2006-08-092-0/+50
| | | | | | | from the actual geometry. This enables support of disks larger than ~120GB on pc98 boxes. They make great little network appliances. I've been using these changes for the past year or so on my network storage pc98 box :-).
* Remove sio(4) and related options from MI files to amd64, i386marcel2006-07-291-0/+38
| | | | | | | | | and pc98 MD files. Remove nodevice and nooption lines specific to sio(4) from ia64, powerpc and sparc64 NOTES. There were no such lines for arm yet. sio(4) is usable on less than half the platforms, not counting a future mips platform. Its presence in MI files is therefore increasingly becoming a burden.
* Simplify the pager support in DDB. Allowing different db commands tojhb2006-07-121-3/+2
| | | | | | | | | | | | | | | | install custom pager functions didn't actually happen in practice (they all just used the simple pager and passed in a local quit pointer). So, just hardcode the simple pager as the only pager and make it set a global db_pager_quit flag that db commands can check when the user hits 'q' (or a suitable variant) at the pager prompt. Also, now that it's easy to do so, enable paging by default for all ddb commands. Any command that wishes to honor the quit flag can do so by checking db_pager_quit. Note that the pager can also be effectively disabled by setting $lines to 0. Other fixes: - 'show idt' on i386 and pc98 now actually checks the quit flag and terminates early. - 'show intr' now actually checks the quit flag and terminates early.
* Make the firmware assist driver resident inmjacob2006-07-091-0/+1
| | | | | | preparation for isp using it. Reviewed by: sam, max
* Backed out the change by request from rwatson.babkin2006-06-261-1/+0
| | | | PR: kern/14584
* The common UID/GID space implementation. It has been discussed on -archbabkin2006-06-251-0/+1
| | | | | | | | | | in 1999, and there are changes to the sysctl names compared to PR, according to that discussion. The description is in sys/conf/NOTES. Lines in the GENERIC files are added in commented-out form. I'll attach the test script I've used to PR. PR: kern/14584 Submitted by: babkin
* Remove COMPAT_43 from GENERIC (and other kernel configs). For amd64 there'snetchild2006-06-151-1/+0
| | | | | | | | | | | | | | | | | | | | | | an explicit comment that it's needed for the linuxolator. This is not the case anymore. For all other architectures there was only a "KEEP THIS". I'm (and other people too) running a COMPAT_43-less kernel since it's not necessary anymore for the linuxolator. Roman is running such a kernel for a for longer time. No problems so far. And I doubt other (newer than ia32 or alpha) architectures really depend on it. This may result in a small performance increase for some workloads. If the removal of COMPAT_43 results in a not working program, please recompile it and all dependencies and try again before reporting a problem. The only place where COMPAT_43 is needed (as in: does not compile without it) is in the (outdated/not usable since too old) svr4 code. Note: this does not remove the COMPAT_43TTY option. Nagging by: rdivacky
* Make the ISAPNP code optional and only enable it on i386 and pc98 (usedmarius2006-06-121-0/+1
| | | | | | | | | for CBUS-PNP cards there) by default, as there are no amd64 and sparc64 machines with ISA slots and which therefore could make use of this code known to exist. For sparc64 this additionally allows to get rid of the compat shims for in{b,w,l}()/out{b,w,l}() etc and the associated hacks. OK'ed by: imp, peter
* Enable a few more things in x86 NOTES to get broader LINT coverage:jhb2006-06-121-1/+5
| | | | | - Turn on iwi(4), ipw(4), and ndis(4) on amd64 and i386. - Turn on ral(4) and ural(4) on i386, pc98, and amd64.
* Add the ability to subset the devices that UART pulls in. This allowsimp2006-06-121-0/+4
| | | | | | | | the arm to compile without all the extras that don't appear, at least not in the flavors of ARM I deal with. This helps us save about 100k. If I've botched the available devices on a platform, please let me know and I'll correct ASAP.
* MFi386: revisions 1.627, 1.628 and 1.629.nyan2006-06-051-0/+4
|
* typo.nyan2006-05-271-2/+2
|
* Aling to new console and gdb_port semanticsphk2006-05-261-54/+14
|
* - Add C-bus and ISA front-ends for le(4) so it can actually replacemarius2006-05-172-2/+9
| | | | | | | | | | | | lnc(4) on PC98 and i386. The ISA front-end supports the same non-PNP network cards as lnc(4) did and additionally a couple of PNP ones. Like lnc(4), the C-bus front-end of le(4) only supports C-NET(98)S and is untested due to lack of such hardware, but given that's it's based on the respective lnc(4) and not too different from the ISA front-end it should be highly likely to work. - Remove the descriptions of le(4), which where converted from lnc(4), from sys/i386/conf/NOTES and sys/pc98/conf/NOTES as there's a common one in sys/conf/NOTES.
* - As only the PCI front-end of le(4) is common to all platforms move itsmarius2006-05-171-2/+2
| | | | | | | entry to the PCI NICs section so it's in the same spot in all GENERIC config files. - Add a note to the description of pcn(4) informing that is has precedence over le(4).
* Send the pcvt(4) driver off to retirement.phk2006-05-171-6/+0
|
* Since DELAY() was moved, most <machine/clock.h> #includes have beenphk2006-05-163-3/+0
| | | | unnecessary.
* Kill more references to lnc(4).ru2006-05-161-1/+1
| | | | Submitted by: grep(1)
* Switch from the lnc driver to the le driver. But C-NET(98)S support isnyan2006-05-153-11/+2
| | | | dropped.
* Clean out sysctl machdep.* related defines.phk2006-05-111-4/+4
| | | | The cmos clock related stuff should really be in MI code.
* Add in linsysfs. A linux 2.6 like sys filesystem to pacify the Linuxambrisko2006-05-091-0/+4
| | | | | | | LSI MegaRAID SAS utility. Sponsored by: IronPort Systems Man page help from: brueffer
* Remove unneeded include.nyan2006-05-084-6/+0
|
* - Move defines for PC-98 machine type from pc98/cbus/cbus.h intonyan2006-05-082-29/+17
| | | | | | pc98/pc98/pc98_machdep.h. - Fix PC98_SYSTEM_PARAMETER_SIZE. - Remove unused defines.
* Add the ath and the wlan crypto support.nyan2006-05-082-0/+14
|
* Rewrite of puc(4). Significant changes are:marcel2006-04-281-2/+0
| | | | | | | | | | | | | | | | | | | | 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.
* o Move ISA specific code from ppc.c to ppc_isa.c -- a bus front-marcel2006-04-242-2491/+0
| | | | | | | | | | | | | | end for isa(4). o Add a seperate bus frontend for acpi(4) and allow ISA DMA for it when ISA is configured in the kernel. This allows acpi(4) attachments in non-ISA configurations, as is possible for ia64. o Add a seperate bus frontend for pci(4) and detect known single port parallel cards. o Merge PC98 specific changes under pc98/cbus into the MI driver. The changes are minor enough for conditional compilation and in this form invites better abstraction. o Have ppc(4) usabled on all platforms, now that ISA specifics are untangled enough.
* Add minidump.h for pc98.nyan2006-04-211-0/+6
|
* MFi386: revision 1.625.nyan2006-04-211-2/+15
|
* Don't allow userland to set hardware watch points on kernel memory at all.jhb2006-03-141-23/+20
| | | | | | | | | | | | | | Previously, we tried to allow this only for root. However, we were calling suser() on the *target* process rather than the current process. This means that if you can ptrace() a process running as root you can set a hardware watch point in the kernel. In practice I think you probably have to be root in order to pass the p_candebug() checks in ptrace() to attach to a process running as root anyway. Rather than fix the suser(), I just axed the entire idea, as I can't think of any good reason _at all_ for userland to set hardware watch points for KVM. MFC after: 3 days Also thinks hardware watch points on KVM from userland are bad: bde, rwatson
* MFi386: revision 1.1220.nyan2006-03-041-3/+2
|
* - Use bus_setup_intr() and bus_teardown_intr() to register device driverjhb2006-02-224-9/+6
| | | | | | | | | | interrupt handlers rather than BUS_SETUP_INTR() and BUS_TEARDOWN_INTR(). Uses of the BUS_*() versions in the implementation of foo_intr methods in bus drivers were not changed. Mostly this just means that some drivers might start printing diagnostic messages like [FAST] when appropriate as well as honoring mpsafenet=0. - Fix two more of the ppbus drivers' identify routines to function correctly in the mythical case of a machine with more than one ppbus.
* MFi386: revision 1.622.nyan2006-02-091-1/+2
| | | | | | | > Clear carry flag in get_mcontext so that setcontext does not > return a bogus error. MFC after: 3 days
OpenPOWER on IntegriCloud