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]
Message-ID: <CAOCk7NrK1XKC=TW8H1QWyiAP86dueZB4gK5S-eg4pifr6vfxXQ@mail.gmail.com>
Date:   Thu, 26 Sep 2019 12:18:10 -0600
From:   Jeffrey Hugo <jeffrey.l.hugo@...il.com>
To:     Stephen Boyd <swboyd@...omium.org>
Cc:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
        Andy Gross <andy.gross@...aro.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        MSM <linux-arm-msm@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] soc: qcom: socinfo: add missing soc_id sysfs entry

On Thu, Sep 26, 2019 at 11:57 AM Stephen Boyd <swboyd@...omium.org> wrote:
>
> Quoting Jeffrey Hugo (2019-09-24 20:54:41)
> > On Mon, Sep 16, 2019 at 3:44 PM Stephen Boyd <swboyd@...omium.org> wrote:
> > >
> > > Quoting Srinivas Kandagatla (2019-09-12 02:10:19)
> > > > looks like SoC ID is not exported to sysfs for some reason.
> > > > This patch adds it!
> > > >
> > > > This is mostly used by userspace libraries like SNPE.
> > >
> > > What is SNPE?
> >
> > Snapdragon Neural Processing Engine.  Pronounced "snap-e".  Its
> > basically the framework someone goes through to run a neural network
> > on a Qualcomm mobile SoC.  SNPE can utilize various hardware resources
> > such as the applications CPU, GPU, and dedicated compute resources
> > such as a NSP, if available.  Its been around for over a year, and
> > much more information can be found by just doing a simple search since
> > SNPE is pretty much a unique search term currently.
>
> I wouldn't mind if it was still spelled out instead of just as an
> acronym. Who knows, a few years from now it may not be a unique acronym
> and then taking the extra few seconds to write it out once would have
> saved future effort.
>

Fair point.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ