IRC logs for #openrisc Monday, 2013-10-07

--- Log opened Mon Oct 07 00:00:28 2013
stekernhansfbaier: no reason, I had to choose one of the two04:47
hansfbaierstekern: thanks. Got the de0_nano today. Did not think it is *that* small05:09
hansfbaierstekern: really sweet05:09
hansfbaierstekern: Are the meeting slides online yet? I am ready to devour the or1k-Progress report :)05:10
hansfbaiermor1kx that is05:10
hansfbaierstekern: Another question for orpsocv3/sockit: After building the bootloader, which Linux-Distro can I use, is the factory yocto image fine?05:12
stekernhansfbaier: I don't think we've got around to put up the material yet, I know I haven't at least05:13
hansfbaierstekern: Another one for the sockit: The qsys contains next to nothing (only HPS and DDR3 controller), is that right? The opencores are mapped in with the tcl I suppose. How do I boot Linux / debug it. Do I have to solder in the JTAG HEADER and disconnect the USB Blaster II? How do you debug that beast?05:13
stekernbut my slides on the mor1kx update is here:
hansfbaierstekern: With: How do I boot Linux, I mean on the OpenRISC, not ARM.05:14
stekernas for the rootf, I use this:
hansfbaierstekern: Cool, does that run X?05:17
stekern(qsys) yes, that's right. The orpsoc cores are "mapped in" by orpsoc (look in the orpsoc.core file)05:17
hansfbaierstekern: How does X run, I guess I have to add a framebuffer stanza in the dts?05:18
stekernit runs X, but you'll need a custom built kernel with the ocfb.c framebuffer driver05:18
stekern(from the openrisc tree)05:18
stekern(and I have some local changes to that in my local tree)05:19
hansfbaierstekern: Is that on the HPS side? and the ocfb is on the FPGA, right?05:19
hansfbaierstekern: would be nice to have a branch for that on  the kernel tree, would that make sense?05:19
stekern <- my current local version05:20
stekernnah, I'm planning on trying to upstream the ocfb.c ASAP05:20
hansfbaierstekern: I'm a bit confused here. But the kernel is for the HPS, right?05:20
stekernok, let's straight things out. ;)05:21
hansfbaierWhat would be the best way to build the kernel?05:21
stekernfrom the HPS side, you have access to all the wishbone peripherals on the FPGA side + the DDR3 on the FPGA side (and it's own DDR3)05:21
hansfbaierInstall source on ARM and compile on the HPS?05:22
stekernfrom the FPGA side, you have access to the HPS DDR305:22
stekernso, you can use the framebuffer core from both the HPS and the openrisc side (not at the sime time of course)05:23
hansfbaierstekern: Would X/OpenRISC be able to run already? It does so in poke53282's emulator, but probably not for something useful, since there is no OpenRISC distro yet AFAIK05:23
stekernyes, I've started X on the sockit (on openrisc)05:24
stekernbut I don't have a pointing device (or keyboard) for the openrisc side, so it's not very useful on that board (yet)05:24
stekernso, regarding which kernel to use on the HPS side. use this git repo:
stekernand then you want a kernel > 3.8, since USB OTG is broken on everything < than that05:28
stekernI checked out rel_13.07_RC5, which is a 3.9 kernel05:29
hansfbaierstekern: Has the linaro any significant advantages over Debian Wheezy? I have a Debian on my flash right now.05:29
stekernprobably not, I'm a Linux on arm newbie, so I just took what crossed my path first05:30
LoneTechjuliusb: yes, it's quite possible to run ordb2a with adv_debug, we've done so05:30
hansfbaierstekern: How do you boot Linux/OpenRISC and debug it? OpenOCD doesn't do USB Blaster II....05:31
stekernhansfbaier: ok, so to do that I use a small ARM program I wrote to write a binary into the FPGA DDR305:32
stekernthat I promised I would extract from my board for you, but I didn't get around to do that during the weekend05:33
stekernI can do that tonight for you05:34
stekernbut it's not very complex, basically I just mmap FPGA DDR3, byteswap the binary and copy it there05:35
hansfbaierstekern: OK, no hurry. But many thanks.... I am done with the labs. Homework done :)05:35
hansfbaierstekern: yes, already looked at the examples.05:35
hansfbaierstekern: What to do when the DS5-Evaluation-License is expired?05:35
hansfbaierstekern: solder in the JTAG header and disconnect the Blaster?05:36
stekernand then I use this: to flick the reset lines05:36
stekern(that memtool is included in the yocto image)05:37
stekernit's pretty useful to quickly read/write things from/to the wishbone peripherals05:38
stekernI haven't used the DS5, but yes it's a problem that blaster II isn't supported by openocd05:38
stekernI did a half-assed effort to reverse engineer it to add support, and made some progress, but never got it finished05:40
stekernI have soldered on the jtag header and connected a "normal" usb-blaster to that05:40
stekernbut I haven't really tested debugging the ARM core with it though05:41
stekern...but, I have an other idea how to solve the debugging of openrisc problem. I want to compile openocd on the ARM and then have some simple regbased access into the openrisc jtag tap05:43
hansfbaierstekern: I have an FTDI-based china JTAG (jtagkey) clone here that works quite ok on my Cortex-M3.05:43
stekernand then write a custom openocd driver for that reg-based interface05:43
stekernthen you can just connect gdb from your workstation through the openocd bridge running on the ARM05:45
hansfbaierstekern: good idea05:45
stekernthe only thing I was uncertain about regarding that setup was if openocd would easily be compilable on the ARM, but I asked _franck_ about that during the weekend and he said it's commonly done05:46
stekernand the missing usb-blaster ii support in openocd isn't the only reason I'd like to do that, the other reason is that when you connect through the JTAG, it upsets the arm (reset it)05:53
stekernnot sure if that's because some configuration miss in openocd or if it's unavoidable though...05:54
hansfbaierstekern: good to know06:00
hansfbaierstekern: Please allow me another question: I have my julius-based locally modified linux-Kernel here running. But if I wanted to move to a newer version (that has the W5100 driver), what would be the recommended revision/tag/branch to go to?06:04
stekernumm, define "julius-based locally modified"?06:05
hansfbaierstekern: Another last question: Do you get paid for working on OpenRISC? The time and effort you put into this is really monumental...06:05
hansfbaierstekern: Wait a moment: git status still running :]06:06
hansfbaierbased on 065bba63d70b6de4f56c75f5e3a89ac2a5d0b01f06:06
stekernhansfbaier: no, I don't get paid for working on openrisc, it's just a hobby06:06
hansfbaierstekern: whooaa. Do you ever sleep?06:07
stekernno =)06:07
hansfbaierstekern: You will die young :)06:07
hansfbaierstekern: need at least 6hrs or heart damage .....06:08
stekernhansfbaier: that oppurtunity have almost already past... ;)06:08
Powermaniachansfbaier: You can survive on 3 hours of sleep a day...06:10
stekernnah, I think that studies have shown that the sleeprequirements are highly individual06:10
stekernthere are no such thing as a fixed number that fits all, and specifically not that they have to be done continously06:13
Powermaniacstekern: True06:14
hansfbaierstekern: where did you get your knowledge about CPU design (see mor1kx slides). Got a recommendation?06:15
stekernumm, hacking on mor1kx ;)06:15
Powermaniachansfbaier: Haha I've asked him that question before, and got basically the same response06:16
hansfbaierstekern: OK, good to hear. After the 2012 slides I got some appetite for that :)06:16
stekern2012 slides?06:17
olofkEveryone got home safely?06:19
stekernolofk: yup06:19
olofkI fixed bug 97 on the flight back home. Nasty little thing. I guess no one has really used l.rori :)06:19
Powermaniacolofk: Did you get home safely?06:20
olofkPowermaniac: No. I'm still hiding under juliusb bed. Just make sure not to tell him06:20
stekernwe had some initial exceitement with what train we should jump on, and the switch at kings cross was a bit tight, but otherwise it went smooth06:21
PowermaniacJust thought it would be rude not to ask...06:21
olofkActually, the flight was delayed on the way back home, but they managed to catch up enough to play Ryanair's infamous we're-in-time-fanfare06:21
olofkstekern: The whole room was screaming GET ON THE TRAIN when you we're talking to juliusb on the phone :)06:22
stekernthere was some mixed messages about what station we should jump off at too, there was engineering work on the line so they were suggesting some other stations than the hitchin station that juliusb adviced for the switch towards kings cross06:24
stekernbut after consulting some locals on the train we found out that the hitchin station was still fine for the switch06:24
olofkI wouldn't trust getting directions from people who drive on the wrong side of the road06:30
PowermaniacWait what side of the road do you drive on...Australians drive on the left.06:33
PowermaniacOh just checked for myself, right hand traffic in most of Europe...06:35
PowermaniacAnd well most of the world actually06:35
PowermaniacMore relevant to the channel question: Do you guys use the programming language C often?06:37
hansfbaierPowermaniac: If you want to do embedded/kernel development write bare metal applications it's fundamental.06:39
Powermaniachansfbaier: Thought that might be the case, trying to learn C now actually. Ditched Java as well I wasn't getting anywhere with it a while ago now and it turned out it wasn't really used for the things I was interested in. And is also supposedly a 'bad' language06:40
olofkFuck... updated the wrong bug06:42
olofkNo, it was correct06:42
hansfbaierPowermaniac: Java is actually a very useful language, if you want to develop banking applications and/or solid enterprise / web applications06:42
stekernPowermaniac: we drive on the right side of the road, not the wrong06:43
hansfbaierIt's one of the top used languages06:43
olofkstekern: :)06:43
Powermaniachansfbaier: Oh okay, I've just been it has a lot of issues...06:43
hansfbaierPowermaniac: I made most of my living with Java as an enterprise/web developer06:43
hansfbaierPowermaniac: now I'm into embedded and I use C06:43
Powermaniacstekern: Haha, I have to wonder why they wouldn't just make right side driving global. Probably too difficult to change now though06:43
hansfbaierThose two are good for different things06:43
hansfbaierPowermaniac: Indonesia drive on the left too06:44
Powermaniacstekern: Probably has something to do with England and the CommonWealth I assume06:44
hansfbaierI've converted06:44
hansfbaierPowermaniac: don't know. Indonesia was a dutch colony. Where do the dutch drive?06:44
Powermaniachansfbaier: The right, hmm that is weird then06:45
olofkPowermaniac: Yeah, just some smaller provinces like Australia and India drives on the left side06:45
PowermaniacHeh North America originally drove on the left06:46
PowermaniacWell The United States I mean06:46
stekernyeah, I think many countries have switched, sweden used to drive on the left too06:53
poke53282hansfbaier: X is not useful at the moment. It is working but still unstable. And yes, a distro would be nice.06:55
poke53282At the moment I am thinking of a simple image for or1ksim and QEMU that contains native compiler and tools.06:55
poke53282Then it would be much easier for others to develop something for or1k.06:55
poke53282Since today I can offer you wayland for or1k ...06:55
poke53282well, almost. It compiles without problems, it runs, it reckognizes the framebuffer and the touch screen. It communicates a lot between server, client and compositor. A lot of applications can be started. But the screen remains black ... all the time. And I don't know why.06:55
hansfbaierpoke53282: Wow, you're really digging in!06:56
stekernpoke53282: your name was mentioned a numerous couple of times during the conference ;)06:59
poke53282Yes, I expected something like this. The community is not big enough yet :-) . Unfortunately I could come. Mainly because it is too expensive to come from Vancouver07:00
poke53282s/could come/could not come/07:00
olofkpoke53282: Wayland? That's so cool. Porting hot applications like that is exactly what's needed to make more people interested07:01
stekernpoke53282: yes, I understand that, we missed you there still07:01
olofkpoke53282: Yeah, I can understand that. I've been thinking it would be great to somehow get sponsorship for things like that. We should check how to do that for next year07:01
poke53282olofk: As I said it works basically but the screen is still black. Let's see if I can manage it to run till the end of the week.07:01
poke53282stekern, olofk: Maybe I am back in living Europe next year.07:03
stekernwe were speaking about potentially having it munich next year07:03
poke53282Oh, that would be very easy for me.07:04
stekern...and wayland, way cool! =)07:04
poke53282I have to say that I like wayland much more than X11. The source code by several orders of magnitude smaller and understandable.07:05
poke53282olofk,stekern: And I had to program and libffi implementation for  or1k. I will put in on github these days.07:07
stekernah, that's great! I would have needed that for something else some time (but I can't for my life remember what now)07:08
stekernhmm, I don't think that was it07:09
stekernit could have been when I tried to compile irssi07:09
stekernit has pretty massive dependencies iirc07:10
poke53282stekern: Tomorrow you can tell me about the decisions about the ABI. Now I have to go to bed.07:11
poke53282Already 12PM.07:11
stekernyeah, that's probably it, it depends on glib which depends on libffi07:11
poke53282And I need normally 8 hours ;)07:12
stekernsleep well!07:12
hansfbaierpoke53282: Yes, put it on git, maybe I can help a bit.07:14
olofklibffi is really cool too, even if it doesn't directly output pretty pictures on the screen. Should open up a lot of new possibilities07:18
olofkI'm thinking java (android?), python and stuff07:19
_franck_stekern: (transport): hopefully we catched that train I arrived quite shortly before the boarding07:46
_franck_and hopefully I didn't follow you to the South Terminal :)07:46
stekernyou mean "luckily"? ;)07:48
stekerndid it get tight to catch your flight?07:49
stekernobviously you made it ;)07:49
_franck_yeah I made it, I had a 15 min margin :)07:52
stekernthat's plenty07:53
stekernI even had time to buy some souvenirs/candy for the family07:53
jeremybennettgood morning all. Glad to hear you made it home07:55
_franck_good morning jeremybennett , we were lucky to get some support by phone to make it on time ;)07:58
Powermaniacgood morning07:59
jeremybennett_franck_: The power of modern communications07:59
jeremybennettPowermaniac: Good morning07:59
PowermaniacSo would you all say ORCONF2013 was a success?08:18
_franck_olofk: Warning: Failed to parse ../orpsoc-cores/cores/mor1kx-dev-env/mor1kx-dev-env.core: Could not find API type in ../orpsoc-cores/cores/mor1kx-dev-env/mor1kx-dev-env.core08:20
_franck_it that the new feature ?08:20
stekerncan't wait to test that "feature" out ;)08:38
olofk_franck_: But it still runs, right?10:10
olofkBecause mor1kx-dev-env doesn't have the API definition, so it should warn, but continue anyway10:11
stekernI just handed over the VGA patches to Richard10:25
olofkstekern: Cool. Has he responded?10:29
stekernwhen I wrote "just", I meant just. so, no ;)10:33
stekernI wouldn't have got it even if he had with the lag from gmails pop3 delay10:34
PowermaniacI'm going to assume you guys wouldn't recommend learning C without much programming knowledge in general, would you?11:08
PowermaniacAs ##programming sure isn;t11:08
hansfbaierPowermaniac: You could start with python11:09
hansfbaierPowermaniac: python is the visual basic of the linux world11:09
hansfbaierPowermaniac: And it is tremendously useful11:09
Powermaniachansfbaier: Yeah that is what I'm looking at now. In particular Learn Python The Hard Way.11:09
hansfbaierstekern: Would you mind pasting your kernel config? The 3.7 seems to be very different from the 3.9. I could take the 3.7 kernel that comes with altera, but as you said, that would break USB OTG11:11
stekernhansfbaier: oh, sorry, I forgot to mention, just run 'make socfpga_defconfig'11:13
hansfbaierstekern: thanks a lot11:13
hansfbaierstekern: I probably have to set CROSS_COMPILE="arm-linux-gnueabihf-" with the compiler from the ds-5, right?11:15
stekernand then make ARCH=arm11:15
hansfbaierstekern: OK, running11:15
hansfbaierstekern: But I probably need a dtb entry for vga_lcd, don't I?11:16
stekernmake ARCH=arm uImage, to be more precise11:16
hansfbaierstekern: thanks again11:16
stekernyes, and you ofcourse need to merge in the Kconfig too11:17
stekernand enable the driver11:17
hansfbaierstekern: already done using obj-y11:17
hansfbaierin the Makefile11:17
hansfbaierso shoudln't need Kconfig I suppose, or is fb disabled...?11:17
hansfbaier# CONFIG_FB is not set11:18
hansfbaieroh... ok11:18
stekernyeah, it has a couple of 'depends on'11:20
stekernerrr, select I meant11:21
stekernthat's the config I used, in case I did some additional changes I might have forgot about11:22
hansfbaierstekern: thanks a lot11:24
hansfbaier1stekern: drivers/video/ocfb.c: file not recognized: File format not recognized11:33
stekernwhat did you set obj-y to?11:35
stekernocb.o I hope11:35
_franck_olofk: yes, I still works, I just didn't let it finished the first time, I ctrl+c it just after seeing *Failed*11:38
_franck_sorry for the noise11:38
stekernhansfbaier: did you set obj-y to ocfb.o?11:39
stekernand not ocfb.c?11:39
hansfbaierstekern: so it was actually:  make ARCH=arm -j12 LOADADDR=0x00008000 uImage11:39
hansfbaierstekern: Yes :] stupid mistake.11:39
stekern(I've done that by mistake some time)11:39
hansfbaierstekern: Makefile habits11:39
hansfbaieruImage is done11:40
* hansfbaier drumroll............... try it11:40
stekernyes, you're right! I forgot about the LOADADDR... good that you found it out anyways11:40
hansfbaierstekern: hangs11:42
hansfbaierdidn't copy device tree yet11:42
stekernit has otherwise changed from 3.7, so you need that11:43
stekernregardless of the ocfb11:43
hansfbaierstekern: didn't program fpga too :]11:43
hansfbaierstekern: I need to copy it to the uboot partition too, right?11:44
hansfbaieras dtb11:44
stekernreminds me of another thing you'll need to know now when you already enabled the framebuffer11:44
stekernyou need to enable the hps2fpga bridge, it *should* be done by the kernel somehow (the "stock" 3.7 did that), but I haven't figured out how to enable it in the 3.9 kernel11:45
stekernso I just have done it manually in u-boot11:46
stekernwith: mw 0xffd0501c 411:47
stekernsee if you want to know what it means ;)11:52
stekernunder rstmgr->brgmodrst11:53
hansfbaierstekern: IT BOOTS11:55
stekernit's nice to be at that point, where you have a kernel you've compiled yourself that boots11:57
stekernany hacking beyond that is just increamental11:58
hansfbaierstekern: Ah stale dtb. Had to call make without uImage first12:03
hansfbaierstekern: reminds me of good old days transferring files with rz/sz12:06
stekernaah, yes. you can make the dtbs alone with 'make dtbs' too12:17
stekernthere's quite alot of info here that you might be interested of:
hansfbaierstekern: # find /proc/device-tree/ | grep ocfb12:20
stekerndo you get any output on the vga output too?12:22
hansfbaierstekern: Yes, black12:23
hansfbaier[    95.401] (EE) FBDEV(0): FBIOBLANK: Invalid argument12:23
stekernI get that too, it's "normal"12:24
hansfbaierstekern: Oh you mean on boot?12:24
hansfbaierstekern: It seems to hang there12:24
stekernisn't that when it tries to start X12:25
hansfbaierstekern: Yes, starting X12:25
hansfbaierwait a minute12:25
hansfbaierstekern: No penguin on VGA on boot.12:26
stekernto do it correctly, you should pass video=ocfb:640x480-32@60 on the kernel command line12:26
hansfbaierin uboot?12:27
stekernbut I think it should default to 640x480-16@60 if you don't specify anything12:27
stekernyes in uboot12:27
stekernbut X get the endian wrong with -16, so you should use -3212:27
stekernyou should still be able to see the distorted image with -1612:28
hansfbaiersetenv bootargs console=ttyS0,57600 video=ocfb:640x480-32@6012:28
stekern...and unfortunately it seems like the framebuffer can't keep up properly with -32, so you will experience some flickering...12:29
stekernbut I have some ideas how to hack around that12:29
hansfbaierstekern: still blank :|12:30
stekernyes, like that, but if you run the normal boot after that the bootargs will be overwritten12:30
stekernlook at the mmcboot command12:30
stekernso copy paste that into an 'fbboot' env var, add the video=.. and then run: run mmcload; run fbboot12:31
stekernor something equivalent ;)12:31
stekernyou can of course just modify the mmcboot command if you find that better12:32
hansfbaier1Enough for today. Many thanks, Stefan. Time for family home evening....12:38
poke53282stekern: Are there any news about the ABI?17:48
stekernpoke53282: we had a discussion about it, and the general opinion was being cautious about breaking the ABI and rather try to identify how widespread the problem is and try to notify the projects where it exists18:18
stekernI did point out the problems with detecting the problem, and how subtle the bugs are when you hit them18:18
stekernJörn Rennecke had some ideas about adding static code analyses for it in general gcc code, so a warning could be issued for call sites calling vararg functions with a static arg definition, but the conclusion for that was that it's not trivial18:22
stekernsince the compiler has no knowledge of how the called function actually was defined, there has to be support in the linker for it18:23
stekernthe discussion was video recorded and I promised to summarize it on the wiki, so we didn't come to a real decision about it18:25
poke53282Is the video available?18:38
poke53282static code analysis in gcc would be the best solution. And put that into -Wall that everyone reckognizes it. But I believe this was discussed a decade ago in gcc mailing list.18:40
stekernit's on the way I think, simoncook was our camera man, he'll probably need to split the videos up and upload them to youtube, but I'd expect he'll be working on that in a near future18:41
stekernpoke53282: really, do you have a link to that discussion?18:41
poke53282No, this is just a guess :)18:42
stekernheh, ok, where did the assumption come from? ;)18:42
poke53282But it is an understandable decision. Maybe the opinion would be different if everyone would have worked with the toolchain like I did.18:44
poke53282Well, the assumption comes from the fact that this is not ISO-C standard and the people would like to have this in -Wall.18:45
stekernI kind of would have wanted the to go the way with "soft deprecation" of the old ABI and support both, but that of course brings some uglyness to our gcc code18:45
stekernah, fair enough18:46
poke53282But it's a cast and a warning on a cast is something strange. A cast is very often a break of the rules in some way.18:46
stekernit doesn't even have to be a cast18:47
stekernif the definition is a vararg, but the declaration the caller see is static arg, it's just a normal function call18:48
poke53282At the moment I see also patches in uClibc and eglibc because of this behavior in the ABI. I found this a week ago:
stekernok, but that's "our" code18:48
stekernwe can't blame others for that ;)18:48
poke53282Yes, but we could get rid of some patches if we change the ABI. That is what I want to say with the link.18:49
poke53282Ok, have to leave for lunch.18:50
stekernah, now I see what that actually does. yeah, that wouldn't be necessary then18:51
stekernin the discussion someone made a point about performance regression, but in hindsight I think that was all wrong. using the changed abi would be a performance *win* I think.18:54
stekernperhaps not in the convoluted way gcc handles it though18:55
stekernsince wasn't the registers then copied out to the stack anyways18:55
stekern(I do realise you probably already left for lunch, but rely on that you also read the backlogs ;))18:56
_franck_stekern: how do you choose the pixel clock for the vga_lcd core ?19:42
poke53282stekern: Yes I read the backlogs. All together it is a performance win. But a very tiny one.19:52
poke53282Ok, if your whole program only consists of hundreds of varargs functions with three line of code in each of them then the performance win could be easily 50-80%. ;)19:55
poke53282By the way, the non-splitting of arguments accross registers and stack needs a special handling in libffi.19:57
poke53282Wow, this dejagnu is stuff is harder to cross-compiler then I think.  dejagnu needs expect which itself needs Tcl/Tk. And now I see an warning message "Expect can't be cross compiled". What the hell.20:20
stekern_franck_: the pixel clock is external to the vga_lcd core20:52
stekerni.e. you have to generate it yourself20:53
stekernon the sockit I have it hardcoded to 25.2 MHz (640x480@60)20:53
_franck_I know, but I think it is 25MHz for 640x480 @ 60Hz right ?20:53
stekernon the atlys I have a hack where I read out the hlen and vlen and program a pll according to that20:57
stekernjust so you don't think I'm crazy, I didn't do that by hand ;)20:59
stekern_franck_: so, did that answer your question? in sockit it's generated in clkgen.v21:08
_franck_yeah, my question was "is it 25MHz for 640x480 ?", so yes it is21:12
-!- knz_ is now known as knz21:43
_franck_stekern: what do you have just after that ?22:08
_franck_kernel prompt ?22:08
poke53282stekern: If you have a minute look at this:
poke53282the newest config.guess run on or1ksim.22:30
poke53282It does not recognize the build-system. Because it does not know the machine name "openrisc". config.sub seems Ok.22:32
poke53282All the time we were focused on config.sub. But to use configure natively config.guess seems to be important ant not config.sub.22:42
poke53282If there is no objection I can write a mail to  <> and to the mailing list.22:42
poke53282or to this one:
poke53282ok, we are not consistent here because config.sub behaves differently22:59
poke53282Current autoconf: "./config.sub openrisc" -> "or1k-unknown-coff"23:11
poke53282<- *confused*23:12
poke53282hansfbaier, stekern:
poke53282The starting point23:49
--- Log closed Tue Oct 08 00:00:30 2013

Generated by 2.15.2 by Marius Gedminas - find it at!