Hi Ruslan,
This is so awesome!
I was first afraid of breaking something because I needed a
non-trivial amount of force opening the T400 up.
But the casing seems to be very flexible and durable -- a
screw driver did the trick.
My new 'lobotomized' T400 works like a charm.
Thank you for this!!
Hello all,
I have a Rasclock sitting on my Raspberry Pi. According to spec it
uses the pins 3.3V, GND SDA and SCL.
The Rasclock itself consists basically of a PCF2127AT chip.
My question: What is the best way to access these I/O pins?
My goal would be to write some sort of driver for this devi
Hello,
I have upgraded my Raspberry Pi with a RasClock:
http://afterthoughtsoftware.com/products/rasclock
In order to use, I put the following line into my profile:
bind -a '#r' /dev
The realtime-clock seems to be successfully recognized
by the system as device /dev/rtc. However, Plan 9 does
Hi,
Am 2013-04-28 23:14, schrieb Richard Miller:
#include "../omap/random.c"
which should be
#include "../port/random.c"
Although it was easy to fix, I wonder where this inconsistency
in the source tree came from. Did I miss an update or something?
I think you did. /sys/src/9/bcm/random.c
Hi,
Am 2013-04-28 23:07, schrieb Bakul Shah:
On 28 Apr 2013 22:01:17 +0200 "Holger Sebert"
wrote:
I did a quick hack on kbd.c and could make the "<,>,|" key
work. Awesome! Thank you all for your help.
What was the fix?
The relevant section from kbd.c i
Hi,
I did a quick hack on kbd.c and could make the "<,>,|" key
work. Awesome! Thank you all for your help.
In the 'bcm' directory some modules refer to 'omap' although
they apparently mean 'port', like this:
#include "../omap/random.c"
which should be
#include "../port/random.c"
Although it
Hi,
I have tried to re-build the kernel on the Raspberry Pi
along the lines as documented here:
http://plan9.bell-labs.com/wiki/plan9/compiling_kernels/index.html
Concretely, I did the following:
% cd /sys/src/9/bcm
% mk 'CONF=pi'
The build starts, but soon exists with an error:
fpi.c:2 5c:
Hi,
Am 24.04.13 22:56, schrieb Bakul Shah:
On 24 Apr 2013 21:25:13 +0200 "Holger Sebert"
wrote:
I have tried it out: The driver says
"sc: e0 56" when pressing the "<"-key.
This means a two char sequence: e0, 0x56 is stuffed into the
kernel device kbin
Hi,
Am 21.04.13 01:18, schrieb Bakul Shah:
On 20 Apr 2013 22:08:00 +0200 "Holger Sebert"
wrote:
This phenomenon does not exist on a x86-based
installation of Plan 9, so it seems specific
to the Raspberry Pi.
Strange Is the x86 installation on real hardware or under
a VM? If
Am 20.04.13 21:14, schrieb Bakul Shah:
On 20 Apr 2013 18:31:02 +0200 "Holger Sebert"
wrote:
However, I have a little trouble using my
German USB keyboard with it.
See
http://plan9.bell-labs.com/wiki/plan9/setting_the_right_keyboard_map/
I have already done that and the Umlauts
It seems like the scan code
is not recognized by the USB driver.
Note: It may be that the key (as hardware) does
not exist on US keyboards:
http://commons.wikimedia.org/wiki/File:German-T2-Keyboard-Prototype-May-2012.jpg
(It is the key at the bottom-left, next to Shift)
Any ideas?
Best regards,
Holger Sebert
11 matches
Mail list logo
