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  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]
Date:   Mon, 20 Feb 2017 14:58:25 +0100
From:   Thomas Petazzoni <>
To:     Andreas Färber <>
        Jisheng Zhang <>,
        Andrew Lunn <>,
        Eric Miao <>,
        Jason Cooper <>,,,
        Haojian Zhuang <>,, Rob Herring <>,
        Gregory Clement <>,
        Mark Rutland <>,
        Robert Jarzmik <>,
        Daniel Mack <>,
        Sebastian Hesselbarth <>
Subject: Re: [PATCH 2/4] Documentation: devicetree: arm: Document Marvell


On Mon, 20 Feb 2017 14:16:13 +0100, Andreas Färber wrote:

> I'm confused now. According to Marvell IR [0] they are NASDAQ-listed as
> MRVL. My understanding is that in that case the official vendor prefix
> becomes mrvl. Why not here?

Not sure why, but as of today, we have a mix of "mrvl" and "marvell" in
the tree, and "marvell" is the one official listed in

> Any comments on the iap140 vs. pxa1908 naming? The Communication
> Processors section has disappeared from, so I couldn't
> verify whether IAP140 was renamed from PXA1908 or whether both coexist
> and we should add a second compatible string here?

I don't have an opinion on this because I'm not familiar with this
family of Marvell SoCs. However, the only thing I would recommend is
that you send a patch to update Documentation/arm/Marvell/README to
document this PXA1908/IAP140 thing. This is particularly important
since this document mentions PXA1908 already.


Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering

Powered by blists - more mailing lists