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

ALTERA_ATSE(4)						   BSD Kernel Interfaces Manual 					    ALTERA_ATSE(4)

NAME

     atse -- driver for the Altera Triple-Speed Ethernet MegaCore

SYNOPSIS

     device atse
     options ATSE_CFI_HACK

     In /boot/device.hints:
     hint.atse.0.at="nexus0"
     hint.atse.0.maddr=0x7f007000
     hint.atse.0.msize=0x540
     hint.atse.0.rc_irq=1
     hint.atse.0.rx_maddr=0x7f007500
     hint.atse.0.rx_msize=0x8
     hint.atse.0.rxc_maddr=0x7f007520
     hint.atse.0.rxc_msize=0x20
     hint.atse.0.tx_irq=2
     hint.atse.0.tx_maddr=0x7f007400
     hint.atse.0.tx_msize=0x8
     hint.atse.0.txc_maddr=0x7f007420
     hint.atse.0.txc_msize=0x20
     hint.e1000phy.0.at="miibus0"
     hint.e1000phy.0.phyno=0

DESCRIPTION

     The atse device driver provides support for the Altera Triple-Speed Ethernet MegaCore.

HARDWARE

     The current version of the atse driver supports the Ethernet MegaCore as described in version 11.1 of Altera's documentation when the device
     is configured with internal FIFOs.

MAC SELECTION

     The default MAC address for each atse interface is derived from a value stored in cfi(4) flash.  The value is managed by the atsectl(8) util-
     ity.

     Only a single MAC address may be stored in flash.	If the address begins with the Altera prefix 00:07:ed and ends in 00 then up to 16
     addresses will be derived from it by adding the unit number of the interface to the stored address.  For other prefixes, the address will be
     assigned to atse0 and random addresses will be used for other interfaces.	If the stored address is invalid, for example all zero's, multi-
     cast, or the default address shipped on all DE4 boards (00:07:ed:ff:ed:15) then a random address is generated when the device is attached.

SEE ALSO

     miibus(4), netintro(4), ifconfig(8)

     Triple-Speed Ethernet MegaCore Function User Guide, Altera Corporation, November 2011.

HISTORY

     The atse device driver first appeared in FreeBSD 10.0.

AUTHORS

     The atse 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 Bjoern
     A. Zeeb.

BUGS

     The atse driver only supports a single configuration of the MegaCore as installed on the Terasic Technologies Altera DE4 Development and Edu-
     cation Board.

     Only gigabit Ethernet speeds are currently supported.

BSD
								   May 21, 2014 							       BSD