From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Romanski Date: Thu, 8 Apr 2021 12:56:33 -0400 Subject: [EXTERNAL] Re: [PATCH v2 6/6] test: dm: Add test for ECDSA UCLASS support In-Reply-To: <4662a6bc-c47e-9ee8-1cc9-1b7e2ec653a9@gmail.com> References: <20210316002432.2581891-1-mr.nuke.me@gmail.com> <20210316002432.2581891-7-mr.nuke.me@gmail.com> <5a0ca21a-1a51-f47e-3159-8d4517f483c9@gmail.com> <398c678d-e577-5d82-5998-b4748fda4af1@linux.microsoft.com> <4662a6bc-c47e-9ee8-1cc9-1b7e2ec653a9@gmail.com> Message-ID: <6ee9fe12-dbaa-ef8c-e350-54cd99fea14d@linux.microsoft.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Ok, will do. I'm writing the verification code, I noticed you're passing the public key into the fdt using fdt_add_bignum, which converts the x and y values into big endian integer arrays. Do you have a method to read these values from the fdt and convert them back into bignums, or is that TODO? I can get that done if it's not yet implemented. All the best, Tim On 2021-04-07 4:03 p.m., Alex G. wrote: > On 4/7/21 12:29 PM, Tim Romanski wrote: > >> Question for Alex, I see your repo has a few branches related to >> ECDSA (patch-ecdsa-v[1-5], patch-mkimage-keyfile-v{1,2}). You sent me >> a link to 'patch-ecdsa-v1' in a previous email, is that the one >> that's being upstreamed? Should I be working off a different branch >> or is that one ok? > > I'm up to v6 on the patch submission. The differences are not that > big, but I recommend sticking to the latest. > > Alex