Re: [9fans] plan9 go output faults on 9vx but ok on cpu
I'm a bit cinfusing... There is a flag (GPOS=plan9) to ebnable plan9 os in the standard Go dsitribution. How the patches you posted here now and before are related to that flag. I suppose the original plan9 flag is for plan9port. Am I correct? That plan9 flag works for plan9port? Then how I can use it on my linux box with plan9port. Kenji
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
On Sat, Jan 15, 2011 at 11:01 AM, wrote: > I'm a bit cinfusing... > > There is a flag (GPOS=plan9) to ebnable plan9 os in the standard Go > dsitribution. > How the patches you posted here now and before are related to that flag. > I suppose the original plan9 flag is for plan9port. > Am I correct? > > That plan9 flag works for plan9port? > Then how I can use it on my linux box with plan9port. > > Kenji > Setting GOOS=plan9 when using the main Go distribution (and linking with symbols stripped 8l -s) will compile to native plan 9 binaries. They assume a stack layout that is not correct when running on 9vx as Anthony points out. The patch I posted is to replace the hard coded values with relative offsets from _tos, so the binaries will run both in 9vx and on a native install of plan 9. Previously I posted a patch for syscall and os Go packages against the Go distribution to allow writing code that can actually do something useful besides println. I'm not sure what you mean by using these with plan9port... Pavel
Re: [9fans] ohci funny on sb850
Its not faulty caps, they just have a limited life, dried up electrolytic caps is the cause of most electronics dieing of old age. -Steve
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
> That plan9 flag works for plan9port? > Then how I can use it on my linux box with plan9port. I looked at connecting Go and p9p a few months back, before my assignments in Cape Town put a halt to my efforts. My conclusion at the time was that it was a worthwhile objective that could be accomplished, but not without a great deal of trouble. Because of the scope of the project, I estimated that the chances of getting upstream approval for the changes, be they to p9p or to Go, would be minimal despite Russ' involvement in both projects. Merging p9p, Go and Plan 9 in a portable manner seems to me to be really hard. I would be extremely pleasantly surprised if somebody had achieved even the smallest portion of such merging and had it pulled up to the source projects. Also, without carefully documentation one runs a real risk of having to repeat and sometimes rediscover many of the changes. At least, that is the situation I am confronted by at this very moment. In a nutshell, I actually took a very recent release of Go and tried to build a Plan 9 version: cd $GOROOT/src GOOS=plan9 ./make.bash I was not surprised that it did not build correctly on my Ubuntu workstation. Fixing it did not seem a trivial task and a cursory web search did not reveal any encouraging help. Right now, I have a few days in which to resurrect work I did initially that concluded with a "working" version of the Hello World "C" program compiled and executed on Plan 9/386 using modifed Go sources to compile and build the "C" development toolchain under Plan 9. It is daunting how much effort I estimate I will need to do to get that far, specially with a view to propagate the rather extensive changes to the Go source release. On the positive side, I had invested no effort in the Go aspects of the project and I'm grateful to those who have added the Go features for Plan 9 to the Go release. My regret is that I am so far out of the loop, I don't even know where the loop is :-( ++L
Re: [9fans] ohci funny on sb850
> Its not faulty caps, they just have a limited life, > dried up electrolytic caps is the cause of most > electronics dieing of old age. In the days before I took up electronics as a hobby, valves were seated in sockets because it was known that the equipment they were used in would outlive them. Maybe we should recommend easily replaceable capacitors in modern equipment instead of blindly accepting that a component of extremely low cost should wreck expensive machinery beyond repair. ++L
Re: [9fans] is this crazy?
I have this exact thing. Direct from China. It has a terribly slow interface, heats up during calls, and runs out of battery during actual call times, like no other. It's good if all you care about is the "smart" part of "smart phone". Not much of a phone. Stickin' with my Motofone. ak On Sat, Jan 8, 2011 at 5:37 AM, Bruce Ellis wrote: > I had this crazy idea for a CDM module. Stick in a smart phone. > > I contacted some friendly asian folk and they sent me this > > 2.4" QVGA screen > Quad Band > Two Sims > Wifi, Bluetooth > Analog TV > etc. > > Bundled with ... > Google/MSN/Java/Yahoo/SKYPE > > It's comaptible with the Nokia Devkit so I'm adding > > imp/cloud/deeptext/shaneyleaks etc... > > $60 for 1 of. > > Works well. > > brucee > >
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
On Sat, Jan 15, 2011 at 4:00 AM, Anthony Martin wrote:
> Pavel Zholkover once said:
>> I have no idea what is causing it to die, I've tried adding a bunch of
>> INT $3 to see how far in the flow I can get, but all I get this:
>>
>> 9vx panic: unknown trap/intr: 0x203
>> aborting, to dump core.
>>
>> for an INT $3 just before
>> CALL SI // fn()
>
> This happens because the linker outputs the two bytes
> { 0xCD, 0x03 } for an INT $3 instruction but libvx32
> only sends a VXTRAP_BREAKPOINT to 9vx if it sees an
> INT3 instruction (a single 0xCC byte). Try using a
> 'BYTE $0xCC' instead.
>
> Anthony
Thanks, that did the trick.
This is what I get when running goroutines on 9vx with a 0xCC
breakpoint compiled in:
% goroutines
goroutines 69: suicide: sys: breakpoint pc=0x9e44
id: 1 0
id: 1 1
id: 1 2
id: 1 3
id: 1 4
id: 1 5
id: 1 6
id: 1 7
id: 1 8
id: 1 9
% acid 69
/proc/69/text:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
no symbol information
acid: regs()
PC 0x9e44 0x9e44 ?file?:0
SP 0x000560e0 ECODE 0x EFLAG 0x
CS 0x DS0x SS 0x
GS 0x FS0x ES 0x
TRAP0x0003 breakpoint
AX 0x0004c0c0 BX 0x0004c0c0 CX 0x0fc8 DX 0x00054100
DI 0x00056100 SI 0x72f8 BP 0x
acid: asm(*PC-32)
0x9e24 0x9e24 ADDL$0x1ed2c,AX
0x9e29 0x9e29 MOVLDX,0xfff8(AX)
0x9e2c 0x9e2c MOVLBX,0xfffc(AX)
0x9e2f 0x9e2f MOVL0x1ed2c,AX
0x9e35 0x9e35 MOVL0x30(AX),AX
0x9e38 0x9e38 MOVLAX,0x24(BX)
0x9e3b 0x9e3b CALL0x1c10
0x9e40 0x9e40 MOVL0x0(DX),DX
0x9e42 0x9e42 MOVL0x0(BX),BX
0x9e44 0x9e44 INT 3 <=== we stopped here,
runtime.rfork() in src/pkg/runtime/plan9/sys.s
0x9e45 0x9e45 CALL* SI
0x9e47 0x9e47 CALL0x9eac
0x9e4c 0x9e4c RET
0x72f8 is runtime.mstart as it should...
acid: asm(*SI)
0x72f8 0x72f8 MOVL0x1ed2c,CX
0x72fe 0x72fe MOVL0xfff8(CX),CX
0x7301 0x7301 CMPL0x0(CX),SP
0x7303 0x7303 JHI 0x730e
0x7305 0x7305 XORLDX,DX
0x7307 0x7307 XORLAX,AX
0x7309 0x7309 CALL0x1a75
0x730e 0x730e SUBL$0x8,SP
0x7311 0x7311 MOVL0x1ed2c,AX
0x7317 0x7317 MOVL0xfff8(AX),AX
0x731a 0x731a MOVL0x1ed2c,CX
0x7320 0x7320 MOVL0xfffc(CX),CX
0x7323 0x7323 MOVL0x0(CX),CX
0x7325 0x7325 CMPLCX,AX
0x7327 0x7327 JEQ 0x7336
0x7329 0x7329 MOVL$0x1eb80,AX
0x732e 0x732e MOVLAX,0x0(SP)
0x7331 0x7331 CALL0x81ee
0x7336 0x7336 MOVL0x1ed2c,AX
0x733c 0x733c MOVL0xfffc(AX),AX
0x733f 0x733f MOVL0x94(AX),AX
0x7345 0x7345 CMPLAX,$0x0
0x7348 0x7348 JNE 0x735e
0x734a 0x734a CALL0x2d75
0x734f 0x734f MOVL0x1ed2c,CX
0x7355 0x7355 MOVL0xfffc(CX),CX
0x7358 0x7358 MOVLAX,0x94(CX)
0x735e 0x735e CALL0x9e4d
0x7363 0x7363 CALL0x74c3
0x7368 0x7368 ADDL$0x8,SP
I can't tell from this why 9vx is dying on me and I don't know how to
use acid to debug a child process after rfork,
is there something like gdb's set follow-fork-mode child ?
Pavel
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
On Sat, Jan 15, 2011 at 11:30 AM, wrote: > In a nutshell, I actually took a very recent release of Go and tried > to build a Plan 9 version: > > cd $GOROOT/src > GOOS=plan9 ./make.bash > > I was not surprised that it did not build correctly on my Ubuntu > workstation. Fixing it did not seem a trivial task and a cursory web > search did not reveal any encouraging help. If you try applying http://codereview.appspot.com/3816043/ you can get pretty far.. you need to cd src/pkg make clean GOOS=plan9 make -k install You'll get os, syscall, fmt and a bunch of other portable go libraries. > Right now, I have a few days in which to resurrect work I did > initially that concluded with a "working" version of the Hello World > "C" program compiled and executed on Plan 9/386 using modifed Go > sources to compile and build the "C" development toolchain under Plan > 9. It is daunting how much effort I estimate I will need to do to get > that far, specially with a view to propagate the rather extensive > changes to the Go source release. On the positive side, I had > invested no effort in the Go aspects of the project and I'm grateful > to those who have added the Go features for Plan 9 to the Go release. > I think that you can produce a "C" hello world pretty easily if you provide stubs for 8l (like morestack and etc.) and use GOOS=plan9 8l -s to link you stuff together. Pavel
Re: [9fans] Need help on installing Google Go for The Plan 9 Operating system
It should compile/install (via debian packages) on linuxemu in Plan 9, just fine. Then you can program, compile, execute all in one rio space. ak On Mon, Jan 10, 2011 at 8:34 AM, Skip Tavakkolian wrote: > I don't believe there is a way to build go on plan9. You have to build it on > a Linux box. Then compile go programs on the Linux box and run them on Plan > 9. If you use drawterm your Linux fs will be accessible via /mnt/term > > -Skip
[9fans] sound, graphics, tuner
Hello, Recently I came across a need to tune a musical instrument. I tried to think how difficult it'd be to write a program which would 1) read the signal from a microphone, 2) process it, 3) show the tone played and its deviation, possibly graphically. (In linux, lingot is the example.) I have a good notion about the middle task (2). So far I've never tried to read anything from a soundcard, nor to create any graphics in plan9. First, I am aware that in linux the soundsystem is controlled by something called ALSA or OSS. It's always seemed to me a complicated thing (I may be well wrong). Second, in linux there are many graphical libraries like GTK, Qt, wxWidgets, Tk, others. Is there anything in plan9 that could be simple to grasp and create an analog gauge with it? Can anybody comment this and/or possibly point me at some good documents? Thanks Ruda
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
> I think that you can produce a "C" hello world pretty easily if you > provide stubs for 8l (like morestack and etc.) and use GOOS=plan9 8l > -s to link you stuff together. Thank you, it's my intention to get as many of these poorly connected pieces under my belt so I have a better view of the whole picture, so I'll definitely try out your suggestions and possibly build them into rc and/or sh scripts so they are not easily lost :-) My primary objective was and remains to jack up the Plan 9 "C" toolchain with newer features it failed to inherit from Inferno and now Go, with my own emphasis on ELF capabilities. There's one significant hurdle to be surmounted, more a design issue than a practical problem, namely that the Plan 9 multi-architecture ways deserve better multi-platform capabilities: the classic approach lacks equivalent convenience to be able to target Operating Systems other than Plan 9. That one can get the Go language and all its novelties and excitement thrown in can only be considered a gift from (Google-) heaven. In passing, there is no doubt that you have a much better understanding of the issues surrounding this subject than I have. I hope you don't mind me asking for direction when I get lost. I also hope that others on this mailing list have sufficient interest in the Go port to Plan 9 to bear with my occasional post. ++L
Re: [9fans] Need help on installing Google Go for The Plan 9
> It should compile/install (via debian packages) > on linuxemu in Plan 9, just fine. Then you can > program, compile, execute all in one rio space. Ouch! This is exactly what I _don't_ want :-) I do respect that others may be considerably more pragmatic than I, in fact I find it warmly ironic than I sure hadn't tought of that! ++L
Re: [9fans] sound, graphics, tuner
> Can anybody comment this and/or possibly point me at some good documents? It looks kind of easy, although I've never gone there myself. After all, you just need to display two lines, one fixed (you omitted to mention that you need to specify the tone you are after) and one that moves closer or further from the base line as the tuning is adjusted. Two points may suffice, but they may be hard to read. As for the audio input, I seem to recall that the audio device delivers numeric values representing the sound, so all you need to do is keep reading, deleting a previous display and producing a new one as each sample is input. Am I being overly simplistic? It sounds almost like a trivial shell (rc) script, if you don't need the graphics. ++L
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
> If you try applying http://codereview.appspot.com/3816043/ you can get > pretty far.. Could you provide more detailed instructions, please? Mercurial seems very helpful, but the learning curve can be quite steep. I presume this requires hg to be involved? ++L
Re: [9fans] sound, graphics, tuner
On Sat, Jan 15, 2011 at 11:38 AM, wrote: >> Can anybody comment this and/or possibly point me at some good documents? > > It looks kind of easy, although I've never gone there myself. After > all, you just need to display two lines, one fixed (you omitted to > mention that you need to specify the tone you are after) and one that > moves closer or further from the base line as the tuning is adjusted. > Two points may suffice, but they may be hard to read. Aliasing... You need to read more than two points, even if you produce only two after. Essentially I would do something like: Read N PCM samples from the sound card, this is just a read from the audio in file, easy part. The samples you can read from http://plan9.bell-labs.com/magic/man2html/3/audio audio(3) or a similar interfaces provided by usb/audio usb(4). Calculate some sort of windowed FFT. Find the peak (I would correlate with a moving peak shape and find a big value). Generate the read/estimated frequency, fin. Then you can draw the margin for the frequency error you tolerate which are probably two lines fthlow, fthhigh or different colors dividing the window/output in three parts, too high, too low and acceptable and superpose the line depicting fin over it (something like the letonian flag). fthlow and fthhigh can come from the user clicking on the window and moving up and down or from some slider (I would do the first).. This last part, I would use draw http://plan9.bell-labs.com/magic/man2html/2/draw draw(2). You can use control http://plan9.bell-labs.com/magic/man2html/2/control control(2) to add sliders but for what you are doing just drawing rectangles and lines should be fine. HTH. G.
Re: [9fans] ohci funny on sb850
On Sat Jan 15 04:25:22 EST 2011, st...@quintile.net wrote: > Its not faulty caps, they just have a limited life, > dried up electrolytic caps is the cause of most > electronics dieing of old age. is that lifetime 2 years? i have 3 va linux machines here that are still working great with no leaky caps. they are all about 12 years old. (by the way, the motherboard + processor + memory is free to a good plan 9 home. you pay shipping.) - erik
Re: [9fans] ohci funny on sb850
On Sat, 15 Jan 2011, erik quanstrom wrote: > On Sat Jan 15 04:25:22 EST 2011, st...@quintile.net wrote: > > Its not faulty caps, they just have a limited life, > > dried up electrolytic caps is the cause of most > > electronics dieing of old age. > > is that lifetime 2 years? > > i have 3 va linux machines here that are still working great > with no leaky caps. they are all about 12 years old. > > (by the way, the motherboard + processor + memory > is free to a good plan 9 home. you pay shipping.) You would be shipping from where, approx.? How much memory in that thar thing? :) -- Duke
Re: [9fans] is this crazy?
On Sat, Jan 15, 2011 at 1:42 AM, Akshat Kumar wrote: > I have this exact thing. Direct from China. > > It has a terribly slow interface, heats up > during calls, and runs out of battery during > actual call times, like no other. > > It's good if all you care about is the "smart" > part of "smart phone". Not much of a phone. is it like the cinco phone? Maybe it comes with its own tube of burn lotion! http://video.adultswim.com/tim-and-eric-awesome-show-great-job/cinco-fone.html ron
Re: [9fans] sound, graphics, tuner
> Read N PCM samples from the sound card, this is just a read from the > audio in file, easy part. > The samples you can read from > http://plan9.bell-labs.com/magic/man2html/3/audio > audio(3) or a similar interfaces provided by usb/audio usb(4). Ok. To start with, audio(3) seems to support soundblaster-16-compatibles. What about others? I guess mine could be AC'97 on one of my notebooks (there fortunately seems to be some support for this one elsewhere, too), while god knows what on another. Connected to this: How do I find from within plan 9 what soundcard/hardware I have? > This last part, I would use draw > http://plan9.bell-labs.com/magic/man2html/2/draw > draw(2). You can use control > http://plan9.bell-labs.com/magic/man2html/2/control control(2) > to add sliders but for what you are doing just drawing rectangles and > lines should be fine. Ok. I ask because some widget sets already have an analog-like gauge I'd like to use, e.g. Tk::gauge. (What'd be the situation in Inferno? They have some Tk, don't they?) Thanks Ruda
Re: [9fans] sound, graphics, tuner
On Sat, Jan 15, 2011 at 10:50 AM, Rudolf Sykora wrote: >> Read N PCM samples from the sound card, this is just a read from the >> audio in file, easy part. >> The samples you can read from >> http://plan9.bell-labs.com/magic/man2html/3/audio >> audio(3) or a similar interfaces provided by usb/audio usb(4). > > Ok. To start with, audio(3) seems to support soundblaster-16-compatibles. > What about others? I guess mine could be AC'97 on one of my notebooks > (there fortunately seems to be some support for this one elsewhere, > too), while god knows what on another. Connected to this: > How do I find from within plan 9 what soundcard/hardware I have? > >> This last part, I would use draw >> http://plan9.bell-labs.com/magic/man2html/2/draw >> draw(2). You can use control >> http://plan9.bell-labs.com/magic/man2html/2/control control(2) >> to add sliders but for what you are doing just drawing rectangles and >> lines should be fine. > > Ok. I ask because some widget sets already have an analog-like gauge > I'd like to use, e.g. Tk::gauge. (What'd be the situation in Inferno? > They have some Tk, don't they?) > > Thanks > Ruda > > If you're tuning a wind instrument, you could just print out the frequency of middle C and then display the calculated frequency coming into the microphone below it. For a guitar tuner, just print out more frequencies (EADGBE)... this is the lazy man's way to do it, but it would be a way to test it at first, at least. If I wanted to make it fancy and graphical, I'd have a horizontal line, bisected in the center by a vertical line representing the target frequency, then draw another moving vertical line to represent the current frequency. John
[9fans] sheevaplug catatonic
has anyone else had a sheevaplug go catatonic? mine reset yesterday and now no longer responds to the usb/serial interface and the ethernet lights are stuck. - erik
Re: [9fans] exporting a namespace
Just FYI, I wanted to verify that this works and I just did. Having a 9vx function as the fs for an Ovaro (TI OMAP) sudo ~/src/plan9/vx32/src/9vx/9vx -r ~/src/9vx-0.12/ The sudo is important. Then in the 9vx instance: aux/listen1 -v tcp!*!564 /bin/exportfs -s Then I boot the Ovaro: Filename '9beagletxt'. Load address: 0x8031 Loading: # # done Bytes transferred = 1315056 (1410f0 hex) Overo # tftpboot 8030 0015c928d6a1 smc911x: detected LAN9221 controller smc911x: phy initialized smc911x: MAC 00:15:c9:28:d6:a1 Using smc911x-0 device TFTP from server 192.168.2.1; our IP address is 192.168.2.5 Filename '0015c928d6a1'. Load address: 0x8030 Loading: T # done Bytes transferred = 207 (cf hex) Overo # go 8031 and then it all comes up with prompts: filesystem IP address[no default]: 192.168.2.1 authentication server IP address[no default]: 192.168.2.1 bad nvram key bad authentication id bad authentication domain authid: bootes authdom: YOURNAMEHERE secstore key: password: can't write key to nvram: jmk added reentrancy for threads version...time... Password: Confirm password: 192.168.2.5 Jan 15 15:03:21 cron for upas owned by rminnich 192.168.2.5 Jan 15 15:03:21 cron for root owned by rminnich 192.168.2.5 Jan 15 15:03:21 cron for sys owned by rminnich init: starting /bin/rc 192.168.2.5# The point being that 9vx is a perfectly capable way to have an fs for all your service needs :-) Thanks to Geoff for his infinite patience with my questions ... ron
Re: [9fans] sound, graphics, tuner
> To start with, audio(3) seems to support soundblaster-16-compatibles. > What about others? to my knowledge you have: soundblaster comptibles, usb thingys, and kirkwood. (the kirkwood driver is in my contrib, it's my 1½st driver, so beware. oh, and record isn't tested (and I would guess doesn't work)). hum, drawterm too (which is a bit of a corner case). that said, the audio interface is pretty simple, and if your card is reasonable (not my laptop) i doubt it would be hard to write, the mixing interface has a lot of faces (which is why i havn't annoyed geoff with the kw yet), but that won't matter for you. > How do I find from within plan 9 what soundcard/hardware I have? pci(1)? enjoy, tristan -- All original matter is hereby placed immediately under the public domain.
[9fans] plan9 compatible notebook
Hello, can anybody recommend any plan9 compatible notebook? I mean with support for say its every hardware part? Does such a thing exists? :) Thanks Ruda
Re: [9fans] plan9 compatible notebook
Check the wiki page 'supported hardware.' There's at least one thinkpad on the list.
Re: [9fans] plan9 compatible notebook
> I mean with support for say its every hardware part? You can't even do that with UNIX these days :-p
Re: [9fans] plan9 compatible notebook
I find my 600e to be very fast with Plan 9. *ducks* On 1/15/11, Jacob Todd wrote: > Check the wiki page 'supported hardware.' There's at least one thinkpad on > the list. >
Re: [9fans] plan9 compatible notebook
My dell inspiron 1000 works fairly well with plan 9, too. The ethernet device doesn't work (there is a driver for it, there's some niggle with the card, I suppose). Usb works, video works, sound doesn't, however. The sound card is some intel card (intel-8x0 driver on lunix).
Re: [9fans] plan9 compatible notebook
I have a ThinkPad T400. 9atom works with SATA controller in IDE mode (I think Erik Quanstrom works on making the DVD-RW drive work in AHCI mode). Never tested sound. Works great :-). -- Aram Hăvărneanu
Re: [9fans] plan9 compatible notebook
On Jan 15, 2011, at 6:50 PM, Aram Hăvărneanu wrote: > I have a ThinkPad T400. 9atom works with SATA controller in IDE mode > (I think Erik Quanstrom works on making the DVD-RW drive work in AHCI > mode). Never tested sound. Works great :-). > > -- > Aram What about graphics and wifi? What resolution and color depth are you able to run in? -sl
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
> On Sat, Jan 15, 2011 at 12:40 PM, wrote: >>> If you try applying http://codereview.appspot.com/3816043/ you can get >>> pretty far.. Your new patch here made me success to make patch. Previous one had problem to patch file_posix.go etc. By the way, now I got the real procedure to get it work, I think. First, compile Go tree as GOOS=linux (not plan9). Second, go to src/pkg/syscall, and GOOS=plan9 make -k install. Third, then go to src/pkg/os, and GOOS=plan9 make -k install. However, even if I could make a binary for Plan 9, I have to compile it on linux machine, and move the binary to Plan 9. Am I right? I tried GOOS=plan9 from top level of the go tree, but it failed somewhere where I didn't dig into more. Kenji
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
oups! I got hello: exec header invalid Kenji
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
Yes. Drawterm is convenient for executing programs exported in /mnt/term On Jan 15, 2011, at 5:51 PM, kokamoto wrote: > However, even if I could make a binary for Plan 9, I have to compile it > on linux machine, and move the binary to Plan 9. > Am I right?
Re: [9fans] sound, graphics, tuner
There exist two different AC97 drivers; look at the port of Doom to plan9 for pointers to one of them. -- vs
Re: [9fans] sound, graphics, tuner
The hg repo for 9doom has been down for ages, so that's not possible atm.
Re: [9fans] plan9 go output faults on 9vx but ok on cpu
Ok, now I got the right procedure to run hello.go. 1) do the patch posted here most recently 2) make sure GOOS=plan9 etc 3) at the top of the source tree, that should be $GOROOT/src 4) ./make.bash it stops at src/pkg/exec. Don't mind it 5) 8g hello.go 6) 8l -s -o hello hello.8 7) copy the hello to somewhere in the real Plan 9 file tree 7) cd at the above directory 8) ./hello Kenji
