[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=Zf+3qR8ZnhcY9KyXHRgcczF-4+Q@mail.gmail.com>
Date: Mon, 6 Jun 2011 16:48:17 -0700
From: David Hulton <0x31337@...il.com>
To: crypt-dev@...ts.openwall.com
Subject: Re: Yuri's Status Report - #3 of 15
Yuri & Alexander,
I apologize for this. We only developed the 32-bit Windows side of
this so that's all I'm really experienced with and just recently got
it working with 64-bit Windows but haven't fully tested it. Are you
able to work on this in Windows? The examples make a lot more sense in
Windows and honestly none of us here have had a chance to play with
the linux code...
-David
On Mon, Jun 6, 2011 at 4:05 PM, Yuri Gonzaga <yuriggc@...il.com> wrote:
>> You mean a kernel module (not "process").
>
> Yes. You are right!
>>
>> OK. Perhaps you made progress at that since then?
>
> Yes. But I still can't communicate my module.
> Using the linux drivers and examples it's is being complicated to put
> everything to work.
> As I said previously, it is necessary to understand how to interface to
> FIFOs and SPI channels in USB device on the board. So, I have done some
> attempts but it is not working properly yet.
> It looks like the windows approach is different. On linux, it is more
> complex...
>>
>> Isn't this hidden behind a software abstraction layer when you use
>> Pico's driver?
>
> The problem is not the software side but the hardware one, where I have to
> use all the signals correctly to read and write data through USB.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
