From: Josh Datko <jbdatko@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] pcengines apu2c4 hardware random number generation
Date: Mon, 09 May 2016 09:10:22 -0600 [thread overview]
Message-ID: <1462806622.5898.9.camel@gmail.com> (raw)
In-Reply-To: <CAA93jw4Jj6cUnhMAzCWnRBJXFZb6v-CfAWA=tQTYr74v+zmddA@mail.gmail.com>
On Fri, 2016-05-06 at 13:19 -0700, Dave Taht wrote:
> On Thu, May 5, 2016 at 9:10 AM, Josh Datko <jbdatko@gmail.com> wrote:
> >
> I forget how fast those chips were (?)
The get_random command, from the perspective of the Atmel chip, takes
on average, 11ms to return 32bytes of random numbers, with a max of
50ms (from the ATSHA204A datasheet).
Practically however, you have to account for the kernel processing,
100khz I2C send and return up the stack.
> Meh. If there is a decent gpio header on j.random x86 board, I'd just
> as soon use that.
Yeah, I hear you. What I do is I split my video cable and hijack the
i2c and power lines from that (typically used to read the EDID from the
monitor) so I can develop on my workstation.
You board didn't seem to have a video connection, otherwise I'd suggest
that. I made a VGA2I2C board that you can get on OSHPark if you want to
solder on some N-channel mosfets and some 0603 resistors.
Otherwise, the drivers all use either the kernel's i2c subsytem or in
userspace, the ioctl. So, afaik, there'd have to be an i2c-bitbang
hardware abstract layer used to use random GPIO pins.
prev parent reply other threads:[~2016-05-09 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 23:28 Dave Taht
2016-05-05 0:16 ` Luis E. Garcia
2016-05-05 0:54 ` Dave Taht
2016-05-05 16:10 ` Josh Datko
2016-05-06 20:19 ` Dave Taht
2016-05-09 15:10 ` Josh Datko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1462806622.5898.9.camel@gmail.com \
--to=jbdatko@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox