netdev - Re: [PATCH net-next 1/2] ptp: ocp: add nvmem interface for accessing eeprom

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: <3D45B7EC-D480-4A0F-8ED2-2CC5677B8B13@gmail.com>
Date:   Thu, 03 Mar 2022 21:39:48 -0800
From:   "Jonathan Lemon" <jonathan.lemon@...il.com>
To:     "Jakub Kicinski" <kuba@...nel.org>
Cc:     netdev@...r.kernel.org, richardcochran@...il.com,
        davem@...emloft.net, kernel-team@...com
Subject: Re: [PATCH net-next 1/2] ptp: ocp: add nvmem interface for accessing
 eeprom

On 3 Mar 2022, at 21:01, Jakub Kicinski wrote:

> On Thu,  3 Mar 2022 15:38:00 -0800 Jonathan Lemon wrote:
>> manufacturer
>
> The generic string is for manufacture, i.e. fab; that's different
> from manufacture*r* i.e. vendor. It's when you multi-source a single
> board design at multiple factories.

The documentation seems unclear:

board.manufacture
-----------------
An identifier of the company or the facility which produced the part.


There isn’t a board.vendor (or manufacturer) in devlink.h.

The board design is open source, there’s several variants of
the design being produced, so I’m looking for a simple way to
identify the design (other than the opaque board id)
—
Jonathan