summaryrefslogtreecommitdiffstats
path: root/sys/dev/dcons
Commit message (Collapse)AuthorAgeFilesLines
* Last minute TTY API change: remove mutex argument from tty_alloc().ed2009-05-291-1/+1
| | | | | | | | | | I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future.
* Reduce the dcons polling frequency to 25 Hz.ed2009-04-061-1/+1
| | | | | | | | | | It makes little sense to use 100 Hz polling in dcons. We cannot live without polling, because that's just how dcons works. It polls the buffer filled by the firewire hardware. 25 Hz is probably enough for most use cases. Discussed with: rwatson Tested by: kan
* Fix logic in MOD_LOAD handler to call dcons_attach after all successfulkan2009-04-061-1/+2
| | | | | | dcons_drv_init invocations. Testing return value for 0 does not work for cases where dcons_drv_init was called already as part of low level console initialization.
* We need to initialize the console for dcons to work.imp2009-03-131-0/+1
| | | | Submitted by: nork@
* Check the return values of contigmalloc(9) as well as bus_dma(9)marius2009-01-072-11/+24
| | | | | | | | | | | | | | functions and stop attaching of dcons(4) and dcons_crom(4) if they indicate failure. This fixes a panic seen on sparc64 machines with no free physical memory in the requested 32-bit region but still doesn't make dcons(4)/dcons_crom(4) these work. I think the latter can be fixed by simply specifying ~0UL as the upper limit for contigmalloc(9) and letting the bounce pages and the IOMMU respectively handle limitations of the DMA engine. I didn't want to change that without the consensus of simokawa@ though, who unfortunately didn't reply so far. MFC after: 1 week
* Given that the buffer dcons_crom(4) exposes is used for both inputmarius2008-11-191-1/+1
| | | | | | | | | | | and output, set BUS_DMA_COHERENT when creating the DMA map used for loading the buffer. As a side-effect this solves locking issues on sparc64 when dcons(4) calls bus_dmamap_sync(9) while in an interrupt filter, which are executed in a critical section, and iommu(4) has to use a sleep lock when taking advantage of the streaming buffer. Reported and tested by: kensmith Approved by: simokawa
* Also make dcons(4) use MPSAFE callouts.ed2008-11-191-1/+1
| | | | | The callout locks the TTY layer the way it should, so there is no reason why its callout shouldn't set this flag.
* Integrate the new MPSAFE TTY layer to the FreeBSD operating system.ed2008-08-202-346/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The last half year I've been working on a replacement TTY layer for the FreeBSD kernel. The new TTY layer was designed to improve the following: - Improved driver model: The old TTY layer has a driver model that is not abstract enough to make it friendly to use. A good example is the output path, where the device drivers directly access the output buffers. This means that an in-kernel PPP implementation must always convert network buffers into TTY buffers. If a PPP implementation would be built on top of the new TTY layer (still needs a hooks layer, though), it would allow the PPP implementation to directly hand the data to the TTY driver. - Improved hotplugging: With the old TTY layer, it isn't entirely safe to destroy TTY's from the system. This implementation has a two-step destructing design, where the driver first abandons the TTY. After all threads have left the TTY, the TTY layer calls a routine in the driver, which can be used to free resources (unit numbers, etc). The pts(4) driver also implements this feature, which means posix_openpt() will now return PTY's that are created on the fly. - Improved performance: One of the major improvements is the per-TTY mutex, which is expected to improve scalability when compared to the old Giant locking. Another change is the unbuffered copying to userspace, which is both used on TTY device nodes and PTY masters. Upgrading should be quite straightforward. Unlike previous versions, existing kernel configuration files do not need to be changed, except when they reference device drivers that are listed in UPDATING. Obtained from: //depot/projects/mpsafetty/... Approved by: philip (ex-mentor) Discussed: on the lists, at BSDCan, at the DevSummit Sponsored by: Snow B.V., the Netherlands dcons(4) fixed by: kan
* Spell KDB_REQ_REBOOT correctly.peter2008-05-051-1/+1
|
* Expand kdb_alt_break a little, most commonly used with the optionpeter2008-05-041-10/+24
| | | | | | | | | | | | | | | | | | | ALT_BREAK_TO_DEBUGGER. In addition to "Enter ~ ctrl-B" (to enter the debugger), there is now "Enter ~ ctrl-P" (force panic) and "Enter ~ ctrl-R" (request clean reboot, ala ctrl-alt-del on syscons). We've used variations of this at work. The force panic sequence is best used with KDB_UNATTENDED for when you just want it to dump and get on with it. The reboot request is a safer way of getting into single user than a power cycle. eg: you've hosed the ability to log in (pam, rtld, etc). It gives init the reboot signal, which causes an orderly reboot. I've taken my best guess at what the !x86 and non-sio code changes should be. This also makes sio release its spinlock before calling KDB/DDB.
* Add a new 'why' argument to kdb_enter(), and a set of constants to userwatson2007-12-251-2/+4
| | | | | | | | | for that argument. This will allow DDB to detect the broad category of reason why the debugger has been entered, which it can use for the purposes of deciding which DDB script to run. Assign approximate why values to all current consumers of the kdb_enter() interface.
* We don't need to call dcons_poll event handlers if KDB is not active.simokawa2007-08-171-3/+9
| | | | Approved by: re (kensmith)
* - Don't force to be the GDB port since dcons(4) is in GENERIC now.simokawa2007-06-111-1/+5
| | | | | | To enable the GDB port of dcons(4), you need to put dcons_gdb=1 in /boot/loader.conf.
* Don't invalidate dcons buffer on shutdown.simokawa2007-06-081-0/+2
| | | | We would like to keep connection after halt.
* Add the address of IDT in the configuration ROM. (i386/amd64 only)simokawa2007-06-082-0/+27
| | | | | | | | | | | | A change to dconschat(8) will follow so that it can bomb this address over FireWire to reset a wedged system. Though this method is just a hack and far from perfection, it should be useful if you don't want to go machine room just to reset or to power-cycle a machine without remote-managed power supply. And much better than doing: # fwcontrol -m target-eui64 # dd if=/dev/zero of=/dev/fwmem0.2 bs=1m
* Replace breakpoint() with kdb_enter().simokawa2007-06-081-2/+2
|
* Poll bus resets on FireWire while kdb/gdb is active.simokawa2007-06-083-0/+19
| | | | | | | | | | | | | | | Now, it's safe to call the fwohci interrupt(polling) routine while ddb/gdb is active. After this change, a dcons connnection over FireWire can survive bus resets even in kernel debugger. This means that it is not too late to plug a FireWire cable after a panic to investigate the problem. Actually there is a small window(between a jump to kernel from loader and initialization of dcons_crom) in which no one can take care of a bus reset. Except that window, firewire console should keep working from loader to reboot even with a panic and a bus reset. (as far as you enable LOADER_FIREWIRE_SUPPORT)
* We should better ignore a break on gdb port if gdb is not enabled.simokawa2007-05-281-2/+2
|
* Change default value of hw.firewire.dcons_crom.force_console to 0simokawa2007-05-271-1/+1
| | | | | | for least astonishment. MFC after: 3 days
* Make compile without GDB option.simokawa2007-05-271-4/+11
| | | | MFC after: 3 days
* Include stand.h for loader.simokawa2007-05-251-0/+3
| | | | MFC after: 3 days
* Sweep kernel replacing suser(9) calls with priv(9) calls, assigningrwatson2006-11-061-1/+3
| | | | | | | | | | | | | specific privilege names to a broad range of privileges. These may require some future tweaking. Sponsored by: nCircle Network Security, Inc. Obtained from: TrustedBSD Project Discussed on: arch@ Reviewed (at least in part) by: mlaier, jmg, pjd, bde, ceri, Alex Lyashkov <umka at sevcity dot net>, Skip Ford <skip dot ford at verizon dot net>, Antoine Brodin <antoine dot brodin at laposte dot net>
* Convert to new console interface.phk2006-05-261-9/+7
|
* Eliminate gdb_checkc member from GDB_DBGPORT(), it is never used.phk2006-05-261-9/+1
| | | | | Use polling behaviour for gdb_getc() where convenient, this edges us closer to the console code.
* Use ttyalloc() instead of ttymalloc()phk2006-01-041-2/+2
|
* Fix -Wundef warnings found when compiling i386 LINT, GENERIC andru2005-12-051-3/+3
| | | | custom kernels.
* Make ttyconsolemode() call ttsetwater() so that drivers don't have to.phk2005-10-161-1/+0
|
* Start each of the license/copyright comments with /*-, minor shuffle of linesimp2005-01-065-5/+5
|
* Use dcons buffer passed by loader on amd64.simokawa2004-10-281-2/+4
|
* - Use quad_t for dcons buffer address and size.simokawa2004-10-241-4/+11
| | | | - Allow read/write access to dcons buffer passed by loader(8).
* Check _BOOT flag.simokawa2004-10-221-3/+3
|
* Add new function ttyinitmode() which sets our systemwide defaultphk2004-10-181-6/+1
| | | | | | | | | | | | | | modes on a tty structure. Both the ".init" and the current settings are initialized allowing the function to be used both at attach and open time. The function takes an argument to decide if echoing should be enabled. Echoing should not be enabled for regular physical serial ports unless they are consoles, in which case they should be configured by ttyconsolemode() instead. Use the new function throughout.
* Fix warnings on non-i386 arch.simokawa2004-10-141-0/+2
| | | | Submitted by: keramida
* - Split dcons core code and OS dependent code.simokawa2004-10-135-650/+883
| | | | | | - Implement dcons_ischar() and dcons_load_buffer(). - If loader passed a dcons buffer address, keep using it. (We still need a patch to cheat memory management system.)
* Invalidate dcons buffer on shutdown.simokawa2004-09-261-0/+1
|
* Sync with DragonFly BSD.simokawa2004-09-241-17/+93
|
* Preparation commit for the tty cleanups that will follow in the nearphk2004-07-151-2/+2
| | | | | | | | | future: rename ttyopen() -> tty_open() and ttyclose() -> tty_close(). We need the ttyopen() and ttyclose() for the new generic cdevsw functions for tty devices in order to have consistent naming.
* Do a pass over all modules in the kernel and make them return EOPNOTSUPPphk2004-07-151-0/+3
| | | | | | | | for unknown events. A number of modules return EINVAL in this instance, and I have left those alone for now and instead taught MOD_QUIESCE to accept this as "didn't do anything".
* Re-enable debugger port.simokawa2004-07-131-3/+124
|
* Update for the KDB framework:marcel2004-07-101-49/+4
| | | | | | | | | | | | o Use kdb_alt_break() to handle the alternate break sequence instead of handcoding it here. o Remove GDB kluges to make this driver work with the pre-KDB remote GDB code. o Call kdb_enter() instead of Debugger(). Note that with this commit the dcons(4) driver cannot be used for remote debugging anymore. This driver has to use the new GDB debug port interface instead. Such has not been done yet.
* Second half of the dev_t cleanup.phk2004-06-171-1/+1
| | | | | | | | | | | The big lines are: NODEV -> NULL NOUDEV -> NODEV udev_t -> dev_t udev2dev() -> findcdev() Various minor adjustments including handling of userland access to kernel space struct cdev etc.
* Do the dreaded s/dev_t/struct cdev */phk2004-06-161-6/+6
| | | | Bump __FreeBSD_version accordingly.
* Machine generated patch which changes linedisc calls from accessingphk2004-06-041-4/+4
| | | | | | linesw[] directly to using the ttyld...() functions The ttyld...() functions ar inline so there is no performance hit.
* Gainfully employ the new ttyioctl in the trivial cases.phk2004-06-011-25/+0
|
* There is no need to explicitly call ttwakeup() and ttwwakeup() afterphk2004-06-011-2/+0
| | | | | ttyclose() has been called. It's already been done once by ttyclose, and probably once by the line-discipline too.
* ttyclose() increments t_gen. Remove redundant increments in drivers.phk2004-06-011-1/+0
|
* Add missing <sys/module.h> includesphk2004-05-302-0/+2
|
* Device megapatch 4/6:phk2004-02-211-1/+2
| | | | | | | | Introduce d_version field in struct cdevsw, this must always be initialized to D_VERSION. Flip sense of D_NOGIANT flag to D_NEEDGIANT, this involves removing four D_NOGIANT flags and adding 145 D_NEEDGIANT flags.
* Device megapatch 3/6:phk2004-02-211-3/+1
| | | | | | | | | | | | Add missing D_TTY flags to various drivers. Complete asserts that dev_t's passed to ttyread(), ttywrite(), ttypoll() and ttykqwrite() have (d_flags & D_TTY) and a struct tty pointer. Make ttyread(), ttywrite(), ttypoll() and ttykqwrite() the default cdevsw methods for D_TTY drivers and remove the explicit initializations in various drivers cdevsw structures.
* Device megapatch 1/6:phk2004-02-211-2/+0
| | | | | | | Free approx 86 major numbers with a mostly automatically generated patch. A number of strategic drivers have been left behind by caution, and a few because they still (ab)use their major number.
OpenPOWER on IntegriCloud