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: <20190821113850.GP52127@atomide.com>
Date:   Wed, 21 Aug 2019 04:38:50 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Adam Ford <aford173@...il.com>
Cc:     "H. Nikolaus Schaller" <hns@...delico.com>,
        Merlijn Wajer <merlijn@...zup.org>,
        Paweł Chmiel <pawel.mikolaj.chmiel@...il.com>,
        Philipp Rossak <embed3d@...il.com>,
        moaz korena <moaz@...ena.xyz>,
        Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
        Filip Matijević <filip.matijevic.pz@...il.com>,
        Tomi Valkeinen <tomi.valkeinen@...com>,
        linux-omap <linux-omap@...r.kernel.org>,
        kernel@...a-handheld.com,
        Discussions about the Letux Kernel 
        <letux-kernel@...nphoenux.org>, maemo-leste@...ts.dyne.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Lay common foundation to make PVR/SGX work without hacks on
 OMAP34xx, OMAP36xx, AM335x and potentially OMAP4, OMAP5

* Adam Ford <aford173@...il.com> [190819 19:26]:
> On Sat, Aug 17, 2019 at 2:03 AM Tony Lindgren <tony@...mide.com> wrote:
> >
> > * Adam Ford <aford173@...il.com> [190816 23:02]:
> > > On Wed, Aug 14, 2019 at 8:16 AM Tony Lindgren <tony@...mide.com> wrote:
> > > > Well I just posted some sgx interconnect target module patches. We might
> > > > still have them in v5.4 assuming people manage to review and test them.
> > >
> > > Nikolaus,
> > >
> > > I tested Tony's change and I can confirm that I can read the value
> > > when enabled.  Should I apply his patches to your branch before I
> > > test, or is it go too to go as-is? I've got an AM3517, OMAP35 and a
> > > DM3730.  I am not sure if the AM3517 is even on the radar, but it has
> > > an sgx530 as well.
> >
> > My estimate is am3517 is wired the same way as omap34xx with a 60%
> > chance, then 30% chance it's wired the same way as omap36xx, and then
> > 10% chance for similar wiring to am335x.. So hopefully that leaves 0%
> > chance for yet something different for it's wiring :)
> 
> Based on [1], I went under the assumption it was wired like the
> omap34xx.  I applied your omap34 patches to the am3517.dtsi, and I was
> able to get the same response as I did for the omap3530.  Do you want
> me to post the patches to the mailing list, or do you want to do it?

OK great, yeah please post patches :)

Thanks,

TOny

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ