VIA PadLock support. [Reward 50BTC]

[sgtstein]

I have a small reward out for implementing VIA's PadLock technology with the software. If done in a good way that could be used in the SVN for other builders I have a reward for 50BTC. If done even locally for just a few builds or instructions on how to do so, reward is 25 to 50 BTC.

Really want to get this working and don't have the time to put into it right now.

[jgarzik]

For anyone tackling this, the Linux kernel's drivers/crypto/padlock-sha.c should be all you need...

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=drivers/crypto/padlock-sha.c;hb=fc1caf6eafb30ea185720e29f7f5eccca61ecd60

[sgtstein]

Correct. It is well implemented in the Linux Kernel.

I'll be using it on Gentoo x86 with support built in without a module.

[jgarzik]

Correct. It is well implemented in the Linux Kernel.

I'll be using it on Gentoo x86 with support built in without a module.

Anyone implementing it in bitcoin will be unlikely to use the kernel support for anything but as a source for code copying...  One would almost surely link it into the bitcoin binary.

[Olipro]

why bother? Via publish an SDK for it.

I should also point out that you will need the lib files for linking.

[jgarzik]

why bother? Via publish an SDK for it.

I should also point out that you will need the lib files for linking.

The sha256 setup is very likely bitcoin-specific, and you don't need lib files or SDK to simply issue an instruction:

Code:

        asm volatile (".byte 0xf3,0x0f,0xa6,0xd0" /* rep xsha256 */
                      : \
                      : "c"((unsigned long)state.count + count), \
                        "a"((unsigned long)state.count), \
                        "S"(in), "D"(result));

[Olipro]

The sha256 setup is very likely bitcoin-specific, and you don't need lib files or SDK to simply issue an instruction:

Sure, you can do it as asm instructions or you can use the SDK to make it more easy to read, it's going to result in the same code in either case.

the bitcoin usage of SHA256 does not prevent you from using Padlock C style functions because they are the same standard of init, update, final.

[sgtstein]

The problem that I have had when implementing this is that I do not know enough about SHA256 to implement it. I'm trying to figure it out and learn but haven't been making much success. It's a bit difficult trying to learn and rewrite from the Crypto++ functions and calls. That, and I haven't programmed in C++ or C for a couple years all adds up to me putting this offer out.