Re: [9fans] Building a Raspberry Pi image / Keyboard support
pi can deal with wireless network? As I have no network connection now. I applied a USB hub (2.0 3 ports) for use of USB stick. Yes, it works no problem with usb devices of keyboard+mouse+usb stick. Please remember I'm using MAX 1.8A power supply. Kenji
Re: [9fans] Building a Raspberry Pi image / Keyboard support
I'm using 20 Sharp LC-20E90 with HDMI cable, then I got 1184x624 display size (sigh). Any idea to exand this? I got it. I changes the line of disable_overscan=1 to uncommented of the file CONFIG.TXT in /n/9fat directory, and rebooted. Then, now I have 1280x720 display. Why you named /dev/sdM0/dos not /dev/sdM0/9fat? I prefer the latter, because it is accordant with other cpus. Kenji
Re: [9fans] Building a Raspberry Pi image / Keyboard support
disk/fdisp -p Oops, disk/fdisk is what I meant to type.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
Why you named /dev/sdM0/dos not /dev/sdM0/9fat? I prefer the latter, because it is accordant with other cpus. This is standard Plan 9 behaviour of disk/fdisp -p, on any cpu. The convention is that dos is the name for a primary dos partition, and 9fat is the name for a dos subpartition at the start of a plan9 partition. Perhaps you are thinking of one of the forks which does it differently? If you prefer different naming, you can change it yourself with a 'part' command to /dev/sdM0/ctl - /cfg/$sysname/termrc would be a sensible place to do this.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
Thanks Richard. The convention is that dos is the name for a primary dos partition, and 9fat is the name for a dos subpartition at the start of a plan9 partition. Then, I'll follow your decision. By the way, how I can arrage the correct time in this system? I don't mean the /adm/timezone/local, because in the usual PC, we can change it at BIOS screen. Kenji
Re: [9fans] Building a Raspberry Pi image / Keyboard support
I attached my Japanese keyboard program here, which deals with multibyte sequence of key codes. Base is same as Gorka's (probably) program. This is the same one which I sent to eric. If anyone want to modify this for your language, don't warry about lisense etc. i think i added this to usb/kb in 9atom. see the -j option. - erik
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On Sat Jul 5 19:46:36 EDT 2014, an...@kix.in wrote: Thanks for the suggestions. The keyboard + mouse work fine with Linux. In fact they work on Plan 9 together, but only for a few seconds before I get: kb: /dev/usb/ep6.1: read: i/o error kb: exiting usbotg: ep5.1 error intr 0082 usb/kb... kb: exiting i see these sometimes, too. a formerly working apple full sized wired keyboard has stopped working with these errors. i assume it's something tricky. however, 9atom has some keyboard/mouse fixes that might be worth checking up on. the original version asked for pretty big descriptors from the device, and many devices generate transaction errors, or otherwise do bad things™ when asked for a descriptor bigger than they envisioned. the solution is to ask for the minimum size descriptor plus enough space to get the descriptor length, then ask again with the device-provided length. - erik
Re: [9fans] Building a Raspberry Pi image / Keyboard support
i think i added this to usb/kb in 9atom. see the -j option. I expected to manage it to use without recompilation for Japanese user. Your change still need to recompile the kernel, because usbd is included in the boot components. If so, my original version is simpler, I think. sorry... Kenji
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On Mon Jul 7 19:12:32 EDT 2014, kokam...@hera.eonet.ne.jp wrote: i think i added this to usb/kb in 9atom. see the -j option. I expected to manage it to use without recompilation for Japanese user. Your change still need to recompile the kernel, because usbd is included in the boot components. If so, my original version is simpler, I think. sorry... this is incorrect. -j is a flag to usb/kb. this obviously does not require a recompile, just the addition of kbargs=-j to your plan9.ini. - erik
Re: [9fans] Building a Raspberry Pi image / Keyboard support
Kenji, I think others are using ethernet to wifi bridges - if I were in the same position, I would too. USB wifi support probably isn't what it could be, for obvious reasons. I was using a DX Chinese wifi bridge until I realised it was beyond hope, it would shut down within five seconds of being powered on, and cycle over and over. I even had a Linux Python script to configure the thing for my old wireless network before I moved... needless to say, it got thrown in a bin. Hopefully you can do better...! Good luck! On Sun, Jul 6, 2014 at 11:15 AM, kokam...@hera.eonet.ne.jp wrote: I use a standard dell keyboard and LCD display at 1920x1600. Wow, you have big screen! I only have a 20 small LCD TV, I don't watch TV much. its the perfect plan9 terminal IMHO. Indeed! pi can deal with wireless network? Kenji PS: I decided to perchase it.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
PS: I decided to perchase it.
Igot pi board from amazon.jp, and yes it's nice for Plan9 terminal.
I'm using max 1.8A power supply, and usb mose and keyboard.
No problem so far.
I can use Japanese keyboard here.
I'm using 20 Sharp LC-20E90 with HDMI cable, then
I got 1184x624 display size (sigh).
Any idea to exand this?
As I have this TV in a diffrent room from the network rooter,
so I have to use wireless LAN which I've not purchased bridge.
Therefore, this is standalone, isolated Plan9 terminal, Hmmm.
I attached my Japanese keyboard program here, which deals
with multibyte sequence of key codes. Base is same as Gorka's
(probably) program. This is the same one which I sent to eric.
If anyone want to modify this for your language, don't warry
about lisense etc.
Just run games/mahjongg, and got good feeling of the graphic
speed from this toy like board!
Kenji
/*
* USB Human Interaction Device: keyboard and mouse.
*
* If there's no usb keyboard, it tries to setup the mouse, if any.
* It should be started at boot time.
*
* Mouse events are converted to the format of mouse(3)'s mousein file.
* Keyboard keycodes are translated to scan codes and sent to kbin(3).
*
* If there is no keyboard, it tries to setup the mouse properly, else it falls
* back to boot protocol.
*/
#include u.h
#include libc.h
#include thread.h
#include usb.h
#include hid.h
enum
{
Stoprpt = -2,
Tick= -3,
Exiting = -4,
Msec= 1000*1000,/* msec per ns */
Dwcidle = 8,
};
typedef struct KDev KDev;
typedef struct Kbd Kbd;
typedef struct Mouse Mouse;
typedef struct Kin Kin;
struct Kbd
{
Channel*repeatc;
Channel*exitc;
longnproc;
};
struct Mouse
{
int accel; /* only for mouse */
};
struct KDev
{
Dev*dev;/* usb device*/
Dev*ep; /* endpoint to get events */
Kin*in; /* used to send events to kernel */
int idle; /* min time between reports (× 4ms) */
int bootp; /* has associated keyboard */
int debug;
Kbd;
Mouse;
HidRepTempl templ;
int (*ptrvals)(KDev *kd, Chain *ch, int *px, int *py, int *pb);
};
/*
* Kbdin and mousein files must be shared among all instances.
*/
struct Kin
{
int ref;
int fd;
char* name;
};
/*
* Map for the logitech bluetooth mouse with 8 buttons and wheels.
* { ptr -mouse}
* { 0x01, 0x01 }, // left
* { 0x04, 0x02 }, // middle
* { 0x02, 0x04 }, // right
* { 0x40, 0x08 }, // up
* { 0x80, 0x10 }, // down
* { 0x10, 0x08 }, // side up
* { 0x08, 0x10 }, // side down
* { 0x20, 0x02 }, // page
* besides wheel and regular up/down report the 4th byte as 1/-1
*/
/*
* key code to scan code; for the page table used by
* the logitech bluetooth keyboard. ===deleted by K.Okamoto===
*
static char sctab[256] =
{
[0x00] 0x0,0x0,0x0,0x0,0x1e, 0x30, 0x2e, 0x20,
[0x08] 0x12, 0x21, 0x22, 0x23, 0x17, 0x24, 0x25, 0x26,
[0x10] 0x32, 0x31, 0x18, 0x19, 0x10, 0x13, 0x1f, 0x14,
[0x18] 0x16, 0x2f, 0x11, 0x2d, 0x15, 0x2c, 0x2,0x3,
[0x20] 0x4,0x5,0x6,0x7,0x8,0x9,0xa,0xb,
[0x28] 0x1c, 0x1,0xe,0xf,0x39, 0xc,0xd,0x1a,
[0x30] 0x1b, 0x2b, 0x2b, 0x27, 0x28, 0x29, 0x33, 0x34,
[0x38] 0x35, 0x3a, 0x3b, 0x3c, 0x3d, 0x3e, 0x3f, 0x40,
[0x40] 0x41, 0x42, 0x43, 0x44, 0x57, 0x58, 0x63, 0x46,
[0x48] 0x77, 0x52, 0x47, 0x49, 0x53, 0x4f, 0x51, 0x4d,
[0x50] 0x4b, 0x50, 0x48, 0x45, 0x35, 0x37, 0x4a, 0x4e,
[0x58] 0x1c, 0x4f, 0x50, 0x51, 0x4b, 0x4c, 0x4d, 0x47,
[0x60] 0x48, 0x49, 0x52, 0x53, 0x56, 0x7f, 0x74, 0x75,
[0x68] 0x55, 0x59, 0x5a, 0x5b, 0x5c, 0x5d, 0x5e, 0x5f,
[0x70] 0x78, 0x79, 0x7a, 0x7b, 0x0,0x0,0x0,0x0,
[0x78] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x71,
[0x80] 0x73, 0x72, 0x0,0x0,0x0,0x7c, 0x0,0x0,
[0x88] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0x90] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0x98] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xa0] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xa8] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xb0] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xb8] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xc0] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xc8] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xd0] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xd8] 0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,
[0xe0] 0x1d,
Re: [9fans] Building a Raspberry Pi image / Keyboard support
What is your feeling of pi as a Plan9 terminal? such as display size, speed etc. I use ( am using now) a pi for a plan9 terminal. it is not very quick, I would not compile on it, but then that is not what a terminal is for. If you accept that it is only a terminal then it is superb. It boots in 2 or 3 seconds and consumes 2 watts. I use a standard dell keyboard and LCD display at 1920x1600. I made a special effort to find some IBM/Lenovo 3 button optical mice which work as you would expect. its the perfect plan9 terminal IMHO. -Steve
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On 5 July 2014 00:45, Anant Narayanan an...@kix.in wrote: I was able to get the keyboard to work as well, but it seems there is a different bug where plugging in both a keyboard and mouse at the same time causes usb/kb to fail. it works for me but with one mouse and not another!
Re: [9fans] Building a Raspberry Pi image / Keyboard support
If each individually works, chances are this is power related. Make sure it has enough power (5v @ 2A should more than suffice but not all adapters marked so meet their stated rating). There are two test points on the RPi. The voltage difference between the two should be close to 5V under load. If it has sufficient power, and you can run Linux, you can check out if everything works in Linux. lsusb -v can give you more details including current draw of eac device. On Jul 4, 2014, at 4:45 PM, Anant Narayanan an...@kix.in wrote: That worked great, thank you! I was able to get the keyboard to work as well, but it seems there is a different bug where plugging in both a keyboard and mouse at the same time causes usb/kb to fail. -Anant On Tue, Jul 1, 2014 at 11:32 PM, Bakul Shah ba...@bitblocks.com wrote: On Tue, 01 Jul 2014 23:01:53 PDT Anant Narayanan an...@kix.in wrote: 1. I'm trying to get a custom built kernel to boot but not having great luck, unfortunately. I got as far as mk 'CONF=pi' in /sys/src/9/bcm (those are the latest sources, correct?) which generated a 2M kernel named 's9pi'. I added that to the FAT partition on the standard 9pi SD card image and edited config.txt to point to it. Now, when I boot I see a rainbow pattern screen -- switching back to the 9pi kernel in config.txt makes it boot again. mk should've created 9pi and s9pi. Copy 9pi to the fat partition, not s9pi. What am I doing wrong? The RPi boot program doesn't know about plan9 executables. It will just copy the bits from the kernel file specified in config.txt at address 0x8000 and jump there. See 9/bcm/words for some details. 2. A couple of my keyboards don't work with the standard kernel on the SD card (the mouse works fine). Is /sys/src/omap/usbehciomap.c the right place for me to start looking into adding support for them? This thread may help: https://groups.google.com/forum/#!topic/comp.os.plan9/ycok6NTCWCg Ideally you shouldn't need more than create a custom kbmap file.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On Sat, Jul 5, 2014 at 5:15 AM, Anant Narayanan an...@kix.in wrote: That worked great, thank you! I was able to get the keyboard to work as well, but it seems there is a different bug where plugging in both a keyboard and mouse at the same time causes usb/kb to fail. I had a tough time with my kb/mouse [1]. I could fix it only by using a powered hub. [1] https://www.mail-archive.com/9fans@9fans.net/msg30165.html
Re: [9fans] Building a Raspberry Pi image / Keyboard support
Thanks for the suggestions. The keyboard + mouse work fine with Linux. In fact they work on Plan 9 together, but only for a few seconds before I get: kb: /dev/usb/ep6.1: read: i/o error kb: exiting usbotg: ep5.1 error intr 0082 usb/kb... kb: exiting Sometimes it recovers, but it's not reliable. It may be related to power, I'll try to get my hands on a powered hub and report back! -Anant On Sat, Jul 5, 2014 at 6:13 AM, Ramakrishnan Muthukrishnan vu3...@gmail.com wrote: On Sat, Jul 5, 2014 at 5:15 AM, Anant Narayanan an...@kix.in wrote: That worked great, thank you! I was able to get the keyboard to work as well, but it seems there is a different bug where plugging in both a keyboard and mouse at the same time causes usb/kb to fail. I had a tough time with my kb/mouse [1]. I could fix it only by using a powered hub. [1] https://www.mail-archive.com/9fans@9fans.net/msg30165.html
Re: [9fans] Building a Raspberry Pi image / Keyboard support
I use a standard dell keyboard and LCD display at 1920x1600. Wow, you have big screen! I only have a 20 small LCD TV, I don't watch TV much. its the perfect plan9 terminal IMHO. Indeed! pi can deal with wireless network? Kenji PS: I decided to perchase it.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
That worked great, thank you! I was able to get the keyboard to work as well, but it seems there is a different bug where plugging in both a keyboard and mouse at the same time causes usb/kb to fail. -Anant On Tue, Jul 1, 2014 at 11:32 PM, Bakul Shah ba...@bitblocks.com wrote: On Tue, 01 Jul 2014 23:01:53 PDT Anant Narayanan an...@kix.in wrote: 1. I'm trying to get a custom built kernel to boot but not having great luck, unfortunately. I got as far as mk 'CONF=pi' in /sys/src/9/bcm (those are the latest sources, correct?) which generated a 2M kernel named 's9pi'. I added that to the FAT partition on the standard 9pi SD card image and edited config.txt to point to it. Now, when I boot I see a rainbow pattern screen -- switching back to the 9pi kernel in config.txt makes it boot again. mk should've created 9pi and s9pi. Copy 9pi to the fat partition, not s9pi. What am I doing wrong? The RPi boot program doesn't know about plan9 executables. It will just copy the bits from the kernel file specified in config.txt at address 0x8000 and jump there. See 9/bcm/words for some details. 2. A couple of my keyboards don't work with the standard kernel on the SD card (the mouse works fine). Is /sys/src/omap/usbehciomap.c the right place for me to start looking into adding support for them? This thread may help: https://groups.google.com/forum/#!topic/comp.os.plan9/ycok6NTCWCg Ideally you shouldn't need more than create a custom kbmap file.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
That worked great, thank you! I'm also considering to buy pi for one of my Plan9 terminal. In that case I may also have Japanese USB keyboard problem... What is your feeling of pi as a Plan9 terminal? such as display size, speed etc. Kenji
[9fans] Building a Raspberry Pi image / Keyboard support
It's been fun playing around with Plan 9 on Raspberry Pi - thanks to everyone who made it happen. 1. I'm trying to get a custom built kernel to boot but not having great luck, unfortunately. I got as far as mk 'CONF=pi' in /sys/src/9/bcm (those are the latest sources, correct?) which generated a 2M kernel named 's9pi'. I added that to the FAT partition on the standard 9pi SD card image and edited config.txt to point to it. Now, when I boot I see a rainbow pattern screen -- switching back to the 9pi kernel in config.txt makes it boot again. The kernel I built seems to be a bit different than the one included in the SD card image, though they are roughly the same size: $ file s9pi # built kernel s9pi: Plan 9 executable, ARM 7-something $ file 9pi # kernel includes in SD card image 9pi: data What am I doing wrong? 2. A couple of my keyboards don't work with the standard kernel on the SD card (the mouse works fine). Is /sys/src/omap/usbehciomap.c the right place for me to start looking into adding support for them? Thanks again! -Anant
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On Tue, 01 Jul 2014 23:01:53 PDT Anant Narayanan an...@kix.in wrote: 1. I'm trying to get a custom built kernel to boot but not having great luck, unfortunately. I got as far as mk 'CONF=pi' in /sys/src/9/bcm (those are the latest sources, correct?) which generated a 2M kernel named 's9pi'. I added that to the FAT partition on the standard 9pi SD card image and edited config.txt to point to it. Now, when I boot I see a rainbow pattern screen -- switching back to the 9pi kernel in config.txt makes it boot again. mk should've created 9pi and s9pi. Copy 9pi to the fat partition, not s9pi. What am I doing wrong? The RPi boot program doesn't know about plan9 executables. It will just copy the bits from the kernel file specified in config.txt at address 0x8000 and jump there. See 9/bcm/words for some details. 2. A couple of my keyboards don't work with the standard kernel on the SD card (the mouse works fine). Is /sys/src/omap/usbehciomap.c the right place for me to start looking into adding support for them? This thread may help: https://groups.google.com/forum/#!topic/comp.os.plan9/ycok6NTCWCg Ideally you shouldn't need more than create a custom kbmap file.
