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] [thread-next>] [day] [month] [year] [list]
Message-ID: <86de8ba0157c451fcce4ca92b6cad835e3f1e4d9.camel@collabora.com>
Date:   Thu, 21 Jul 2022 09:03:56 +0100
From:   Martyn Welch <martyn.welch@...labora.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc:     kernel@...labora.com, Rob Herring <robh@...nel.org>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: add MSC
 Technologies

On Wed, 2022-07-20 at 19:07 +0200, Krzysztof Kozlowski wrote:
> On 20/07/2022 17:00, Martyn Welch wrote:
> > Add "msc" vendor prefix for MSC Technologies GmbH
> > (https://www.msc-technologies.eu).
> 
> Does not really work - leads to Avnet, so there is no MSC anymore?
> 

It still seems to be used as branding by Avnet.

> > 
> > Signed-off-by: Martyn Welch <martyn.welch@...labora.com>
> > ---
> > 
> > Changes in v2:
> >   - New addition
> > 
> >  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > index 0496773a3c4d..1658357bc1c4 100644
> > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > @@ -816,6 +816,8 @@ patternProperties:
> >    "^mrvl,.*":
> >      description: Marvell Technology Group Ltd.
> >      deprecated: true
> > +  "^msc,.*":
> > +    description: MSC Technologies GmbH.
> 
> This should be rather msct or msctech, but anyway in fact you maybe
> should use avnet?
> 

My rationale for using MSC Technologies is that is how the device is
described on the website as being a MSC device. I think the
amalgamation of the MSC website into Avnet's has happened in the last
year or so. I assume a new device released in the near future would be
branded more directly as an Avnet device, or maybe not, I see that the
i.MX 9 is being described as "MSC SM2S-IMX93".

I'll switch to msctech unless there are objections to that.

Martyn

> >    "^mscc,.*":
> >      description: Microsemi Corporation
> >    "^msi,.*":
> 
> 
> Best regards,
> Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ