| --- Log opened Tue Mar 01 00:00:53 2016 | ||
| mithro | Heyo! | 00:44 |
|---|---|---|
| mithro | TimVideos got into GSoC too, and we are very interested in what is happening around or1k / openrisc stuff | 00:45 |
| mithro | Our current HDMI2USB firmware uses the lm32 architecture because it had better upstream GCC+BinUtils support, I was wondering how that was going for or1k? | 00:45 |
| mithro | I'm wondering if there is a way for us to collaborate in GSoC too | 00:55 |
| mafm | mithro: probably most people in this channel will be asleep at this time | 00:57 |
| mithro | mafm: I assume people will read the channel backlog? | 00:57 |
| mafm | wallento is the one organising the gsoc for openrisc | 00:57 |
| mithro | wallento: See my comments above. If I'm not around, feel free to contact me at [email protected] or jump on the #timvideos IRC channel | 00:58 |
| mafm | mithro: presumably, but just informing you if you want to chat to them in real time | 00:58 |
| mafm | :) | 00:58 |
| mithro | that reminds me, I still have that partially written bot which syncronized the data from opencores to the freecores github repo. I seem to remember that some of the developers here were involved in setting that up.... | 00:59 |
| mithro | I can probably organise things like Opsis boards (https://www.crowdsupply.com/numato-lab/opsis) for doing or1k work on if they suitible overlap with our goals too. | 01:02 |
| wallento | hi mithro: cool, sounds great | 08:49 |
| wallento | we are very interested in cooperating, I will also drop you a mail | 08:50 |
| mithro | wallento: so, lowRISC and FOSSi are both some way related to or1k ? | 08:50 |
| wallento | lowRISC not | 08:50 |
| wallento | lowRISC is solely based on risc-v | 08:50 |
| wallento | but there is an overlap in the communitis | 08:51 |
| wallento | and the overall goal is the same (FOSSi) | 08:51 |
| mithro | risc-v is another "open risc instruction set"? | 08:51 |
| mithro | It's been a while since I've looked into all this stuff | 08:51 |
| wallento | it seems to become _the_ open ISA | 08:51 |
| wallento | they have a lot of traction and (financial) support | 08:52 |
| wallento | but I still see a place for the OpenRISC community, especially the community part is much different | 08:52 |
| wallento | but we for example have dropped our ambitions for an or2k ISA | 08:53 |
| mithro | btw - Is or1k support in upstream gcc/binutils yet? | 08:55 |
| wallento | binutils yes | 08:55 |
| wallento | gcc no | 08:55 |
| mithro | wallento: Any idea if that is still progressing / likely to eventually happen? | 08:56 |
| wallento | we have a problem with copyright assignments | 08:56 |
| wallento | it is still a topic, but not progressing | 08:56 |
| wallento | one escape plan we have is to get a GSoC student that starts from scratch | 08:57 |
| wallento | so if you happen to know someone masochistic ;) | 08:57 |
| mithro | ha :) | 09:00 |
| mithro | We are using the lm32 in our HDMI2USB firmware mainly because of the upstream gcc support | 09:01 |
| mithro | Does RISC-V have gcc upstream support? | 09:02 |
| wallento | not yet, but they have the advantage that they are at the start | 09:03 |
| wallento | so everyone is around and has already submitted is, but I don't track this stuff closely | 09:03 |
| --- Log closed Tue Mar 01 19:04:33 2016 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!