Re: [9fans] Raspberry Pi 2 Model B
Does anybody know where to look for documentation on the changes, or general documentation for the bcm2836? On Mon, Feb 2, 2015 at 1:24 PM, Bakul Shah wrote: > On Mon, 02 Feb 2015 20:54:02 GMT Skip Tavakkolian < > skip.tavakkol...@gmail.com> wrote: > > > > hardkernel's odroid-c1 is similar and slightly better performance for the > > same price; any sense which port might be easier? > > Odroid-c1 is Cortex-A5 while Pi2 is Cortex-A7 so Pi2 is more > performant (but has worse ethernet and horrible usb). Port to > pi2 should be easier as the periphs are the same as in Pi1; > only their IO maps have changed a bit. > > > > http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433 > >
Re: [9fans] Raspberry Pi 2 Model B
FANTASTIC! Thank you so much! That's so cool! On Fri, Feb 6, 2015 at 10:13 AM, Richard Miller <9f...@hamnavoe.com> wrote: > To return to the original subject ... > > /n/sources/contrib/miller/9pi2 is a Plan 9 kernel which runs on the > Raspberry Pi 2 (one core only, so far). I'll put updated source > in contrib/miller/9/bcm later today. mk CONF'='pi2 for the new > model, CONF'='pi for the original model. > > Plan 9 from Bell Labs > firmware: rev 1422642103 > cpu0: 900MHz ARM Cortex-A7 r0p5 > fp: 32 registers, simd > fp: arm arch VFPv3+ with common VFP subarch v2; rev 5 > eMMC external clock 250 Mhz > #u/usb/ep1.0: dwcotg: port 0X0 irq 9 > 992M memory: 200M kernel data, 792M user, 3762M swap > usb/hub... usb/ether... > etherusb smsc: b827eb4f2fbd > usb/kb... usb/kb... root is from (local, tcp)[local]: tcp > > Even with one core activated, the rpi2 is noticeably quicker than > the rpi. Decoding a 1600x1200 jpeg with 'jpg -t' (from ramfs) > takes about 5.8s on rpi, 3.2s on rpi2. > > Note that the publicity says 900Mhz, but the firmware boots at > 600Mhz, and relies on dynamic clock and voltage management in > linux to adjust the speed. To get a fixed 900Mhz speed, I put > this in config.txt: > > kernel=9pi2 > gpu_mem=16 > disable_overscan=1 > arm_freq=900 > force_turbo=1 > > Disclaimer: if you put silly numbers in arm_freq, bad stuff > might happen. Supposedly the firmware detects this and sets > an irreversible bit somewhere that voids your warranty. > > >
Re: [9fans] r-pi usbotg error
I'm not experiencing this issue (I've got a cheapo, 5+ year old USB keyboard, of make and model that I don't recall, attached to a B+ that's been running for a few days without an issue, plugged directly into the B+) Could it be associated with particular keyboard models? On Wed, Feb 18, 2015 at 8:48 AM, Steven Stallion wrote: > On Sun, Mar 9, 2014 at 11:15 AM, Ramakrishnan Muthukrishnan < > vu3...@gmail.com> wrote: > >> On Sun, Mar 9, 2014 at 9:11 PM, Rubén Berenguel >> wrote: >> > Sounds like the keyboard went idle (on its own!?) and the Rasp lost >> > connection to it. ep6.1 is the name of a USB device (something about >> logical >> > unit devices or something,) you can try unplugging something and you'll >> see >> > similar things pop up. kb is complaining the keyboard went away, and >> since >> > there is no keyboard, died. You could try ungplugging it and plugging >> it in. >> >> Yes, indeed, it came back to life after unplugging and re-plugging. >> Thanks. >> > > Last night I finally got around to getting a B+ I've had sitting in the > closet and converted it to a terminal. I'm seeing this same problem. I've > tried unplugging multiple keyboards and have also tried using a powered > hub. I'm at a loss. Has anyone else figured out how to deal with this issue? > > Steve >
Re: [9fans] How do I get a CSR CA's like?
If it's just as simple, this might be the right place/time to use sha256 for this sort of thing. On Tue, May 26, 2015 at 12:35 PM, Brantley Coile wrote: > I just changed “md5(…)” to “shall(…)” and added an object id to the > table. Once I figured out I didn’t have to us RSA to *sign* the CSR, but > had to have something other than md5, it was easy. > > > On May 26, 2015, at 2:00 PM, lu...@proxima.alt.za wrote: > > > >> I now have reason to believe that they just removed MD5 from known > >> signing algorithms, and that a SHA1 will work. Anyone know anything > >> about this? > > > > There's an exploit for the MD5 version. It looks pretty serious and > > deserves to be fixed by disabling the MD5 signing algorithm. > > > > www.phreedom.org/research/rogue-ca/ > > > > What exactly did you change in /sys/src/libsec/port/x509.c? I had a > > quick look this morning, but I didn't have the opportunity to dig deep > > enough. > > > > Lucio. > > > > > > >
