summaryrefslogtreecommitdiffstats
path: root/recipes-platform
diff options
context:
space:
mode:
authorDenys Dmytriyenko <denys@konsulko.com>2023-03-06 21:16:56 +0000
committerJan-Simon Moeller <jsmoeller@linuxfoundation.org>2023-03-19 22:11:42 +0000
commitebac35dea1de30d02c3ba2d48b91a557f9f0c989 (patch)
tree73b13159e288046fedb7321e66600c0ff21fe078 /recipes-platform
parent1797bb956087f9ee13f525b8bb26f099f115317b (diff)
conf/layer.conf: explicitly depend on networking-layer
As meta-agl-demo now explicitly depends on meta-flutter layer, it appears it uses networkmanager package in some of its plugins w/o marking the correct dependency in its own layer.conf. Also, cannelloni is no longer a standalone recipe, but a bbappend against the upstream recipe in meta-networking layer of meta-openembedded repository. To resolve both of the above issues and make yocto-check-layer happy, let's add an explicit dependency on networking-layer. Bug-AGL: SPEC-4685 Change-Id: Ib6781f63bd1f76ccbf2fcd649473bf59407bb7ef Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Diffstat (limited to 'recipes-platform')
0 files changed, 0 insertions, 0 deletions
*/ .highlight .si { color: #3333bb; background-color: #fff0f0 } /* Literal.String.Interpol */ .highlight .sx { color: #22bb22; background-color: #f0fff0 } /* Literal.String.Other */ .highlight .sr { color: #008800; background-color: #fff0ff } /* Literal.String.Regex */ .highlight .s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ .highlight .ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ .highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */
Building AVIRT
===================================

## Table of Contents

1. [Introduction](#intro)
2. [Out of Tree](#out-of-tree)
3. [In Tree](#in-tree)

<a name="intro"/>

## Introduction

The AVIRT module and submodules can be built using a variety of methods. There are Visual Code build tasks for in and out of tree builds, make file support for CLI building (both in and out of tree), and xds build support.

<a name="out-of-tree"/>

## Out Of Tree

### Building with CLI

To build both AVIRT and the additional Audio Paths out-of-tree, use the following command:

```sh
$ make
```

or

```sh
$ CONFIG_AVIRT=m CONFIG_AVIRT_BUILDLOCAL=y CONFIG_AVIRT_DUMMYAP=m make -C /lib/modules/$(uname -r)/build/ M=$(pwd)
```

The latter is executed internally with the make file.

### Building with XDS SDK

To build both AVIRT and the dummy Audio Path out-of-tree for [AGL](http://docs.automotivelinux.org/) (`aarch64` currently supported), use the [XDS](http://docs.automotivelinux.org/docs/devguides/en/dev/reference/xds/part-1/0_Abstract.html) build system together with the `make_agl.sh` script:

```sh
$ ./make_agl.sh ${XDS_SDK_ID}
```

<a name="in-tree"/>

## In tree

The kernal modules can be built in tree, dependent on the avirt repository being located in drivers/staging - If using your own fork of the linux kernel, you will need to update the staging Makefiles and Kconfigs accordingly.

To build in tree, use the [Fiberdyne Linux fork](https://github.com/fiberdyne/linux), which will automatically clone the AVIRT Driver and required AudioPath modules to the `drivers/staging` directory. You can then turn AVIRT Support on by setting to `<M>`. The drivers can be found here:

```
$ make menuconfig

# Navigate to: Device Drivers--->Staging Drivers--->AVIRT Support
```

Finally build the kernel with the configuration selected by making.

```
$ make
```