| --- Log opened Tue Oct 14 00:00:36 2014 | ||
| -!- Netsplit *.net <-> *.split quits: mithro, stekern, Amadiro, ams, trevorman, rokka, rhythmx, sfa, iorivur, fotis2 | 02:54 | |
| -!- mithro_ is now known as mithro | 02:54 | |
| -!- stekern_ is now known as stekern | 03:43 | |
| olofk | poke53282: I'll never forget your birthday now :) | 06:44 |
|---|---|---|
| olofk | My first programming stuff that I can remember was probably qbasic on a 486. I remember having a really hard time understanding for loops | 06:45 |
| wallento | hey guys | 07:37 |
| wallento | I took this one: http://openrisc.github.io/ | 07:37 |
| wallento | and forked it, updated the bootstrap, jekyll wondermagic | 07:38 |
| wallento | and tried to structure it more like a noob page | 07:38 |
| wallento | preview is here: http://wallento.github.io/openrisc.github.io/ | 07:38 |
| wallento | we need another logo (we did not buy it) plus I will now create the content | 07:38 |
| olofk | I didn't know we had openrisc.github.io :) | 07:42 |
| olofk | And I think a new logo would be good. Looking at it now, I don't like it very much | 07:42 |
| olofk | Or well, looking at it in the context on the url you pasted it looked quite good there | 07:43 |
| _franck__ | so a new website/fundation would only be OpenRISC ? Not cores ? | 07:43 |
| wallento | yeah, I am also not entirely sure about the logo | 07:43 |
| wallento | no, it will be cores | 07:43 |
| olofk | _franck_: Good point | 07:43 |
| wallento | but the openrisc landing page was really necessary now | 07:44 |
| olofk | Agree | 07:44 |
| wallento | even if only temporary | 07:44 |
| wallento | but its a shame.. | 07:44 |
| olofk | Don't forget to link to closedcisc.com as well | 07:44 |
| wallento | lol, never saw this before | 07:45 |
| olofk | :) | 07:45 |
| wallento | julius proposed a "call for logo" for two weeks and then a vote | 07:45 |
| olofk | Yeah, the call for logo was a good initiative, but it never got decided IIRC | 07:46 |
| wallento | maybe start it again, jungma also offered to create one | 07:47 |
| wallento | juliusb said maybe the ORCONF logo in an adapted way | 07:48 |
| olofk | Yeah, I like that one a lot | 07:48 |
| olofk | But it might be worth to see alternatives | 07:48 |
| wallento | there are a few requirements, I would definitely make mandatory: i) background needs to be transparent, ii) it needs a version that works on light and one that works on dark backgrounds, iii) for both it needs a large version (for documents etc.), a small version (like for the website navigation) and an icon | 07:50 |
| wallento | then we should be fine I suppose | 07:50 |
| olofk | Agree | 07:50 |
| olofk | And this probably means a few logos | 07:50 |
| wallento | we should maybe integrate your news with the landing page | 07:51 |
| olofk | news? | 07:52 |
| wallento | OpenRISC news/update mail | 07:52 |
| olofk | The stuff on my blog? | 07:52 |
| wallento | exactly | 07:52 |
| wallento | or just link there | 07:52 |
| olofk | Yes. We should integrate the OpenRISC-related stuff from there somehow, but maybe just as an additional resource, together with the stuff that _franck_ has written for example | 07:53 |
| olofk | And write short status updates on the main page instead | 07:54 |
| wallento | yes, as it is based on jekyll, everybody can blog, add news under his name easily | 07:54 |
| olofk | c00l | 07:54 |
| _franck__ | wallento: is there any plan to store cores from opencores somewhere else ? Like blueCmd started to do ? | 07:58 |
| wallento | yes | 07:58 |
| wallento | we agreed to start a preliminary board of contributors from OpenRISC that hopefully constitutes the next day | 07:59 |
| wallento | it definitely needs a new page, independent of how its called | 08:00 |
| wallento | but we also agreed it is not the repositories that really matter | 08:00 |
| wallento | but more the community stuff that should be in the focus | 08:00 |
| wallento | repositories can be github or whatever | 08:00 |
| _franck__ | I agree | 08:00 |
| wallento | the foundation will then establish a new site | 08:01 |
| wallento | and not a single person or company | 08:01 |
| olofk | stekern: I've tried to separate your wb_streamer_test to a driver and test application. I'm not very sure how the driver should be packaged though. Should I just have a .c and .h, or should I make an archive? | 09:01 |
| olofk | I guess this is a general question. How are bare-metal drivers normally handled? | 09:01 |
| wallento | some more updates: http://wallento.github.io/openrisc.github.io/ | 13:45 |
| wallento | I tried to put all main information on the front page and now we can start put more detailed information or an overview+links on the detail sites | 13:46 |
| wallento | plus a news post | 13:46 |
| wallento | quite simple to handle actually | 13:46 |
| wallento | i will continue and once I am completed and we have a logo ready, we can put it online, I propose | 13:47 |
| poke53282 | olofk: I did in QBasic on a 386 my first more serious programming steps. I figured also out, what a variable is during that time :) | 13:52 |
| maxpaln | wallento: looking good - already a very concise overview :-) | 14:12 |
| stekern | olofk: I don't think there's a standard way | 14:39 |
| juliusb | That is *so* much neater | 16:39 |
| stekern | I agree | 16:39 |
| stekern | and I vote for a variant of the orconf logo as the openrisc logo, I think that was neat | 16:40 |
| wallento | regarding the Downloads, what do you think should go there. i think the following things can go in there: links to the latest pre-built toolchain releases, a virtualbox image (including what?) | 16:47 |
| wallento | both can be pretty good automatized | 16:48 |
| poke53282 | Yes, the orconf logo looks nice. Also for jor1k I need another one. At the moment I use the opencores logo. | 17:13 |
| poke53282 | I would also suggest to add some toolchain, which uses the qemu user mode emulator. Something like https://github.com/s-macke/jor1k/wiki/How-to-develop-for-jor1k#chroot-into-an-emulated-sysroot-environment | 17:14 |
| poke53282 | This are just a few lines and you compile directly in an OpenRISC machine. | 17:15 |
| wallento | sounds good | 17:48 |
| -!- rhythmx_ is now known as rhythmx | 18:41 | |
| olofk | wallento: Latest tar ball of FuseSoC could go there too | 18:49 |
| olofk | oh.. and pre-built FPGA images | 18:56 |
| juliusb | downloads of virtualbox images are very very useful. pre-built tool chains are tricky, right? there's so many platforms to cover, maybe geting it apt-get-able is the target there? | 22:34 |
| juliusb | I think for the logo I would still like to open it up for some more to be considered before deciding | 22:35 |
| imphil | juliusb, pre-built toolchains are very doable, essentially only a linux64 and linux32 version is required | 22:57 |
| imphil | juliusb, example of the linaro toolchain for arm: http://releases.linaro.org/14.08/components/toolchain/gcc-linaro/4.9 | 23:00 |
| imphil | juliusb, I'm working on a automated way of creating a virtual box image including the toolchain using packer, that works rather well at least for the open source components. including things like systemc and vendor tools is unfortunately not possible, and we'll provide wrapper scripts for easier installation instead | 23:02 |
| --- Log closed Wed Oct 15 00:00:38 2014 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!