> But there is a problem with it, which is why it's hard to do this. Please > read the wiki page Greg posted which explains why you cannot include chip > specific headers in board.h > > What is it that must go in there? >
All this comes from my idea of solving driver balkanization. It's illogical to incur in an extra step in the problematic direction (needing a per board function to fill in GPIO structure that can be filled with a unique, system-wide function) just to keep header files in src/ instead of include/