On 10/25/07, Kristian Kielhofner <[EMAIL PROTECTED]> wrote: > On 10/24/07, Brandon Black <[EMAIL PROTECTED]> wrote: > > > > AES: Driver loads (CONFIG_CRYPTO_DEV_GEODE), haven't tried to actually > > use it yet via OFC+OpenSSL... > > Can you elaborate on this? What's OFC+OpenSSL? >
I typo'd, it's OCF :) Basically, it's a patch for the kernel to give a different API layer (the OpenBSD Cryptography Framework) to the linux kernel's cryptography layer, which is where the hardware AES support is at. With this API in place, you can compile OpenSSL to use the OCF facilities, and therefore anything that uses OpenSSL for crypto can in theory take advantage of the Geode's AES-128 hardware. This is the most useful link I've found, I plan on following up on what he did here: http://www.docunext.com/resources/mediawiki/index.php/My_Notes_on_Patching_2.6.22_with_OCF > > RTC: I'm not sure exactly which RTC hardware drivers I'm supposed to > > enable, and the kernel isn't being very informative about it either. > > Sometimes I get no explicit errors, sometimes I get a failure to set > > the system from the RTC at startup, as in: > > > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > > > > Anyone know for sure which RTC hardware driver should be working and > > what the deal is? > > The standard RTC driver is fine. This error comes from trying to > set the system clock from the hardware clock (RTC) and not having the > proper device node (rtc0). Either disable this in your kernel config > and use hwclock later in the init process or create a /dev/rtc0 device > node the kernel can read at that point in startup. > Duh, thanks :) I didn't even think it would be a /dev file, I figured that early in the boot process it would be looking these things up internally. I have a wiki account now, I'll try to organize this stuff and get it up there soon. -- Brandon _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
