I have fixed all the broken links in the documentation except links for
Yocto project and security section.
Bug-AGL: [SPEC-4470]
Signed-off-by: Vinod Ahuja <vahuja@unomaha.edu>
Change-Id: I1c05bf2c3a9365bba0b67077cf51b294352e7943
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/28384
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
### 2. BeagleBone Enhanced (BBE)
### 2. BeagleBone Enhanced (BBE)
- 1. Download the [compressed prebuilt image](https://download.automotivelinux.org/AGL/snapshots/master/latest/bbe/deploy/images/bbe/agl-demo-platform-crosssdk-bbe.wic.xz).
+ 1. Download the [compressed prebuilt image](https://download.automotivelinux.org/AGL/snapshots/master/latest/bbe/deploy/images/bbe/agl-telematics-demo-platform-bbe.wic.xz).
2. Extract the image into the SD card of BeagleBone Enhanced :
```sh
$ lsblk
$ sudo umount <sdcard_device_name>
2. Extract the image into the SD card of BeagleBone Enhanced :
```sh
$ lsblk
$ sudo umount <sdcard_device_name>
- $ xzcat agl-demo-platform-crosssdk-bbe.wic.xz | sudo dd of=<sdcard_device_name> bs=4M
+ $ xzcat agl-telematics-demo-platform-bbe.wic.xz | sudo dd of=<sdcard_device_name> bs=4M
#### **Using `kuksa_viss_client`**
#### **Using `kuksa_viss_client`**
-Know more about kuksa_viss_client, [Follow this](https://github.com/eclipse/kuksa.val/tree/master/kuksa_viss_client)
+Know more about kuksa_viss_client, [Follow this](https://github.com/eclipse/kuksa.val/tree/master/)
- Run the kuksa_viss_client
- Authorize using token
- Run the kuksa_viss_client
- Authorize using token
to avoid potential name collisions and ease D-Bus integration.
The application ID is set in the desktop entry file itself for
to avoid potential name collisions and ease D-Bus integration.
The application ID is set in the desktop entry file itself for
-[graphical applications](../3_Creating_a_New_Application/#graphical-applications):
+[graphical applications](/04_Developer_Guides/03_Creating_a_New_Application/#graphical-applications):
it is the value of the `StartupWMClass` field, which must be identical to the `app-id`
advertised through the Wayland XDG toplevel protocol. In case this field is missing
(as is usually the case for non-graphical application), the application ID will be the
it is the value of the `StartupWMClass` field, which must be identical to the `app-id`
advertised through the Wayland XDG toplevel protocol. In case this field is missing
(as is usually the case for non-graphical application), the application ID will be the
**NOTE:** The `meta-agl` layer does not include a reference UI.
The reference UI is included as part of the
**NOTE:** The `meta-agl` layer does not include a reference UI.
The reference UI is included as part of the
- [`meta-agl-demo`](3_meta-agl-demo.md) layer.
+ [`meta-agl-demo`](03_meta_agl_demo.md) layer.
Furthermore, `meta-agl` does not include additional components, such
as security, which are part of the
`meta-agl-extra` layer.
Furthermore, `meta-agl` does not include additional components, such
as security, which are part of the
`meta-agl-extra` layer.
* packagegroup-agl-test.bb
Additional tools used in QA tests (for agl-image*-qa).
* packagegroup-agl-test.bb
Additional tools used in QA tests (for agl-image*-qa).
### Hardware Dependencies
Aside from the previously listed base dependencies, if you are using a
### Hardware Dependencies
Aside from the previously listed base dependencies, if you are using a
-[supported Renesas board](../../0_Getting_Started/2_Building_AGL_Image/5_3_RCar_Gen_3.md)
-supported Renesas board, these dependencies exist:
+[supported Renesas board](/01_Getting_Started/02_Building_AGL_Image/09_Building_for_Supported_Renesas_Boards.md), these dependencies exist:
- AGL's `meta-renesas` Layer:
- AGL's `meta-renesas` Layer:
-The `meta-agl-demo` layer has the following AGL [feature](../../0_Getting_Started/2_Building_AGL_Image/3_Initializing_Your_Build_Environment.md#agl-features)
+The `meta-agl-demo` layer has the following AGL [feature](/01_Getting_Started/02_Building_AGL_Image/04_Initializing_Your_Build_Environment/#agl-features)
dependencies:
- Yocto Project `meta-security` Layer:
dependencies:
- Yocto Project `meta-security` Layer:
Because the `packagegroup-agl-demo-qt-examples` is not mandatory for the AGL
Application Framework and the AGL DEMO, the packagegroup is added to the layer's
Because the `packagegroup-agl-demo-qt-examples` is not mandatory for the AGL
Application Framework and the AGL DEMO, the packagegroup is added to the layer's
- `local.conf` file only when needed.
\ No newline at end of file
+ `local.conf` file only when needed.
-Similarly to [services](../2_Creating_a_New_Service/#d-bus-activation), applications can
+Similarly to [services](../02_Creating_a_New_Service/#d-bus-activation), applications can
also be activated through D-Bus.
Such applications must name their `.desktop` file after the D-Bus name they register. In addition,
also be activated through D-Bus.
Such applications must name their `.desktop` file after the D-Bus name they register. In addition,
handling input events is an important feature to have, giving the user to
possibility to manipulate the application/environment as he or she seems fit.
The compositor loads a plug-in that streams out the buffers to an output
handling input events is an important feature to have, giving the user to
possibility to manipulate the application/environment as he or she seems fit.
The compositor loads a plug-in that streams out the buffers to an output
-remotely, with [another plug-in](2_waltham-receiver_waltham-transmitter.md)
+remotely, with [another plug-in](03_waltham_receiver_transmitter.md)
handling the input events. The events, which are sent back from the display to
the compositor, are generated with the help of wayland-eque protocol that works
over the network, called [Waltham](https://github.com/waltham/waltham).
handling the input events. The events, which are sent back from the display to
the compositor, are generated with the help of wayland-eque protocol that works
over the network, called [Waltham](https://github.com/waltham/waltham).
In the works, there's a new policy model, called [Role Based
Arbitration](https://gerrit.automotivelinux.org/gerrit/admin/repos/staging/rba).
In the works, there's a new policy model, called [Role Based
Arbitration](https://gerrit.automotivelinux.org/gerrit/admin/repos/staging/rba).
-Internally, how it works, should be found at [RBA](3_rba.md).
+Internally, how it works, should be found at [RBA](04_Rule_Based_Arbitrator.md).
While the other two policies are embedded into the compositor, the RBA policy
model is an off the-shell policy. Obviously, vendors and users can hook up
their own policies, just like RBA did. These all work towards satisfying
While the other two policies are embedded into the compositor, the RBA policy
model is an off the-shell policy. Obviously, vendors and users can hook up
their own policies, just like RBA did. These all work towards satisfying
The [documentation gerrit
repository](https://gerrit.automotivelinux.org/gerrit/admin/repos/AGL/documentation)
contains AGL documentation website template and content, rendering is visible at
The [documentation gerrit
repository](https://gerrit.automotivelinux.org/gerrit/admin/repos/AGL/documentation)
contains AGL documentation website template and content, rendering is visible at
-[https://automotivegradelinux.readthedocs.io/en/latest/](https://automotivegradelinux.readthedocs.io/en/latest/).
+[https://docs.automotivelinux.org](https://docs.automotivelinux.org).
The documentation site is hosted on
[readthedocs](https://readthedocs.org/projects/automotivegradelinux/) and
corresponding builds are mentioned
The documentation site is hosted on
[readthedocs](https://readthedocs.org/projects/automotivegradelinux/) and
corresponding builds are mentioned