On Fri, Jan 16 2015, Jose Fonseca wrote:
> Oh, just saying that in fact I got it to build that module on Windows.
Thanks. That's good to know. I appreciate that testing.
I've just pushed this series along with your fixes.
And for the sake of everyone that contributed to the discussion on the
SHA
On 15/01/15 19:46, Carl Worth wrote:
On Thu, Jan 08 2015, Jose Fonseca wrote:
Note that Windows build is only supported with SCons. Never with
autobuild.
OK. That's good for me to learn. I've requested that the folks doing our
automated build testing here will also start testing scons builds,
On Thu, Jan 08 2015, Jose Fonseca wrote:
> Note that Windows build is only supported with SCons. Never with
> autobuild.
OK. That's good for me to learn. I've requested that the folks doing our
automated build testing here will also start testing scons builds, so
hopefully on our end we can avoid
On 07/01/15 19:11, Carl Worth wrote:
On Wed, Jan 07 2015, Jose Fonseca wrote:
I lost bit track of email over the Christmas period. Just noticed I had
flagged this one for replay. Sorry.
No worries. Thanks for following up now. :-)
Do you still need me to test anything on Windows? If so are
On Wed, Jan 07 2015, Jose Fonseca wrote:
> I lost bit track of email over the Christmas period. Just noticed I had
> flagged this one for replay. Sorry.
No worries. Thanks for following up now. :-)
> Do you still need me to test anything on Windows? If so are the patches
> in some pull-able gi
Hi,
Not sure there's anything to maintain, but sure, I'll maintain it.
Best,
OG.
On Sun, Dec 21, 2014 at 8:51 PM, Emil Velikov wrote:
> On 20 December 2014 at 14:21, Olivier Galibert wrote:
>> Here is an implementation I've written myself, so no license issues.
>>
> Thanks OG,
>
> Afaics
On Fri, Dec 19, 2014 at 11:44:42AM -0800, Kenneth Graunke wrote:
> On Sunday, December 14, 2014 03:06:41 PM Emil Velikov wrote:
> > On 11/12/14 21:51, Carl Worth wrote:
> > > From: Kristian Høgsberg
> > >
> > > The upcoming shader cache uses the SHA-1 algorithm for cryptographic
> > > naming. The
On 20 December 2014 at 14:21, Olivier Galibert wrote:
> Here is an implementation I've written myself, so no license issues.
>
Thanks OG,
Afaics the main issue is not the lack of implementation, but that
no-one wants to step up to "maintain" it.
Even adding code that is x2 the size is considered
Here is an implementation I've written myself, so no license issues.
OG.
On Fri, Dec 12, 2014 at 10:48 AM, Jose Fonseca wrote:
> On 11/12/14 22:02, Brian Paul wrote:
>>
>> On 12/11/2014 02:51 PM, Carl Worth wrote:
>>>
>>> From: Kristian Høgsberg
>>>
>>> The upcoming shader cache uses the SHA
On Fri, Dec 12 2014, Jose Fonseca wrote:
> Yes, ideally we'd have something small that we could bundle into mesa
> source tree, for sake of non Linux OSes.
Ken has pointed to an implementation that might be suitable for this.
I haven't reviewed that code myself, nor am I signing up to maintain a
On Sunday, December 14, 2014 03:06:41 PM Emil Velikov wrote:
> On 11/12/14 21:51, Carl Worth wrote:
> > From: Kristian Høgsberg
> >
> > The upcoming shader cache uses the SHA-1 algorithm for cryptographic
> > naming. These new mesa_sha1 functions are implemented with the nettle
> > library.
> > -
On 15/12/14 17:19, Matt Turner wrote:
> On Mon, Dec 15, 2014 at 3:15 AM, Emil Velikov
> wrote:
>> On 14/12/14 17:19, Matt Turner wrote:
>>> On Sun, Dec 14, 2014 at 7:06 AM, Emil Velikov
>>> wrote:
On 11/12/14 21:51, Carl Worth wrote:
> From: Kristian Høgsberg
>
> The upcoming
On 15/12/14 14:16, Francisco Jerez wrote:
> Emil Velikov writes:
>
>> On 11/12/14 21:51, Carl Worth wrote:
>>> From: Kristian Høgsberg
>>>
>>> The upcoming shader cache uses the SHA-1 algorithm for cryptographic
>>> naming. These new mesa_sha1 functions are implemented with the nettle
>>> librar
On Mon, Dec 15, 2014 at 3:15 AM, Emil Velikov wrote:
> On 14/12/14 17:19, Matt Turner wrote:
>> On Sun, Dec 14, 2014 at 7:06 AM, Emil Velikov
>> wrote:
>>> On 11/12/14 21:51, Carl Worth wrote:
From: Kristian Høgsberg
The upcoming shader cache uses the SHA-1 algorithm for cryptogr
If we're looking for something to drop in to Mesa to avoid a dependency
maybe we could look at simpler hashing algorithms too. For the shader
cache presumably we don't care about the hash being cryptographically
secure, just that it is unlikely to *accidentally* make a hash
collision. I think it wo
Emil Velikov writes:
> On 11/12/14 21:51, Carl Worth wrote:
>> From: Kristian Høgsberg
>>
>> The upcoming shader cache uses the SHA-1 algorithm for cryptographic
>> naming. These new mesa_sha1 functions are implemented with the nettle
>> library.
>> ---
>>
>> This patch is another in support o
On 14/12/14 17:19, Matt Turner wrote:
> On Sun, Dec 14, 2014 at 7:06 AM, Emil Velikov
> wrote:
>> On 11/12/14 21:51, Carl Worth wrote:
>>> From: Kristian Høgsberg
>>>
>>> The upcoming shader cache uses the SHA-1 algorithm for cryptographic
>>> naming. These new mesa_sha1 functions are implemente
On Sun, Dec 14, 2014 at 7:06 AM, Emil Velikov wrote:
> On 11/12/14 21:51, Carl Worth wrote:
>> From: Kristian Høgsberg
>>
>> The upcoming shader cache uses the SHA-1 algorithm for cryptographic
>> naming. These new mesa_sha1 functions are implemented with the nettle
>> library.
>> ---
>>
>> This
On 11/12/14 21:51, Carl Worth wrote:
> From: Kristian Høgsberg
>
> The upcoming shader cache uses the SHA-1 algorithm for cryptographic
> naming. These new mesa_sha1 functions are implemented with the nettle
> library.
> ---
>
> This patch is another in support of my upcoming shader-cache work.
Hi,
SHA1 is easy to implement. If you want an always-working backup, I
have a couple of C versions I wrote myself. Libraries are only
interesting if they offer significant speedups through cpu-dependance.
Especially since the shader cache is not in the happy fun land of
hardware-based attacks
On 11/12/14 22:02, Brian Paul wrote:
On 12/11/2014 02:51 PM, Carl Worth wrote:
From: Kristian Høgsberg
The upcoming shader cache uses the SHA-1 algorithm for cryptographic
naming. These new mesa_sha1 functions are implemented with the nettle
library.
---
This patch is another in support of my
On Thu, Dec 11 2014, Brian Paul wrote:
> We'll need a solution for Windows too. I don't have time right now to
> do any research into that.
The code from xserver seems to cover that. I'll follow up with a
(largely untested) patch that I ported over from xserver.
If people can give some high-lev
On 12/11/2014 02:51 PM, Carl Worth wrote:
From: Kristian Høgsberg
The upcoming shader cache uses the SHA-1 algorithm for cryptographic
naming. These new mesa_sha1 functions are implemented with the nettle
library.
---
This patch is another in support of my upcoming shader-cache work. Thanks to
From: Kristian Høgsberg
The upcoming shader cache uses the SHA-1 algorithm for cryptographic
naming. These new mesa_sha1 functions are implemented with the nettle
library.
---
This patch is another in support of my upcoming shader-cache work. Thanks to
Kritian for coding this piece.
As currentl
24 matches
Mail list logo
