--- Log opened Fri Mar 21 00:00:29 2014 | ||
analognoise | So what's stopping the movement to a new portal? | 00:09 |
---|---|---|
blueCmd | analognoise: http://bob.cmd.nu:8080/ | 00:11 |
blueCmd | analognoise: nobody doing it :P | 00:11 |
blueCmd | http://bob.cmd.nu:8080/ - yeah, I just forked archweb and played some with the colors | 00:44 |
blueCmd | might work | 00:44 |
blueCmd | something is weird with IPC in either 1) or1k with qemu or 2) glibc. (or more, but I think those are the most probable) | 01:31 |
blueCmd | fakeroot-sysv just hangs, fakeroot-tcp seems to work though | 01:31 |
stekern | blueCmd: what's IPC? | 03:47 |
stekern | I'm guessing inter-process communication in this context | 03:53 |
stekern | I *really* hate theater of the living arts | 03:54 |
analognoise | ERROR: Failed to run the simulation. | 03:58 |
analognoise | Failed to run Icarus Simulation | 03:58 |
stekern | sounds like failure | 04:02 |
analognoise | ERROR: Can't find core 'wb_bfm' | 04:03 |
analognoise | Yeah | 04:03 |
analognoise | Having a hell of a time :) | 04:03 |
stekern | give me some more context and I might be able to help | 04:03 |
stekern | blueCmd: (reading backlog about portal) I agree about a new portal. But, the last effort to do that (opernisc.net) ended in a big fight and the idiocy of having several mailing lists are a result of that | 04:10 |
stekern | s/opernisc.net/openrisc.net | 04:11 |
analognoise | I would give you more context, but I'm not at all sure where the error(s) ile | 04:34 |
analognoise | *lie | 04:34 |
analognoise | For some reason it installed on my other machine just fine | 04:34 |
analognoise | They're both running Crunchbang (Debian based) in Virtual machines | 04:35 |
stekern | more context could be: what you actually are doing (reading the backlog I saw running fusesoc/orpsoc-cores and the wb_bfm gave that away) and/or paste the command you are trying to run + the output | 04:40 |
analognoise | I'm trying to run the example to check the installation (fusesoc sim wb_bfm) | 04:46 |
analognoise | analognoise@crunchbang:~$ fusesoc sim wb_bfm | 04:46 |
analognoise | ERROR: Can't find core 'wb_bfm' | 04:46 |
stekern | did you add a fusesoc.conf file to your build directory? | 04:55 |
stekern | (and I see you are trying to run it in your home dir, you might not want to do that) | 04:55 |
stekern | fusesoc.conf should contain something like this: | 04:58 |
stekern | [main] | 04:58 |
stekern | cores_root =../orpsoc-cores/cores | 04:58 |
stekern | systems_root =../orpsoc-cores/systems | 04:58 |
analognoise | Ah, but if I cloned from github and did the autoreconf -i... | 04:59 |
analognoise | I was just following the steps | 04:59 |
analognoise | Should I have done it differently if I cloned from Git? | 05:00 |
stekern | the 'autoreconf -i' is related to the ./configure step | 05:00 |
stekern | the fusesoc.conf is related to running the installed fusesoc | 05:00 |
stekern | so, no, your installation is fine | 05:01 |
stekern | you just have to setup your 'runtime' environment correctly now | 05:01 |
analognoise | I have fusesoc.conf in ~/ | 05:01 |
stekern | even though that works, I would advise to run it in a seperate directory | 05:02 |
stekern | because it will scatter some files in there | 05:02 |
stekern | if you don't care polluting your home dir, it doesn't matter though | 05:02 |
stekern | +about | 05:03 |
stekern | so... with the fusesoc.conf and similar lines to what I pasted in it, does it still give the error? | 05:04 |
analognoise | ERROR: Error: Failed to register cores root | 05:05 |
analognoise | ERROR: ../orpsoc-cores/cores is not a directory | 05:05 |
stekern | mmm... *similar* | 05:06 |
stekern | you don't have orpsoc-cores in /home/orpsoc-cores, do you? | 05:06 |
analognoise | yup | 05:29 |
trsohmers | Greetings | 05:33 |
analognoise | howdy | 05:56 |
trsohmers | I'm new to the OpenRISC project, so what is the status of the ASIC hardware implementation? | 06:10 |
trsohmers | and hi analognoise | 06:13 |
stekern | trsohmers: if you refer to the donation project started by orsoc, it's pretty much stalled | 06:20 |
trsohmers | stekern: Yea I noticed. So is the majority of the costs just to get into a fab house? | 06:20 |
stekern | I'm not betting any money on it ever being unstalled neither | 06:20 |
stekern | if you mean fabrication costs by "get into a fab house", then yes | 06:22 |
stekern | the designs already exists | 06:23 |
trsohmers | Have you looked into alternative fabrication techniques? | 06:23 |
stekern | alternative to what? as far as I know, all techniques are expensive | 06:24 |
stekern | but I'm no expert in ASIC fabrication | 06:25 |
trsohmers | So I have not had experience with IC fabrication, but I have worked with electron beam lithography for MEMs systems | 06:25 |
trsohmers | it is shit slow in comparison to any photolithography technology, but you can (slowly) dry etch a wafer with transistors | 06:26 |
trsohmers | Do you know who was involved in the ASIC project, and what they had synthesized? | 06:27 |
stekern | I don't, and I think it only got to the stage of begging for money | 06:28 |
trsohmers | Any idea how to find out? I'm not really knowledgable on the HDL and design side, but I'm familiar with semiconductor fab | 06:29 |
trsohmers | basically, if I have a GDSII file, I can fab anything down to ~6nm | 06:32 |
trsohmers | but yield would be shit at that resolution, so it would probably be more effective at ~22-28nm | 06:33 |
stekern | you probably have a better chance getting HDL coders among the active people in this channel that are interested in collaborating with you | 06:34 |
trsohmers | Should I hang around here, or is there a better place/person I can look at/talk to? | 06:35 |
stekern | hang around here, all the core openrisc devs are here | 06:36 |
analognoise | Yeah and I've gotten my questions answered. It's actually pretty awesome. (Just chiming in) | 06:37 |
analognoise | Although I'm not sure wtf is the problem right now :) | 06:37 |
stekern | and there are the mailing lists, for more elaborate questions and ideas: http://opencores.org/or1k/OR1K:Community_Portal#Mailing_lists | 06:38 |
trsohmers | I don't have a copy of any Cadence or other EDA software that to my understanding would generate the GDSII files, so I'm wondering if the ASIC people got to that stage | 06:39 |
analognoise | Electric VLSI can do that, and it's free | 06:39 |
analognoise | That'd be a hell of a layout project | 06:40 |
analognoise | But the parameter extraction would be questionable at advanced nodes | 06:40 |
analognoise | There's no reason to go to advanced nodes for something this size though - save money, older process. | 06:40 |
trsohmers | Well, the same machine can do anything down to 6nm | 06:41 |
trsohmers | I have free (within reason when it comes to amount of time) access to the ebeam machine | 06:41 |
trsohmers | but using a larger process would cut down on the time it takes to etch significantly | 06:42 |
analognoise | There's a reason production chip manufacturing isn't at 6nm yet. A slew of them, actually. | 06:43 |
stekern | trsohmers: another problem is that the fabs have their own logic libraries, which they charge money for | 06:43 |
stekern | like RAMs and such | 06:43 |
analognoise | Logic libraries and, more importantly, verified models of their process. | 06:43 |
analognoise | That's really what you're paying for. | 06:43 |
stekern | yes, that too | 06:43 |
analognoise | Any dope can lay out a 6T register cell and pattern it. But how does that nice layout actually look on the process you're going to spend 1-2 million dollars for one run doing? | 06:45 |
analognoise | Unless you do a multi project wafer | 06:45 |
analognoise | Which I've thought is a better place to start | 06:45 |
analognoise | But it's still a little pricey for an individual. | 06:45 |
trsohmers | The major part of fabrication is the lithography step, which I've done in other scenarios (not IC fab) | 06:46 |
trsohmers | The most expensive actual cost for the fab using photolithography is the creation of the masks, and maintenance for the optical equipment | 06:47 |
trsohmers | Doing direct etching is a significant time increase, but if you are doing a very small run, it's relatively easy | 06:48 |
trsohmers | At least from my understanding | 06:48 |
analognoise | I don't know if there are published layouts for the OR1K designs. That'd be interesting... | 06:49 |
trsohmers | I haven't found any, so I came here to see if anyone knew about anything | 06:50 |
analognoise | Well it'd be a hell of a lot of fun to build them. | 06:53 |
analognoise | That's for sure. | 06:53 |
analognoise | Your process will determine what types of blocks you can build, then your parasitic extraction will tell you how the device should actually be performing | 06:53 |
analognoise | We'd have to work out a clock tree and all that jazz without fancy tools | 06:54 |
analognoise | Brutal | 06:54 |
analognoise | Sounds...kickass. | 06:54 |
stekern | =) | 06:54 |
analognoise | I'm down. Anyone else? | 06:55 |
trsohmers | I'm not sure how much I can help on that side of things, but I would love to learn along the way | 06:55 |
trsohmers | But I'm obviously up for it on the fabrication side | 06:56 |
analognoise | I love analog shit (it doesn't get more brutal than that) but I make my bread with HDL. I've only been seriously considering OR1K for a production design for a short period of time, but I like the way it ties things together so far (when it works - it's fine on my other machine, damn it) | 06:58 |
analognoise | I'd say go for something like the AK-47 of designs - not cutting edge at all, but very cheap and effective. As a proof of concept. Also badassery. | 06:59 |
stekern | I'd be the first to agree on that | 07:01 |
trsohmers | From what it seems like, whoever was working on this OR1K ASIC didn't publish much of anything | 07:01 |
trsohmers | So I guess this should be the OpenOpenRISC ASIC? ;) | 07:01 |
analognoise | Full custom ASICs are...fucking hard. They might have just gotten overwhelmed. | 07:02 |
trsohmers | Most likely. I was secretly hoping they got a lot of the design finished and just couldn't get to fab | 07:03 |
analognoise | Hmm... | 07:03 |
trsohmers | I suppose the likelyhood of that is slim, as nothing seems to have been released | 07:04 |
analognoise | I'd agree | 07:07 |
analognoise | I see fusesoc.conf in the fusesoc main folder - is it also being copied somewhere else & then referenced? | 07:12 |
trsohmers | orpsoc is now fusesoc? | 07:14 |
trsohmers | olofk: Ping | 07:16 |
analognoise | Alright yall I gotta pass out | 07:18 |
analognoise | I'll catch everyone tomorrow | 07:18 |
analognoise | cheers | 07:18 |
_franck_web_ | trsohmers: yes, orpsocv3 is now fusesoc | 08:16 |
trsohmers | Hi _franck_web_ | 08:17 |
trsohmers | Yea... are you knowledgable of any attempts to make a OpenRISC ASIC? | 08:18 |
_franck_web_ | not at all | 08:19 |
trsohmers | or know anyone in here that does | 08:22 |
_franck_web_ | sorry no | 08:23 |
jungma | stekern: i tried it again, configure: error: no usable dependency style found | 08:54 |
stekern | jungma: ok, but at what stage does that happen? | 09:07 |
stekern | another hour wasted on connecting a reset signal with wrong polarity | 09:48 |
jungma | stekern: at the stage "Build gcc" | 09:57 |
stekern | jungma: could you post the config.log somewhere? | 10:02 |
jungma | stekern: http://nopaste.info/1545a8d73a.html | 10:34 |
_franck_web_ | ../or1k-gcc/configure: line 4808: g++: command not found | 10:41 |
stekern | yes, you'll need that | 10:41 |
jungma | yes, i discoverd that also, so the dependecy list should be updatet | 10:41 |
jungma | for centos it is gcc-c++ | 10:42 |
jungma | not g++ | 10:42 |
jungma | different package name | 10:42 |
stekern | ok, feel free to add a note on the wiki, somewhere around the other dependencies | 10:42 |
_franck_web_ | I'm using a centos right now and I have g++ in my PATH | 10:43 |
_franck_web_ | which version do you have ? | 10:43 |
jungma | its only the package name | 10:43 |
jungma | the executable is still named g++ | 10:44 |
_franck_web_ | ah sorry :) | 10:44 |
jungma | and it is necessary to run this: | 10:44 |
stekern | I think the dependency list stems from the time when gcc wasn't built with g++ | 10:44 |
jungma | cd ../or1k-gcc | 10:44 |
jungma | ./contrib/download_prerequisites | 10:44 |
jungma | I have a new list now... i will post it later into the wiki | 10:45 |
blueCmd | stekern: yes, IPC. stekern: ah I see (re: portal) | 11:01 |
blueCmd | wow https://wiki.debian.org/FPGA is really bad :) | 11:04 |
blueCmd | A guy emailed me and asked me to fix it | 11:04 |
jungma | :D | 11:06 |
blueCmd | jeremy_bennett: you spoke that you will have some time to dedicate to GCC. I'm very much interested in upstreaming it as well, so any help you can give in the effort would be appriciated. I don't know if olofk is up for another scan of the revision systems, but that would be super helpful. | 11:07 |
jeremy_bennett | blueCmd: It won't be me, it will be a new member of staff who joins us at the end of June. | 11:21 |
jeremy_bennett | He'll be able to support you then. Thanks for your work on this. | 11:22 |
blueCmd | jeremy_bennett: yes, I didn't mean you in person :) that's great! | 11:48 |
blueCmd | jeremy_bennett: so, I emailed you about this but maybe it got lost - now when binutils is heading upstream containing o1knd references, would you consider it to be included for upstream config.guess/config.sub? | 11:53 |
blueCmd | stekern: olofk: my board designer wants a name for the board de0_something - I'm thinking de0_orpsoc but, is it named orpsoc? or fusesoc? | 11:56 |
blueCmd | or is just fusesoc the builder? | 11:56 |
stekern | yes, fusesoc is just the builder | 12:56 |
stekern | I think that orpsoc-cores fits more into what is orpsoc | 12:59 |
stekern | and if you want to take the name literally (Openrisc Reference Platfrom System On Chip), what are here is the core of orpsoc: https://github.com/openrisc/orpsoc-cores/tree/master/systems | 13:01 |
maxpaln | Hi, been a busy few weeks so no chance to check-in | 13:24 |
_franck_web_ | hi, good to see you | 13:25 |
stekern | maxpaln: wb | 13:26 |
maxpaln | Things are progressing very well though - the memory controller is pretty much done (I've had precious little time to test it in HW but simulation testing is pretty much done) and I am nearing completion on everything else | 13:26 |
maxpaln | :-) | 13:26 |
maxpaln | thanks | 13:26 |
maxpaln | I have a question though - slightly out of the ordinary | 13:26 |
maxpaln | my boss has asked me to do a short presentation to the other FAEs on the ORPSOC platform on Monday | 13:26 |
maxpaln | I have (traditionally) left it to the last minute to do the prep | 13:27 |
maxpaln | I wondered if there is any sharable PPT material with general overview content that I could include | 13:27 |
_franck_web_ | juliusb_ might have this | 13:28 |
_franck_web_ | and it should be online somewhere | 13:28 |
maxpaln | otherwise, I hope the vacation went well - you must have only just returned if my memory serves me well | 13:28 |
maxpaln | _franck_web_ - great, I'll see if I can find it | 13:28 |
_franck_web_ | stekern went in vacation far away :) | 13:29 |
_franck_web_ | https://www.dropbox.com/s/bybyk5h8riju77f/julius-baxter-open-chip-design.pdf | 13:30 |
_franck_web_ | https://www.dropbox.com/s/vtwn4kx18kkexa8/presentation.pdf | 13:30 |
_franck_web_ | (I just did a search with "dropbox" on the IRC logs) | 13:31 |
maxpaln | :-) great - nice idea, I'll have a look at that | 13:31 |
stekern | then there's probably the orpsocv3/fusesoc/orpsoc-cores slides from this http://www.youtube.com/watch?v=W3-fUkrdR1M&feature=youtu.be | 13:31 |
stekern | if you ask olofk about them | 13:32 |
maxpaln | ...more good suggestions. olofk: do you have any slides you think could be relevant? Top level stuff is fine | 13:33 |
maxpaln | FWIW does anyone have a meaningful or otherwise metric of performance for the latest iteration of the ORSOC that I can include in material I am presenting on Monday? | 15:35 |
blueCmd | maxpaln: It's 500 times slower on 'openssl bench' than my i5 laptop :) | 15:38 |
blueCmd | A very scientfic statement | 15:38 |
maxpaln | I'm having that one :-) | 15:38 |
blueCmd | that's 50 MHz, mor1kx, de0_nano ($79) | 15:39 |
maxpaln | can I have more detail on the i5 spec too please ;-) | 15:39 |
blueCmd | sure, let me boot it up | 15:40 |
maxpaln | only kidding - although 500 times slower for something that is probably running at 1/500th the clock rate is not bad | 15:41 |
maxpaln | ooops, bad maths - 1/50th the clock rate | 15:42 |
maxpaln | worse, but still pretty impressive | 15:42 |
maxpaln | especially if you have several cores running on the i5! | 15:42 |
blueCmd | it's 2.6 GHz, i5 3320M | 15:42 |
blueCmd | but it's not very scientificly done | 15:42 |
maxpaln | LOL - I might still include it to see if everyone is awake! | 15:43 |
blueCmd | I just ran the same thing on my laptop and the or1k thing | 15:43 |
blueCmd | 500 times slower is quite good. We don't have any optimized assembler in openssl (as x86_64 does), atomic operations are done via expensive syscalls (shouldn't matter much since it's single threaded, but still) and the CPU is not doing out of order execution | 15:44 |
maxpaln | agreed - plus Intel have quite a few engineers working on theirs! | 15:45 |
blueCmd | stekern: crack-md5_5.0a-9.3_or1k.deb - now we can do fun stuff! | 15:48 |
blueCmd | printer-driver-cjet_0.8.9-5_or1k.deb | 16:15 |
blueCmd | that will be useful | 16:15 |
stekern | ah, yes, crack = fun, that I've heard. Especially when combined with pipes | 16:20 |
blueCmd | and printer drivers | 16:21 |
stekern | combining crack with printer drivers, that I haven't heard of, but I guess anything goes when it comes to drugs | 16:22 |
stekern | ah, now I get it: https://www.youtube.com/watch?v=6NaJw2-PqLQ | 16:24 |
stekern | maxpaln: you could quote a coremark score of 88 for mor1kx @50MHz on de0 nano | 16:26 |
blueCmd | so what I'm doing is building all debian packages, the first pass (the ones that do not depend on anything but essential) | 16:29 |
blueCmd | which means we now have 'cdbackup' available | 16:29 |
maxpaln | stekern: thanks | 16:30 |
blueCmd | for all your FPGA-based backup needs | 16:30 |
stekern | that's cool, and reminds me that I should test it on real hw | 16:41 |
stekern | perhaps hacking together some ise support to fusesoc and an atlys port is next on the agenda to fulfill that | 16:42 |
analognoise | howdy all. | 16:46 |
blueCmd | analognoise: hello! | 17:03 |
blueCmd | stekern: that would be awesome :) | 17:04 |
blueCmd | analognoise: what are you up to? any cool ideas your hacking on? | 17:09 |
analognoise | blueCmd:Too many projects, never enough time. :) I'm verifying the datapath for a space program currently, so I beat my face against Verilog all day. I want to get conversant with the Openrisc materials so I can use it as an embedded soft processor, then I'd like to see if we can get some movement to lay one out. | 17:17 |
blueCmd | space! space is cool :) | 17:17 |
analognoise | Space is pretty cool, but it is weak from a technology standpoint. hahaha | 17:18 |
analognoise | Unless you're doing radio/satellite comm stuff, which is intense. | 17:18 |
analognoise | We use the absolute LATEST in 1990's technology. | 17:19 |
analognoise | What about you? | 17:19 |
blueCmd | haha | 17:28 |
blueCmd | I'm currently building all debian packages. | 17:28 |
analognoise | That's awesome! I have no bloody clue how to do that | 17:29 |
analognoise | That'll really get the work out there | 17:30 |
analognoise | So you're doing these for openrisc? Any way I could help? | 17:35 |
blueCmd | analognoise: well, my build server is doing that | 17:37 |
blueCmd | it's just a slow process really | 17:37 |
blueCmd | but I appriciate your offer. I'll let you know if I think of anything | 17:37 |
analognoise | No worries | 17:39 |
trsohmers | Goodmorning folks | 19:45 |
trsohmers | hey analognoise | 19:45 |
trsohmers | olofk: Are you here? | 19:51 |
trsohmers | or jeremy_bennett | 19:57 |
trsohmers | juliusb_: Are you Julius Baxter? | 19:57 |
blueCmd | trsohmers: yes, he is :) | 19:59 |
trsohmers | Just found a powerpoint by Julius and Jeremy about the process of making an OpenRISC ASIC | 19:59 |
trsohmers | blueCmd: Do you know anything about the OpenRISC ASIC development? | 20:02 |
blueCmd | trsohmers: well, I know there is none - sadly | 20:04 |
stekern | well, there are several ASICs with openrisc implementations on them. None that are community driven nor "open" though. | 20:13 |
trsohmers | Are they all corporate/for profit projects? | 20:16 |
analognoise | It's time we change that. | 20:21 |
trsohmers | :) | 20:22 |
blueCmd | analognoise: well, sure - we just need cadence / mentor to sponsor the utilites and a fab to do the same - or kickstart something | 20:34 |
blueCmd | still, it would probably need a lot of work to make or1k worth doing an ASIC of. just putting it on the chip and hope the performance would increase enoguh to make it worth doesn't seem to be a good idea to me :) | 20:35 |
stekern | trsohmers: there's an openrisc processor on allwinner a31 SoCs, a couple of MP3 chips uses openrisc, it has been featured in samsungs DTV SoCs and some more | 20:36 |
stekern | all corporate projects, where they presumably needed an embedded processor | 20:37 |
blueCmd | stekern: it would be weird if they didn't | 20:37 |
stekern | yes M) | 20:37 |
blueCmd | "Oh, so why do we have this OpenRISC thing here?" | 20:37 |
stekern | ;) | 20:37 |
blueCmd | "I don't know, I thought you needed it!" | 20:38 |
stekern | you never know in the corporate world ;) | 20:38 |
blueCmd | indeed | 20:38 |
blueCmd | debian has a _lot_ of weird packages | 20:38 |
blueCmd | I just built jpnevulator - god knows what it does | 20:39 |
stekern | a thing or two lost in the translation in a multinational company, and anything can happen ;) | 20:39 |
blueCmd | "Minimize risk?" "Yes, yes, openrisc!" | 20:39 |
stekern | exactly! | 20:40 |
trsohmers | blueCmd: Well, I can probably help on the fab end | 20:44 |
blueCmd | cool! trsohmers: what do you do? | 20:44 |
trsohmers | I've done some work on MEMS fabrication using direct etching tech... Electron beam and focused ion beam primarily | 20:45 |
trsohmers | the electron beam lithography machine I have access to can technically etch feature sizes as small as 6nm | 20:46 |
blueCmd | hah, that's cool :) | 20:52 |
blueCmd | I've only done full custom stuff for 350nm | 20:53 |
trsohmers | transistors have been made as small as 9nm on this machine, but not with good yield AFAIK | 20:54 |
trsohmers | So the smallest realistic run with good yield would be around 22nm, and it would take forever to make (E beam is very very *very* slow compared to photolithography) | 20:55 |
trsohmers | but you wouldn't have to have every layer done on the ebeam... only the smallest feature layers | 20:56 |
trsohmers | it would probably still take a full work day at least to do a 8 inch wafer thoug | 20:56 |
trsohmers | h | 20:56 |
analognoise | blueCmd: We could use Electric VLSI. | 21:01 |
analognoise | Although if we were serious, we'd have to sign NDAs for some process, which can really only be done as a corporate entity. For volume production. | 21:01 |
trsohmers | for volume, yes. but a wafer a day with a small enough die size isn't horrible | 21:02 |
analognoise | For a multi-project wafer at MOSIS there might be a set of files available | 21:02 |
analognoise | It is if you're paying for electricity for an ebeam machine... | 21:03 |
analognoise | I think doing the layout/simulation and then trying to get kickstarter backing on a MOSIS run might be the best option. | 21:04 |
trsohmers | Luckily I am not paying anything for the ebeam machine, as long as I am not taking up a ridiculous amount of time on it | 21:04 |
trsohmers | I could technically buy out time on it for ~$10k a month, but I wouldn't be able to use it for production runs (only prototyping) | 21:05 |
analognoise | So we'd have to get a corporate account to get into MOSIS | 21:07 |
analognoise | Might want to set up a coprorate entity for that. | 21:08 |
analognoise | Bah...getting off the topic of openrisc. | 21:08 |
analognoise | Ok | 22:20 |
analognoise | Trying to explain IC layout to people in #electronics | 22:20 |
analognoise | I still think this is worth doing. | 22:20 |
blueCmd | stekern: http://storage.googleapis.com/bluecmd-openrisc/i.png - let me know if you want us to build one for you :) | 23:45 |
--- Log closed Sat Mar 22 00:00:31 2014 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!