Fix a bunch of broken links

dlech · dlech · commit 42c1b86f0d43 · 2016-01-08T21:02:05.000-06:00
diff --git a/_data/ports.json b/_data/ports.json
@@ -184,21 +184,21 @@
                 "id": "EV3_OUTPUT_PORT_MODE_TACHO_MOTOR",
                 "name": "tacho-motor",
                 "name_footnote": "[^tacho-motor-mode]",
-                "notes": "\n[^tacho-motor-mode]: Configures the port to use the\n    [tacho-motor] driver module. The default driver is the\n    EV3 Large Motor (`lego-ev3-l-motor`). You can change\n    the driver using the `set_device` attribute.\n    ^\n    [tacho-motor]: /docs/drivers/tacho-motor\n    \n    "
+                "notes": "\n[^tacho-motor-mode]: Configures the port to use the\n    [tacho-motor] driver module. The default driver is the\n    EV3 Large Motor (`lego-ev3-l-motor`). You can change\n    the driver using the `set_device` attribute.\n    ^\n    [tacho-motor]: /docs/drivers/tacho-motor-class\n    \n    "
             },
             {
                 "description": "Load the [dc-motor] device.",
                 "id": "EV3_OUTPUT_PORT_MODE_DC_MOTOR",
                 "name": "dc-motor",
                 "name_footnote": "[^dc-motor-mode]",
-                "notes": "\n[^dc-motor-mode]: This can be use with MINDSTORMS RCX\n    motors, Power Functions motors and any other 'plain' DC\n    motor. By 'plain', we mean the motor is just a motor without\n    any feedback.\n    ^\n    [dc-motor]: /docs/drivers/dc-motor\n    \n    "
+                "notes": "\n[^dc-motor-mode]: This can be use with MINDSTORMS RCX\n    motors, Power Functions motors and any other 'plain' DC\n    motor. By 'plain', we mean the motor is just a motor without\n    any feedback.\n    ^\n    [dc-motor]: /docs/drivers/dc-motor-class\n    \n    "
             },
             {
                 "description": "Load the [led] device.",
                 "id": "EV3_OUTPUT_PORT_MODE_LED",
                 "name": "led",
                 "name_footnote": "[^led-mode]",
-                "notes": "\n[^led-mode]: This can be used with MINDSTORMS RCX LEDs,\n    Power Functions LEDs or any other LED connected to pins 1\n    and 2 of the output port.\n    ^\n    [led]: /docs/drivers/led\n    \n    "
+                "notes": "\n[^led-mode]: This can be used with MINDSTORMS RCX LEDs,\n    Power Functions LEDs or any other LED connected to pins 1\n    and 2 of the output port.\n    ^\n    [led]: /docs/drivers/rcx-led\n    \n    "
             },
             {
                 "description": "Provide access to low level drivers.",
diff --git a/docs/drivers/brickpi-i2c-sensor.markdown b/docs/drivers/brickpi-i2c-sensor.markdown
@@ -20,7 +20,7 @@ Devices bound to this driver can be found in the directory
 the [lego-sensor class] which is where the useful stuff is. Follow the link
 for more information.
 
-[brickpi]: /docs/drivers/brickpi
+[brickpi]: /docs/drivers/brickpi-ld
 [brickpi-in-port]: /docs/ports/brickpi-port
 [list of supported sensors]: /docs/sensors#supported-sensors
 [lego-sensor class]: ../lego-sensor-class
diff --git a/docs/kernel-hackers-notebook/ev3-i2c.md b/docs/kernel-hackers-notebook/ev3-i2c.md
@@ -2,26 +2,42 @@
 title: EV3 I2C
 ---
 
-The [AM1808 SoC](ev3-processor) has 2 hardware [Inter-Integrated Circuit](https://en.wikipedia.org/wiki/I2c) (I2C) controllers. Additionally, there are 4 software controllers implemented using [fast interrupts](../ev3-fiq) (FIQs).
+The [AM1808 SoC](../ev3-processor) has 2 hardware [Inter-Integrated Circuit][i2c]
+(I2C) controllers. Additionally, there are 4 software controllers implemented using
+[fast interrupts](../ev3-fiq) (FIQs).
 
 ## Usage
 
 __I2C0__: [Boot EEPROM](../ev3-eeprom) @400kHz
 
 __I2C1__: Not used/connected
 
-__[FIQ](ev3-fiq) I2C__: Input ports 1-4 @10kHz
+__[FIQ](../ev3-fiq) I2C__: Input ports 1-4 @10kHz
 
 ## Device Drivers
 
-The Linux kernel has a well established [framework for I2C drivers](https://www.kernel.org/doc/Documentation/i2c/).
+The Linux kernel has a well established [framework for I2C drivers].
 
-The SoC I2C uses the existing driver at [drivers/i2c/busses/i2c-davinci.c](https://github.com/ev3dev/ev3dev-kernel/blob/master/drivers/i2c/busses/i2c-davinci.c) as a backend.
+The SoC I2C uses the existing driver at [drivers/i2c/busses/i2c-davinci.c] as a backend.
 
-Since there are not enough I2C controllers on the SoC, LEGO chose to implement the I2C buses for the four input ports using GPIOs. A secondary reason for this is that the NXT Ultrasonic sensors does not work well with standard I2C masters. It requires an extra clock pulse between the stop and the next start. (TODO: add references here.) 
+Since there are not enough I2C controllers on the SoC, LEGO chose to implement
+the I2C buses for the four input ports using GPIOs. A secondary reason for this
+is that the NXT Ultrasonic sensors does not work well with standard I2C masters.
+It requires an extra clock pulse between the stop and the next start. (TODO: add
+references here.)
 
-This Linux kernel has an existing GPIO i2c driver, but in order to get the performance needed, we have to use [fast interrupts](EV3 FIQ) (FIQs). (Be sure to follow the link for some interesting reading.) So, the really low level stuff is done in [arch/arm/mach-davinci/legoev3-fiq.c](https://github.com/ev3dev/ev3dev-kernel/blob/master/arch/arm/mach-davinci/legoev3-fiq.c) and the rest is in [drivers/i2c/busses/i2c-legoev3.c](https://github.com/ev3dev/ev3dev-kernel/blob/master/drivers/i2c/busses/i2c-legoev3.c).
+This Linux kernel has an existing GPIO i2c driver, but in order to get the
+performance needed, we have to use [fast interrupts](../ev3-fiq) (FIQs). (Be sure
+to follow the link for some interesting reading.) So, the really low level stuff
+is done in [arch/arm/mach-davinci/legoev3-fiq.c] and the rest is in
+[drivers/i2c/busses/i2c-legoev3.c].
 
 ## I2C Addressing
 
-See [I2C Sensor Addressing]({{ github.site.url }}/docs/sensors/i2c-sensor-addressing/).
+See [I2C Sensor Addressing](/docs/sensors/i2c-sensor-addressing/).
+
+[i2c]: https://en.wikipedia.org/wiki/I2c
+[framework for I2C drivers]: https://www.kernel.org/doc/Documentation/i2c/
+[drivers/i2c/busses/i2c-davinci.c]: https://github.com/ev3dev/ev3-kernel/blob/ev3dev-jessie/drivers/i2c/busses/i2c-davinci.c
+[arch/arm/mach-davinci/legoev3-fiq.c]: https://github.com/ev3dev/ev3-kernel/blob/ev3dev-jessie/arch/arm/mach-davinci/legoev3-fiq.c
+[drivers/i2c/busses/i2c-legoev3.c]: https://github.com/ev3dev/lego-linux-drivers/blob/master/ev3/legoev3_i2c.c
diff --git a/docs/kernel-hackers-notebook/ev3-uart.md b/docs/kernel-hackers-notebook/ev3-uart.md
@@ -2,7 +2,8 @@
 title: EV3 UART
 ---
 
-The [AM1808 SoC](../ev3-processor) has 3 hardware [UART](https://en.wikipedia.org/wiki/Universal_asynchronous_receiver/transmitter) controllers. We are also using the [PRU](../ev3-pru) to provide 2 additional software UARTs.
+The [AM1808 SoC](../ev3-processor) has 3 hardware [UART] controllers. We are
+also using the [PRU](../ev3-pru) to provide 2 additional software UARTs.
 
 ## Usage
 
@@ -19,9 +20,22 @@ __PRU0/SUART1__ | Input port 3 UART sensors.
 
 See the [PRU](../ev3-pru) page for info on the PRU UART drivers.
 
-The SoC UARTs are standard UARTs and therefore use the [8250](https://github.com/ev3dev/ev3dev-kernel/tree/uart-sensors/drivers/tty/serial/8250) driver. Both types of UARTs (SoC and PRU) of course implement the [tty](https://github.com/ev3dev/ev3dev-kernel/tree/uart-sensors/drivers/tty) device class. The interesting part is the LEGOEV3 [line discipline](https://github.com/ev3dev/ev3dev-kernel/blob/uart-sensors/Documentation/serial/tty.txt) that runs on top of the tty driver.
+The SoC UARTs are standard UARTs and therefore use the
+[8250](https://github.com/ev3dev/ev3-kernel/tree/ev3dev-jessie/drivers/tty/serial/8250)
+driver. Both types of UARTs (SoC and PRU) of course implement the
+[tty](https://github.com/ev3dev/ev3-kernel/tree/ev3dev-jessie/drivers/tty)
+device class. The interesting part is the LEGOEV3 [line discipline] that runs
+on top of the tty driver.
 
 ### LEGOEV3 Line Discipline
-Source: [uart-sensors/drivers/legoev3/legoev3_uart.c](https://github.com/ev3dev/ev3dev-kernel/blob/uart-sensors/drivers/legoev3/legoev3_uart.c)
+Source: [ev3_uart_sensor_ld.c](https://github.com/ev3dev/lego-linux-drivers/blob/master/sensors/ev3_uart_sensor_ld.c)
 
-There are udev rules in place ([/lib/udev/rules.d/ev3dev-uart.rules](https://github.com/ev3dev/ev3dev-base/blob/master/debian/ev3dev-uart.udev) in conjunction with [/lib/ev3dev/uart.sh](https://github.com/ev3dev/ev3dev-base/blob/master/usr/lib/ev3dev/uart.sh)) that attach the line discipline to a tty (serial port) when a UART sensor is detected on a given input port. When the sensor is removed, the line discipline is detached (process killed). 
+There are udev rules in place ([ev3.rules] in conjunction with [ev3-uart@.service])
+that attach the line discipline to a tty (serial port) when a UART sensor is
+detected on a given input port. When the sensor is removed, the line discipline
+is detached (process killed).
+
+[UART]: https://en.wikipedia.org/wiki/Universal_asynchronous_receiver/transmitter
+[line discipline]: https://github.com/ev3dev/ev3dev-kernel/blob/uart-sensors/Documentation/serial/tty.txt
+[ev3.rules]: https://github.com/ev3dev/ev3-systemd/blob/ev3dev-jessie/debian/ev3.udev#L19
+[ev3-uart@.service]: https://github.com/ev3dev/ev3-systemd/blob/ev3dev-jessie/systemd/ev3-uart%40.service
diff --git a/docs/kernel-hackers-notebook/index.md b/docs/kernel-hackers-notebook/index.md
@@ -38,22 +38,17 @@ the ev3dev kernel. It is mostly information about the hardware and device driver
 
 ### Sensors (Input Devices)
 
-* [Sensor Driver Model](ev3-sensor-driver-model)
-* [List of Sensors](list-of-sensors)
+* [Sensor Driver Model](/docs/drivers/lego-sensor-class)
+* [List of Sensors](/docs/sensors/#supported-sensors)
 
 ### Motors (Output Devices)
 
-* [Motor Driver Model](ev3-motor-driver-model)
-* [List of Motors](list-of-motors)
+* [Motor Driver Model](/docs/drivers/tacho-motor-class)
+* [List of Motors](/docs/motors/#motors)
 
 
 ## Software
 
 ### Operating System
 
-* [Kernel v3.16](ev3dev-linux-kernel)
-* [Debian 8 Jessie](ev3dev-debian-distro)
-
-### Applications
-
-* [fbcat (screen capture)](fbcat)
+* [Kernel v3.16](../ev3dev-linux-kernel)
diff --git a/docs/sensors/using-i2c-sensors.md b/docs/sensors/using-i2c-sensors.md
@@ -247,8 +247,8 @@ With the mindsensors.com Realtime Clock Sensor on input port 2.
     00:                         46 72 65 65 20 72 61 6d            Free ram
     10: 20 73 70 61 63 65 21                                space!
 
-[lego-sensor]: ../lego-sensor-class
+[lego-sensor]: /docs/drivers/lego-sensor-class
 [I2C Sensor Addressing]: ../i2c-sensor-addressing
 [port splitter]: http://mindsensors.com/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=79
 [sensor MUX]: http://mindsensors.com/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=179
-[nxt-i2c-sensor]: ../nxt-i2c-sensor
+[nxt-i2c-sensor]: /docs/drivers/nxt-i2c-sensor
diff --git a/docs/tutorials/adding-new-project.md b/docs/tutorials/adding-new-project.md
@@ -31,7 +31,7 @@ To do this, open a browser and navigate to the [website repository]. Make
 sure that you are signed in to your GitHub account, and then click the "fork"
 button in the upper-right corner.
 
-<img src="https://github-images.s3.amazonaws.com/help/repository/fork_button.jpg" style="max-width: 300px;" />
+<img src="https://github-images.s3.amazonaws.com/help/repository/fork_button.jpg" style="max-width: 300px;" alt="github screenshot" />
 
 It should take a second, but when GitHub finishes processing your request you
 should be at a page very similar to where you started, except now you are
@@ -104,7 +104,7 @@ select "gh-pages."
 
 Now click the green "Compare, review and pull request" button.
 
-<img src="https://github-images.s3.amazonaws.com/help/pull_requests/pull-request-start-review-button.png" style="max-width: 300px;" />
+<img src="https://github-images.s3.amazonaws.com/help/pull_requests/pull-request-start-review-button.png" style="max-width: 300px;" alt="github screenshot" />
 
 Then click "Create pull request," and enter a title and brief description of
 your new page before clicking the button that says "Create pull request" again
