Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

reggie_se(1) [osx man page]

REGGIE_SE(1)						    BSD General Commands Manual 					      REGGIE_SE(1)

NAME
reggie_se -- read and modify hardware registers SYNOPSIS
reggie_se [-d dev] [-D type] [-i index] [-r] [-w val] [-s n] [-S val] [-c n] [-C] [-l] [-x] [-b b:e] [-v] [-h] USAGE
To read a register: reggie_se -r [-d devclass] [-D devname] [-i index] [-v] -n register_name reggie_se -r [-d devclass] [-D devname] [-i index] [-v] -a register_addr -B reg_size To write a register: reggie_se -w value [-d devclass] [-D devname] [-i index] [-v] -n register_name reggie_se -w value [-d devclass] [-D devname] [-i index] [-v] -a register_addr -B reg_size To set a bit or range of bits: reggie_se -s bit_index [-d devclass] [-D devname] [-i index] [-v] -n register_name reggie_se -s bit_index [-d devclass] [-D devname] [-i index] [-v] -a register_addr -B reg_size reggie_se -S value -b b:e [-d devclass] [-D devname] [-i index] [-v] -n register_name reggie_se -S value -b b:e [-d devclass] [-D devname] [-i index] [-v] -a register_addr -B reg_size To clear a bit or range of bits: reggie_se -c bit_index [-d devclass] [-D devname] [-i index] [-v] -n register_name reggie_se -c bit_index [-d devclass] [-D devname] [-i index] [-v] -a register_addr -B reg_size reggie_se -C -b b:e [-d devclass] [-D devname] [-i index] [-v] -n register_name reggie_se -C -b b:e [-d devclass] [-D devname] [-i index] [-v] -a register_addr -B reg_size To get a list of available registers: reggie_se -l [-d devclass] [-D devname] User supplied values are interpreted as follows: Hexadecimal (base-16) if prefixed by '0x' or '0X' Octal (base-8) if prefixed by '0o' or '0O' Binary (base-2) if prefixed by '0b' or '0B' Decimal (base-10) if no prefix DESCRIPTION
reggie_se is used to read and modify hardware registers and physical memory. -d dev specify target device by class c cpu (DEFAULT) p pci device -D type specify target device by name CPU: 750, 750FXDDR1, 750FXDDR2, 7400, 7410, 7450, 7455, 7447A, 7457, 970 Memory: PhysAddr Expansion: PCI -i index a target all devices (e.g. CPUn) n target only device at index n (e.g. -i 0 = CPU0) -r read register -w val write val to register -s n set register bit n -S val set register bit range to val (specify bit range with -b option) -c n clear register bit n -C clear register bit range (specify bit range with -b option) -l list registers and exit -x list expansion devices (PCI) and exit -b begin:end specify bit index range from begin to end for -S and -C actions -v verbose mode (prints bit definitions) -h print usage information and exit Darwin July 30, 2004 Darwin

Check Out this Related Man Page

DEVICE(9)						   BSD Kernel Developer's Manual						 DEVICE(9)

NAME
device -- an abstract representation of a device SYNOPSIS
typedef struct device *device_t; DESCRIPTION
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into, disk drives attached to the expansion card etc. The system defines one device, root_bus and all other devices are created dynamically during autoconfiguration. Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and other devices will be added as children of their relevant bus. The devices in a system form a tree. All devices except root_bus have a parent (see device_get_parent(9)). In addition, any device can have children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and device_delete_child(9)). A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a devclass (see device_get_devclass(9) and devclass(9)). Various other attributes of the device include a unit number (see device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe- cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)). Devices can be in one of several states: DS_NOTPRESENT the device has not been probed for existence or the probe failed DS_ALIVE the device probe succeeded but not yet attached DS_ATTACHED the device has been successfully attached DS_BUSY the device is currently open The current state of the device can be determined by calling device_get_state(9). SEE ALSO
devclass(9), driver(9) AUTHORS
This manual page was written by Doug Rabson. BSD
June 16, 1998 BSD
Man Page