[PATCH] zd1211rw: Consistency for address space constants

Browse source

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>

...

This commit is contained in:

Daniel Drake 2006-12-12 01:25:52 +00:00 • committed by Jeff Garzik

parent a2bdcc6792

commit ee30276774

3 changed files with 75 additions and 64 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

117

drivers/net/wireless/zd1211rw/zd_chip.h

View file

2

drivers/net/wireless/zd1211rw/zd_types.h

View file

18

drivers/net/wireless/zd1211rw/zd_usb.c

View file