Re: [9fans] Plan 9 C compiler for Xtensa CPUs

2019-07-27 Thread Anthony Martin
Charles Forsyth once said: > I'd need a letter or number and thought about reusing x (xa/xc/xl) since > the AT&T DSP is long gone https://github.com/0intro/plan9-mips/tree/master/sys/src/cmd/4c https://github.com/0intro/plan9-mips/blob/master/rc/bin/xc I think I sent this to the list once before

Re: [9fans] Trying to make 9front work on QWERTZ

2019-07-27 Thread cinap_lenrek
on my t23, which has physical german keyboard layout, the scancode for the [<>|] key left to the [Y] key is 0x56 (86 decimal), which is not mapped with us layout. tho this is mapped in german keyboard layout: term% grep '86' /sys/lib/kbmap/de 0 86 '< 1 86 '> 2 86

Re: [9fans] Plan 9 C compiler for Xtensa CPUs

2019-07-27 Thread Richard Miller
> https://www.pbrane.org/comp.html I've used .x for riscv32 but it's easily changed. I see the above list uses .e and .j for riscv and riscv64 - are these just reserved or are there actual compilers somewhere?

Re: [9fans] Plan 9 C compiler for Xtensa CPUs

2019-07-27 Thread Anthony Martin
Richard Miller <9f...@hamnavoe.com> once said: > I see the above list uses .e and .j for riscv and riscv64 - > are these just reserved or are there actual compilers somewhere? No, it was just a suggestion on my part. If I remember correctly, I thought it was mildly clever that 'e' is the fifth let

Re: [9fans] Trying to make 9front work on QWERTZ

2019-07-27 Thread Jens K. Loewe
> maybe your keyboard produces a different scancode? The internal T60 keyboard, a native USB keyboard and a DIN-to-USB converted keyboard all produce the wrong scancodes on different hardware? That sounds unreasonable. But I'll try to test that next week ... thank you. Am Sa., 27. Juli 2019 um 1