linux-kernel - arc vendor prefix

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-next>] [day] [month] [year] [list]

Date:   Tue, 18 Sep 2018 21:05:20 -0400
From:   Brian Dodge <bdodge09@...il.com>
To:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: arc vendor prefix

Hi,

In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the 
vendor prefix "arctic" was added to vendor-prefixes.txt.

The original change I authored used "arc" not "arctic", and the device 
tree bindings were added assuming that prefix in commit 
ce9d22573d85341c987f997461ac712e4dbe47b1

Perhaps odeju changed the name to arctic in the patch after I created it 
and before it was approved.

This pairing isn't really compatible is it?  Either the prefix should be 
reverted to "arc" or the bindings (and driver source) changed to use 
"arctic", as in "arctic,arc2c0608" vs. "arc,arc2c0608"

The arcticsand company is now part of psemi (formerly peregrine 
semiconductor) and they would like to keep using the arc prefix for 
these chips and in the driver and I plan on changing the 
vendor-prefix.txt to reflect that.

I am in the process of updating the driver code to support different and 
new variants of the chip and would like to know what the preference is 
for this prefix going forward.

Thank you

Brian