Add link to third-party signed version of the official FLIP DFU driver for 64-bit Windows OSes to the DFU bootloader readme file.

Add HTML anchor links to URLs in the documentation to ensure that they are rendered correctly in the generated documentation.

8 files changed, 20 insertions, 13 deletions

diff --git a/Bootloaders/DFU/BootloaderDFU.txt b/Bootloaders/DFU/BootloaderDFU.txt
index ca2f1651d..1f5eeb2f4 100644
--- a/Bootloaders/DFU/BootloaderDFU.txt
+++ b/Bootloaders/DFU/BootloaderDFU.txt
@@ -52,10 +52,14 @@
  *  software to load firmware onto the AVR.

  *  

  *  This bootloader is compatible with Atmel's FLIP application. However, it requires the use of Atmel's

- *  DFU drivers. You will need to install Atmel's DFU drivers prior to using this bootloader.

+ *  DFU drivers. You will need to install Atmel's DFU drivers prior to using this bootloader. If you are

+ *  using a 64 bit Windows OS, you will need to either disable the driver signing requirement (see online

+ *  tutorials for details) or use a digitally signed version of the official Atmel driver provided by a

+ *  third party AVR user at

+ *  <a>http://www.avrfreaks.net/index.php?module=Freaks%20Academy&func=viewItem&item_id=2196&item_type=project</a>.

  *  

  *  As an open-source option, this bootloader is also compatible with the Linux Atmel USB DFU Programmer

- *  software, available for download at http://sourceforge.net/projects/dfu-programmer/.

+ *  software, available for download at <a>http://sourceforge.net/projects/dfu-programmer/</a>.

  *  

  *  If SECURE_MODE is defined as true, upon start-up the bootloader will be locked, with only the chip erase

  *  function available (similar to Atmel's DFU bootloader). If SECURE_MODE is defined as false, all functions 

diff --git a/Bootloaders/TeensyHID/TeensyHID.txt b/Bootloaders/TeensyHID/TeensyHID.txt
index 4cf13082b..3a450f9e4 100644
--- a/Bootloaders/TeensyHID/TeensyHID.txt
+++ b/Bootloaders/TeensyHID/TeensyHID.txt
@@ -45,7 +45,7 @@
  *  \section SSec_Description Project Description: 

  *

  * This bootloader enumerates to the host as a HID Class device, allowing for Teensy compatible programming

- * software to load firmware onto the AVR, such as the official software at http://www.pjrc.com/teensy/.

+ * software to load firmware onto the AVR, such as the official software at <a>http://www.pjrc.com/teensy/</a>.

  *  

  * Out of the box this bootloader builds for the AT90USB162, and will fit into 4KB of bootloader space.

  *

diff --git a/Demos/Host/LowLevel/MouseHost/MouseHost.c b/Demos/Host/LowLevel/MouseHost/MouseHost.c
index f6a2f3820..ab0eadc6c 100644
--- a/Demos/Host/LowLevel/MouseHost/MouseHost.c
+++ b/Demos/Host/LowLevel/MouseHost/MouseHost.c
@@ -138,6 +138,9 @@ void ReadNextReport(void)
 	/* Check to see if a packet has been received */

 	if (!(Pipe_IsINReceived()))

 	{

+		/* No packet received (no movement), turn off LEDs */

+		LEDs_SetAllLEDs(LEDS_NO_LEDS);

+	

 		/* Refreeze HID data IN pipe */

 		Pipe_Freeze();

 			

diff --git a/LUFA/ManPages/ChangeLog.txt b/LUFA/ManPages/ChangeLog.txt
index b27b724ed..76e939067 100644
--- a/LUFA/ManPages/ChangeLog.txt
+++ b/LUFA/ManPages/ChangeLog.txt
@@ -43,7 +43,7 @@
   *  <b>Fixed:</b>

   *  - Fixed possible lockup in the CDC device class driver, when the host sends data that is a multiple of the

   *    endpoint's bank

-  *  - Fixed swapped paremeters in the HID state memory copy call while processing a HID PUSH item in the HID report parser

+  *  - Fixed swapped parameters in the HID state memory copy call while processing a HID PUSH item in the HID report parser

   *  - Fixed memory corruption HID report parser when too many COLLECTION or PUSH items were processed

   *  - Fixed HID report parser not resetting the FEATURE item count when a REPORT ID item is encountered

   *  - Fixed USBtoSerial demos not reading in UDR1 when the USART receives data but the USB interface is not enumerated,

@@ -56,10 +56,10 @@
   *  - Fixed Device mode HID Class driver not explicitly initializing the ReportSize parameter to zero before calling callback

   *    routine, so that ignored callbacks don't cause incorrect data to be sent

   *  - Fixed StillImageHost not correctly freezing and unfreezing data pipes while waiting for a response block header

-  *  - Fixed error in PrinterHost preventing the full page data from being sent to the attached device

-  *  - CDC based demos and project now work under 64 bit versions of Windows (thanks to Ronny Hanson, Thomas Bleeker)

-  *  - Re-add in flip, flip-ee, dfu and dfu-ee targets to project makefiles (thanks to Opendous Inc.)

-  *  - Fix allowable F_CPU values comment in project makefiles

+  *  - Fixed error in the PrinterHost demo preventing the full page data from being sent to the attached device (thanks to John Andrews)

+  *  - Fixed CDC based demos and projects' INF driver files under 64 bit versions of Windows (thanks to Ronny Hanson, Thomas Bleeker)

+  *  - Re-add in missing flip, flip-ee, dfu and dfu-ee targets to project makefiles (thanks to Opendous Inc.)

+  *  - Fix allowable F_CPU values comment in project makefiles to more accurately reflect the allowable values on the USB AVRs

   *  - Fixed DFU and CDC class bootloaders on the series 2 USB AVRs, corrected invalid signatures, added support for the new

   *    ATMEGAxxx2 series 2 variant AVRs to the DFU bootloader

   *

diff --git a/LUFA/ManPages/CompilingApps.txt b/LUFA/ManPages/CompilingApps.txt
index b1d5ed6ed..7cea32121 100644
--- a/LUFA/ManPages/CompilingApps.txt
+++ b/LUFA/ManPages/CompilingApps.txt
@@ -11,7 +11,7 @@
  *  \section Sec_Prerequisites Prerequisites

  *  Before you can compile any of the LUFA library code or demos, you will need a recent distribution of avr-libc (1.6.2+)

  *  and the AVR-GCC (4.2+) compiler. For Windows users, the best way to obtain these is the WinAVR project

- *  (http://winavr.sourceforge.net) as this provides a single-file setup for everything required to compile your

+ *  (<a>http://winavr.sourceforge.net</a>) as this provides a single-file setup for everything required to compile your

  *  own AVR projects.

  *

  *  \section Sec_Compiling Compiling a LUFA Application

diff --git a/LUFA/ManPages/Donating.txt b/LUFA/ManPages/Donating.txt
index fad401de7..c85e93e49 100644
--- a/LUFA/ManPages/Donating.txt
+++ b/LUFA/ManPages/Donating.txt
@@ -14,6 +14,6 @@
  *  and supporter. Please consider donating a small amount to support this and my future Open Source projects - All

  *  donations are <i>greatly</i> appreciated.

  *

- *  <b>Donate to this project at http://www.fourwalledcubicle.com </b> via PayPal - Thanks in Advance!

+ *  <b>Donate to this project at <a>http://www.fourwalledcubicle.com</a></b> via PayPal - Thanks in Advance!

  */

  
\ No newline at end of file
diff --git a/LUFA/ManPages/LibraryApps.txt b/LUFA/ManPages/LibraryApps.txt
index 257682b46..0b49a32e1 100644
--- a/LUFA/ManPages/LibraryApps.txt
+++ b/LUFA/ManPages/LibraryApps.txt
@@ -18,7 +18,7 @@
  *  Also included with the library are three fully functional bootloaders, located in the /Bootloaders/ subdirectory.

  *  The DFU class bootloader is compatible with Atmel's FLIP software or the open source dfu-programmer project, the

  *  CDC class (AVR109 protocol) is compatible with such open source software as AVRDUDE and AVR-OSP, and the TeensyLoader

- *  HID class bootloader is compatible with the software from PJRC (http://www.pjrc.com/teensy/index.html).

+ *  HID class bootloader is compatible with the software from PJRC (<a>http://www.pjrc.com/teensy/index.html</a>).

  *

  *  User-submitted projects are located in the /Projects/ subdirectory. If you wish to have your LUFA project included,

  *  please email it to the Library author.

diff --git a/Projects/Magstripe/Magstripe.txt b/Projects/Magstripe/Magstripe.txt
index b725b709d..5688a7db3 100644
--- a/Projects/Magstripe/Magstripe.txt
+++ b/Projects/Magstripe/Magstripe.txt
@@ -44,9 +44,9 @@
  *

  *  Firmware for a USB AVR powered USB TTL magnetic stripe reader (using a card

  *  reader such as the Omron V3B-4K) by Denver Gingerich. This project is designed

- *  to be used with the open source Stripe Snoop project at http://stripesnoop.sourceforge.net/.

+ *  to be used with the open source Stripe Snoop project at <a>http://stripesnoop.sourceforge.net/</a>.

  * 

- *  See http://ossguy.com/ss_usb/ for the USB reader hardware project website,

+ *  See <a>http://ossguy.com/ss_usb/</a> for the USB reader hardware project website,

  *  including construction and support details.

  * 

  *  To use, connect your magnetic card reader device to the USB AVR as follows (pin and port mapping may be adjusted