summaryrefslogtreecommitdiffstats
path: root/sys/dev/altera/avgen/altera_avgen.c
Commit message (Collapse)AuthorAgeFilesLines
* MFC r274820:brooks2014-12-021-13/+0
| | | | | | | | Merge from CheriBSD (2e28d2a3090239b30481f35dc452ad95a5c57389): Remove initalized, but unused devname variable Sponsored by: DARPA, AFRL
* Merge Perforce changeset 219952 to head:rwatson2013-01-131-0/+2
| | | | | | | Make different bus attachments for Altera and Terasice device drivers share the same devclass_t. Sponsored by: DARPA, AFRL
* Merge Perforce changeset 219940 to head:rwatson2013-01-131-83/+11
| | | | | | | | Rework altera_avgen(4) to cleanly(ish) separate nexus bus attachment from the driver itself. This should allow us to plug in an fdt attachment more easily. Sponsored by: DARPA, AFRL
* Add altera_avgen(4), a generic device driver to be used by hard and softrwatson2012-08-251-0/+451
CPU cores on Altera FPGAs. The device driver allows memory-mapped devices on Altera's Avalon SoC bus to be exported to userspace via device nodes. device.hints directories dictate device name, permissible access methods, physical address and length, and I/O alignment. Devices can be accessed using read(2)/write(2), but also memory mapped in userspace using mmap(2). Devices attach directly to the Nexus, as is common for embedded device drivers; in the future something more mature might be desirable. There is currently no facility to support directing device-originated interrupts to userspace. In the future, this device driver may be renamed to socgen(4), as it can in principle also be used with other system-on-chip (SoC) busses, such as Axi on ASICs and FPGAs. However, we have only tested it on Avalon busses with memory-mapped ROMs, frame buffers, etc. Sponsored by: DARPA, AFRL
OpenPOWER on IntegriCloud