| commit | 24834d2c8455a6eeee82e007d41d7e05986d134f | |
| author | Jay Sternberg <jay.e.sternberg@intel.com> | |
| Tue, 11 Jan 2011 23:41:00 +0000 (11 15:41 -0800) | ||
| committer | Wey-Yi Guy <wey-yi.w.guy@intel.com> | |
| Fri, 21 Jan 2011 23:50:33 +0000 (21 15:50 -0800) | ||
| tree | 76f261bf903ce7aa7458bec2a26aa115698efe2c | treesnapshot (tar.gz zip) |
| parent | fcdf1f73fe913c5f16b7f0547cc3df1b0796689f | commitdiff |
iwlwifi: correct debugfs data dumped from sram
the sram data dumped through the debugfs interface would only work properly
when dumping data on even u32 boundaries and swap bytes based on endianness
on that boundary making byte arrays impossible to read.
now addresses are displayed at the start of every line and the data is
displayed consistently if dumping 1 byte or 20 and regardless of what is the
starting address.
if no lenght given, address displayed is u32 in device format
Signed-off-by: Jay Sternberg <jay.e.sternberg@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
the sram data dumped through the debugfs interface would only work properly
when dumping data on even u32 boundaries and swap bytes based on endianness
on that boundary making byte arrays impossible to read.
now addresses are displayed at the start of every line and the data is
displayed consistently if dumping 1 byte or 20 and regardless of what is the
starting address.
if no lenght given, address displayed is u32 in device format
Signed-off-by: Jay Sternberg <jay.e.sternberg@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
| drivers/net/wireless/iwlwifi/iwl-debugfs.c | diffblobblamehistory |