lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 17 Feb 2022 15:15:54 -0600
From:   Rob Herring <robh+dt@...nel.org>
To:     Rafał Miłecki <zajec5@...il.com>
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Tom Rini <trini@...sulko.com>,
        Ricardo Salveti <ricardo@...ndries.io>,
        Michal Simek <michal.simek@...inx.com>,
        Jorge Ramirez-Ortiz <jorge@...ndries.io>,
        U-Boot Mailing List <u-boot@...ts.denx.de>,
        Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH RFC *RFC*] dt-bindings: add U-Boot chosen for environment
 data phandle

On Thu, Feb 17, 2022 at 6:09 AM Rafał Miłecki <zajec5@...il.com> wrote:
>
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> This is RFC and request for a help & discussion.
>
> While reviewing patch for U-Boot env binding it has been mentioned that:
>
> 1. /Processing/ whole DT in U-Boot may be too much work
>    Handling flash devices, partitions, their formats & NVMEM may require
>    too many U-Boot drivers involved.
>
> 2. It'd be nice to have env data storage devices pointed in chosen
>
> I wrote this hacky PATCH to give a rough idea how it could look like.
>
> Please review this and let me know:
> 1. If solution with chosen + phandles is acceptable
> 2. How to properly name .yaml file
> 3. Where it put it
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
> ---
>  .../devicetree/bindings/u-boot,chosen.yaml    | 39 +++++++++++++++++++
>  1 file changed, 39 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/u-boot,chosen.yaml
>
> diff --git a/Documentation/devicetree/bindings/u-boot,chosen.yaml b/Documentation/devicetree/bindings/u-boot,chosen.yaml
> new file mode 100644
> index 000000000000..8369da91193d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/u-boot,chosen.yaml
> @@ -0,0 +1,39 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/u-boot,chosen.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: U-Boot setup
> +
> +maintainers:
> +  - Rafał Miłecki <rafal@...ecki.pl>
> +
> +properties:
> +  u-boot,env:
> +    $ref: /schemas/types.yaml#/definitions/phandle-array
> +    description: |
> +      A list of storage volumes containing U-Boot environment data.
> +
> +      Env data can be stored on various kinds of storage devices, e.g.:
> +      1. Raw flash partition
> +      2. UBI volume
> +
> +additionalProperties: true
> +
> +examples:
> +  - |
> +    chosen {
> +        u-boot,env = <&env>;

You should look at the u-boot config support:

https://github.com/devicetree-org/dt-schema/commit/0986f729eff0f40a66e85ab9dfb37681bf025ac4

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ