Squashed 'tmk_core/' changes from caca2c0..dc0e46e

dc0e46e Rename LUFA to LUFA-git
3bfa7fa Remove LUFA-120730
215b764 Merge commit 'afa0f22a9299686fd88f58ce09c5b521ac917e8f' as 'protocol/lufa/LUFA'
afa0f22 Squashed 'protocol/lufa/LUFA/' content from commit def7fca
c0c42fa Remove submodule of LUFA
30f897d Merge commit '87ced33feb74e79c3281dda36eb6d6d153399b41' as 'protocol/usb_hid/USB_Host_Shield_2.0'
87ced33 Squashed 'protocol/usb_hid/USB_Host_Shield_2.0/' content from commit aab4a69
14f6d49 Remove submodule of USB_Host_Shield_2.0

git-subtree-dir: tmk_core
git-subtree-split: dc0e46eaa4367d4e218f8816e3c117895820f07c

1 files changed, 0 insertions, 27 deletions

diff --git a/protocol/lufa/LUFA-120730/LUFA/DoxygenPages/WritingBoardDrivers.txt b/protocol/lufa/LUFA-120730/LUFA/DoxygenPages/WritingBoardDrivers.txt
deleted file mode 100644
index 1b3326907..000000000
--- a/protocol/lufa/LUFA-120730/LUFA/DoxygenPages/WritingBoardDrivers.txt
+++ /dev/null
@@ -1,27 +0,0 @@
-/** \file

- *

- *  This file contains special DoxyGen information for the generation of the main page and other special

- *  documentation pages. It is not a project source file.

- */

-

-/** \page Page_WritingBoardDrivers Writing LUFA Board Drivers

- *

- *  LUFA ships with several basic pre-made board drivers, to control hardware present on the supported board

- *  hardware - such as Dataflash ICs, LEDs, Joysticks, or other hardware peripherals. When compiling an application

- *  which makes use of one or more board drivers located in LUFA/Drivers/Board, you must also indicate what board

- *  hardware you are using in your project makefile. This is done by defining the BOARD macro using the -D switch

- *  passed to the compiler, with a constant of BOARD_{Name}. For example <b>-DBOARD=BOARD_USBKEY</b> instructs the

- *  compiler to use the USBKEY board hardware drivers.

- *

- *  If your application does not use *any* board level drivers, you can omit the definition of the BOARD macro.

- *  However, some users may wish to write their own custom board hardware drivers which are to remain compatible

- *  with the LUFA hardware API. To do this, the BOARD macro should be defined to the value BOARD_USER. This indicates

- *  that the board level drivers should be located in a folder named "Board" located inside the application's folder.

- *

- *  When used, the driver stub files located in the LUFA/CodeTemplates/DriverStubs folder should be copied to the user

- *  Board/ directory, and fleshed out to include the values and code needed to control the custom board hardware. Once

- *  done, the existing LUFA board level APIs (accessed in the regular LUFA/Drivers/Board/ folder) will redirect to the

- *  user board drivers, maintaining code compatibility and allowing for a different board to be selected through the

- *  project makefile with no code changes.

- */

-