remote talking to AR9271

bruce m beach brucembeach at gmail.com
Mon Apr 11 19:45:34 PDT 2016


Hello

 I'm still working on cleaning up the ath9k_htc firmware (although only for
ar9271) and although its still a long way on the horizon, it looks like there
is an end in sight, in which case I'll release it. Currently all code is in 3
directories (with no subdirectories)

   ram_code, rom_code, include

where the set of includes suffice both for the ram and rom.  Both ram and rom
are compiling but the rom is still bogus until I do some stuff with the
linking. There is still a block of assembler code that I still have to move in
place and get to build.


What I'm wondering about is is in sys_cfg.h Just out of a whim I tried
altering some of the #defines. For instance setting

#define SYSTEM_MODULE_UART 0

breaks the builds(both rom and ram). That is okay, I'll test them all and
fix them if they break. I think what should happen is setting
SYSTEM_MODULE_UART  to zero should just elimate the UART code( and possibly
all the debugging code) for builds where there is no debugging.

The question that I have is setting

SYSTEM_MODULE_PCI 1

breaks the build. It seems to be set to zero on k2, and in addition I'm
wondering if SYSTEM_MODULE_PCI and USB are mutually exclusive. Okay
so I look at the AR9271.pdf sheet and realize that there is is only USB so the
question is moot. I can eliminate the PCI stuff altogether. The only problem
is that once I am finished I am open to merging the magpie stuff back in so
maybe for now I should leave the PCI stuff in.

Bruce



More information about the ath9k_htc_fw mailing list