diff options
| author | 2006-12-12 01:25:52 +0000 | |
|---|---|---|
| committer | 2007-02-05 16:58:42 -0500 | |
| commit | ee30276774451d657407855d95d9393ee8bc0bac (patch) | |
| tree | ceb02ea0a59acf90ac532c72e7ff294c2736f9a4 /tools/lib/python/kdoc/python_version.py | |
| parent | [PATCH] zd1211rw: 2 new ZD1211B device ID's (diff) | |
[PATCH] zd1211rw: Consistency for address space constants
The zd1211rw address space has confused me once too many times. This
patch introduces the following naming notation:
Memory space is split into segments (cr, fw, eeprom) and segments may
contain components (e.g. boot code inside eeprom). These names are
arbitrary and only for the description below:
x_START: Absolute address of segment start
(previously these were named such as CR_BASE_OFFSET, but they weren't
really offsets unless you were considering them as an offset to 0)
x_LEN: Segment length
x_y_LEN: Length of component y of segment x
x_y_OFFSET: Relative address of component y into segment x. The absolute
address for this component is (x_START + x_y_OFFSET)
I also renamed EEPROM registers to EEPROM data. These 'registers' can't
be written to using standard I/O and really represent predefined data
from the vendor.
Signed-off-by: Daniel Drake <dsd@gentoo.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
