Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ ddi_mem_getb(9F) — SunOS 5.5.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ddi_mem_putb(9F)

ddi_mem_rep_getb(9F)

ddi_mem_rep_putb(9F)

ddi_regs_map_setup(9F)

ddi_device_acc_attr(9S)

ddi_mem_getb(9F)

NAME

ddi_mem_getb, ddi_mem_getw, ddi_mem_getl, ddi_mem_getll − read  data from mapped device in the memory space or allocated DMA memory

SYNOPSIS

#include <sys/ddi.h>
#include <sys/sunddi.h>

uchar_t ddi_mem_getb(ddi_acc_handle_t handle, uchar_t ∗dev_addr);

ushort_t ddi_mem_getw(ddi_acc_handle_t handle, ushort_t ∗dev_addr);

ulong_t ddi_mem_getl(ddi_acc_handle_t handle, ulong_t ∗dev_addr);

unsigned long long ddi_mem_getll(ddi_acc_handle_t handle,

unsigned long long ∗dev_addr);

ARGUMENTS

handle The data access handle returned from setup calls, such as ddi_regs_map_setup(9F). 

dev_addr Base device address. 

INTERFACE LEVEL

Solaris DDI specific (Solaris DDI). 

DESCRIPTION

These routines generate a read of various sizes from memory space or allocated DMA memory.  The ddi_mem_getb(), ddi_mem_getw(), ddi_mem_getl(), and ddi_mem_getll() functions read 8 bits, 16 bits, 32 bits and 64 bits of data, respectively, from the device address, dev_addr, in memory space.

Each individual datum will automatically be translated to maintain a consistent view between the host and the device based on the encoded information in the data access handle. The translation may involve byte-swapping if the host and the device have incompatible endian characteristics. 

CONTEXT

These functions can be called from user, kernel, or interrupt context. 

SEE ALSO

ddi_mem_putb(9F), ddi_mem_rep_getb(9F), ddi_mem_rep_putb(9F), ddi_regs_map_setup(9F), ddi_device_acc_attr(9S)

SunOS 5.5.1  —  Last change: 28 Oct 1994

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026