Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

terasic_mtl(4) [freebsd man page]

TERASIC_MTL(4)						   BSD Kernel Interfaces Manual 					    TERASIC_MTL(4)

NAME
terasic_mtl -- driver for the Terasic/Cambridge Multi-Touch LCD device SYNOPSIS
device terasic_mtl In /boot/device.hints: hint.terasic_mtl.0.at="nexus0" hint.terasic_mtl.0.reg_maddr=0x70400000 hint.terasic_mtl.0.reg_msize=0x1000 hint.terasic_mtl.0.pixel_maddr=0x70000000 hint.terasic_mtl.0.pixel_msize=0x177000 hint.terasic_mtl.0.text_maddr=0x70177000 hint.terasic_mtl.0.text_msize=0x2000 DESCRIPTION
The terasic_mtl device driver provides support for the Terasic Multi-Touch LCD combined as controlled by a University of Cambridge's IP Core. Three device nodes are instantiated, representing various services supported by the device: terasic_regX Memory-mapped register interface, including touch screen input. terasic_pixelX Memory-mapped pixel-oriented frame buffer. terasic_textX Memory-mapped text-oriented frame buffer. terasic_mtl devices are also attached to the syscons(4) framework, which implements a VT-compatible terminal connected to the tty(4) frame- work. ttyvX device nodes may be added to ttys(5) in order to launch login(1) sessions at boot. Register, text, and pixel devices may be accessed using read(2) and write(2) system calls, and also memory mapped using mmap(2). SEE ALSO
login(1), ioctl(2), mmap(2), poll(2), read(2), write(2), syscons(4), tty(4), ttys(5) HISTORY
The terasic_mtl device driver first appeared in FreeBSD 10.0. AUTHORS
The terasic_mtl device driver and this manual page were developed by SRI International and the University of Cambridge Computer Laboratory under DARPA/AFRL contract (FA8750-10-C-0237) (``CTSRD''), as part of the DARPA CRASH research programme. This device driver was written by Robert N. M. Watson. BUGS
The syscons(4) attachment does not support the hardware cursor feature. A more structured interface to control registers using the ioctl(2) system call, would sometimes be preferable to memory mapping. For touch screen input, it would be highly desirable to offer a streaming interface whose events can be managed using poll(2) and related system calls, with the kernel performing polling rather than the userspace application. terasic_mtl supports only a nexus bus attachment, which is appropriate for system-on-chip busses such as Altera's Avalon bus. If the IP core is configured off of another bus type, then additional bus attachments will be required. BSD
August 18, 2012 BSD

Check Out this Related Man Page

DEVICE.HINTS(5) 					      BSD File Formats Manual						   DEVICE.HINTS(5)

NAME
device.hints -- device resource hints DESCRIPTION
The device.hints file is read in by the boot loader(8) when the system is about to start, and its contents are passed to the kernel. It con- tains various variables to control the boot behavior of the kernel. These variables are typically ``device hints''. The file contains one variable per line. Lines starting with the '#' character are comments and are ignored by the boot loader. After the file is read by the boot loader, you may examine the variables with the show command, and may add a new variable, modify an exist- ing one, or delete a variable with the set and unset commands of the boot loader (see loader(8)). After the system has started, you can dump these variables with the kenv(1) command. DEVICE HINTS
Device hint variables are used by device drivers to set up the device. They are most often used by ISA device drivers to specify where the driver will probe for the relevant devices, and what resources it will attempt to use. A device hint line looks like: hint.driver.unit.keyword="value" where driver is the name of a device driver, unit is the unit number, and keyword is the keyword of the hint. The keyword may be: at specifies a bus to which the device is attached. port specifies the start address of I/O ports to be used by the device. portsize specifies the number of ports used by the device. irq is the interrupt line number to be used. drq is the DMA channel number. maddr specifies the physical memory address used by the device. msize specifies the physical memory size used by the device. flags sets various flag bits for the device. disabled can be set to "1" to disable the device. A device driver may require one or more hint lines with these keywords, and may accept other keywords not listed here, through resource_int_value(9). Consult individual device drivers' manual pages for available keywords and their possible values. FILES
/boot/device.hints Device resource hints file. /sys/ARCH/conf/GENERIC.hints Sample resource hints for the GENERIC kernel. /sys/ARCH/conf/NOTES Notes on the kernel configuration file and device resource hints. EXAMPLES
The following example sets up resources for the sio(4) driver on the ISA bus: hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x10" hint.sio.0.irq="4" The following example disables the ACPI driver: hint.acpi.0.disabled="1" SEE ALSO
kenv(1), loader.conf(5), loader(8), resource_int_value(9) HISTORY
The device.hints file first appeared in FreeBSD 5.0. BSD
September 11, 2009 BSD
Man Page