| --- Log opened Fri Feb 19 04:11:44 2016 | ||
| -!- Irssi: #openrisc: Total of 44 nicks [0 ops, 0 halfops, 0 voices, 44 normal] | 04:11 | |
| -!- Irssi: Join to #openrisc was synced in 16 secs | 04:11 | |
| wallento | hi all | 10:14 |
|---|---|---|
| wallento | anyone has an interesting project idea as a summer of code project? | 10:15 |
| wallento | we are applying as FOSSi Foundation, mainly around OpenRISC and any ideas that can fit a three month period are welcome | 10:16 |
| mafm | wallento: were you selected as orga? | 10:51 |
| wallento | no, we prepare the application | 10:52 |
| wallento | and put up a preliminary list | 10:53 |
| wallento | so if you have an idea it does not need to be fully elaborated | 10:53 |
| mafm | not really, I am not very involved with openrisc nowadays (I was with the Debian port) | 10:54 |
| mafm | just asking because somebody was asking yesterday to the lowRISC project if they had applied to GSoC as orga | 10:55 |
| mafm | I don't know if FOSSi includes lowrisc nowadays? | 10:55 |
| wallento | no, they are complementary | 10:55 |
| wallento | lowrisc included many more generic projects | 10:56 |
| wallento | and sponsored extra projects | 10:56 |
| mafm | the Debian port would be a good project idea for GSoC, if GCC was upstreamed -- there were people accepted in previous years to work on the port of mips64el, for example | 10:56 |
| wallento | so stuff like fusesoc can better be done under the FOSSi umbrella we think | 10:56 |
| wallento | GCC upstream is a mandatory, right? Problem is we do not progress on this part unfortunately | 10:57 |
| mafm | yeah, I know :( | 10:57 |
| mafm | IIRC gsoc projects for lowrisc accepted were porting seL4 to risc-v or similar | 10:58 |
| mafm | maybe that with openrisc? | 10:58 |
| wallento | yeah, I mentored the seL4 port | 10:59 |
| wallento | will put it up for OpenRISC this year :) | 10:59 |
| wallento | we will also continue with that for lowRISC | 11:00 |
| wallento | Maybe poke53281 wants to do another fast simulator :) | 11:01 |
| wallento | is there anything in the Linux part that needs to be done | 11:01 |
| wallento | I unfortunately lost track of this | 11:01 |
| mafm | I think that it was poke53281 the one asking about this yesterday for lowrisc, BTW, but maybe I mistake the number X) | 11:04 |
| mafm | GCC support for openrisc (e.g. a clean reimplementation from scratch, to get rid of the copyright assignment problems -- if the person agrees to it from the start) would be a possibility for a project, but maybe too hard for 3 months and students jumping into the boat | 11:06 |
| mafm | if you want openrisc to continue to go ahead and be useful, I think that GCC is quite important to have (LLVM is another possibility nowadays, but still) | 11:07 |
| mafm | s/I think/I guess/ -- you'll know better than me :-) | 11:07 |
| mafm | I guess that keeping the support of {binutils,glibc,gcc,linux,qemu}, either upstreamed or in unmerged ports (but working with recent versions of upstream) is good to have, if one wants to get good support in the Linux ecosystem | 11:10 |
| wallento | yep, agree | 11:11 |
| wallento | a clean GCC implementation is probably too much for a student in 3 months | 11:11 |
| wallento | especially as we need to keep them away from the current code.. | 11:11 |
| mafm | I was wondering if they could reuse or inspire themselves in similar implementations, like risc-v? | 11:14 |
| mafm | wallento: in theory, if risc-v is a clean-room implementation (not based on MIPS or others, so they own the copyright and don't owe anything to any other implementation), and they release their part with the BSD license (it's Berkeley, after all) or GPL (the code will be GPL when added to GCC upstream), maybe the GCC support for openrisc would just need to be modified | 11:18 |
| wallento | nice idea, MIPS is probably the easiest | 11:18 |
| wallento | mmh, okay | 11:18 |
| mafm | I am not a lawyer! :D | 11:19 |
| wallento | is there any problem with deriving from the MIPS port? | 11:19 |
| mafm | maybe patents? | 11:19 |
| wallento | But RISC-V is also fine | 11:19 |
| mafm | I am not 100% sure how these things work in practice | 11:20 |
| wallento | I think someone from the compiler guys needs to pick it up as a mentor as the student must be a really good one to do this task | 11:20 |
| wallento | I have some basic knowledge of compilers, but of no help in this :) | 11:20 |
| simoncook | I would imagine if starting a new GCC backend, deriving from one that is already upstream would work best, because FSF already have the copyright on that? | 11:20 |
| wallento | yes, that makes sense | 11:21 |
| mafm | hmmm, yes, makes sense, I just don't know if there's some kind of catch that might be problematic | 11:23 |
| mafm | but I guess that with GCC being GPLv3 and insisting on the part about patents, people implementing new backends would be clear of problems | 11:24 |
| mafm | so there's at least risc-v (even if not upstreamed, their code is on github and should have some free license, I suppose), superh (supported by gcc, with patents expiring) and mips (supported by gcc, also some older patents expiring) that should be similar to openrisc | 11:26 |
| wallento | Yep, it may make sense to start a GSoC on this | 11:27 |
| wallento | it just should be a closed project | 11:28 |
| wallento | like with a result | 11:28 |
| wallento | so it is probably a basic port | 11:28 |
| mafm | yeah, and make sure to get a good mentor knowing about the topic :) | 11:29 |
| wallento | yep, thats the most critical | 11:29 |
| mafm | and yes, having realistic and clearly defined goals is quite important for the students | 11:34 |
| mafm | and for the orgas it is better if the project is not overly ambitious and doesn't extract 100% of the effort, but completely finished... a closed project, as you say | 11:35 |
| mafm | the basic port can then be expanded, but if it's half-baked and it doesn't work at all by the time the project is finished, maybe it all goes to waste | 11:36 |
| jeremy_bennett | wallento: More ideas emailed to you | 11:42 |
| wallento | thanks, jeremy! | 11:43 |
| poke53281 | mafm: Yes I was asking this. But didn't get a reply. | 12:44 |
| poke53281 | At the moment I am just curious. | 12:45 |
| poke53281 | Last year was funny, but also time consuming. Still wait for some Linux patches for MMIO so that I can finish the GSoC project from last year | 12:46 |
| mafm | poke53281: what was the name of the project? | 12:46 |
| mafm | and yeah, I am afraid that most people actually involved in the project never participate in that channel | 12:47 |
| mafm | I don't know if it was always like that, but it has been for a few months :) | 12:47 |
| poke53281 | http://jor1k.com/jor1k-orconf2015.pdf | 12:47 |
| poke53281 | Here are the details | 12:47 |
| wallento | hey poke53281 | 12:47 |
| wallento | you already have some nice ideas? | 12:48 |
| wallento | I will put up a fossi page this afternoon for collecting ideas | 12:48 |
| poke53281 | To have finally a good QEMU port would be still nice. | 12:48 |
| poke53281 | and doable | 12:48 |
| wallento | that means bringing the current one into a proper shape, right? | 12:48 |
| poke53281 | Yes | 12:49 |
| poke53281 | https://github.com/s-macke/jor1k/issues/24 + debugger + new interface + .... | 12:50 |
| wallento | that sounds great | 12:51 |
| mafm | poke53281: reading through the PDF... amazing :D | 12:51 |
| poke53281 | port of OpenJDK | 12:55 |
| poke53281 | Actually there is a good chance, that I start at a software company this year, which does mainly Java. So would be nice to start there with a port to OpenRISC ;) | 12:56 |
| poke53281 | mafm: Thanks | 13:00 |
| _franck__ | wallento: what about porting romcc (from coreboot project) to openrisc. It's a C compiler that only use registers. It can be useful to write rom code. | 13:17 |
| wallento | sounds good | 13:17 |
| wallento | can you write a 2 sentence description of it? | 13:18 |
| _franck__ | or SMP support in openocd for openrisc | 13:18 |
| wallento | and send to my mail: [email protected] | 13:18 |
| _franck__ | wallento: ok I will | 13:18 |
| wallento | great, thanks | 13:18 |
| wallento | feel free what you think is 3 months of work and a project with an actual outcome | 13:18 |
| poke53281 | http://opencores.org/or1k/OR1K:FutureWork | 13:19 |
| wallento | nice page, funny that we never use it anymore | 13:21 |
| wallento | so, I have started off with a few ideas I have the two sentences for already | 13:51 |
| wallento | http://fossi-foundation.org/gsoc16-ideas.html | 13:51 |
| wallento | please create a PR with your ideas to this file: https://github.com/fossi-foundation/fossi-foundation.github.io/blob/master/gsoc16-ideas.md | 13:52 |
| poke53281 | wallento: Send you two projects | 14:37 |
| poke53281 | http://www.lowrisc.org/docs/gsoc-2015-ideas/ | 14:45 |
| poke53281 | There were the projects last year. | 14:45 |
| poke53281 | Oh, I forgot. What about gdb port? | 14:45 |
| poke53281 | stekern or blueCmd would be a good mentor for this. | 14:46 |
| poke53281 | 3.5 hours to deadline wallento. | 15:31 |
| wallento | yeah, I am nearly finished with the application | 15:32 |
| wallento | the ideas are not mandatory before the deadline | 15:32 |
| wallento | but presumably are considered during evaluation | 15:32 |
| poke53281 | the question is, if you can apply in some way as an umbrella organization together with lowrisc and RISC-V. This would increase the chances significantly. But it is too late now I guess. | 15:33 |
| wallento | yeah, I think so | 15:35 |
| wallento | actually, FOSSi should at some point in time be able to run its own summer of code | 15:35 |
| mafm | wallento: (reading the fossi website) -- librecores is nice, but given the name of the org, fossicores could be a good name, although maybe some people will try to find second meanings or puns :D | 15:58 |
| mafm | foxycores, fossilcores, fussycores... | 15:58 |
| wallento | yeah, and actually it went the other way around | 15:58 |
| wallento | librecores was there before fossi | 15:59 |
| wallento | but we want it to be more then librecores | 15:59 |
| mafm | ah, since there is no link I thought that it hadn't been created yet | 15:59 |
| wallento | it is now | 15:59 |
| wallento | the intention was there earlier | 15:59 |
| wallento | but we just started with drafting the implementation | 15:59 |
| wallento | we wanted fossi as the legal body | 16:00 |
| wallento | to not have it under control of a company or a single person | 16:00 |
| mafm | is this a departure of opencores.org, then? | 16:04 |
| juliusb | we offered to take opencores over but that didn't work out | 16:06 |
| juliusb | so we've gone our own way | 16:07 |
| mafm | :) | 16:12 |
| mafm | that's quite nice | 16:14 |
| mafm | I was under the impression that everything would be shifted to risc-v now, and that these previous efforts would fade away | 16:15 |
| wallento | no, they can co-exist. In my humble opinion the RISC-V community and the OpenRISC community are organized differently | 16:19 |
| wallento | and the ambition around librecores is somehow orthogonal to both | 16:19 |
| wallento | its just that opencores is so 90s ;) | 16:20 |
| mafm | it is | 16:20 |
| wallento | speaking of all this stuff | 17:27 |
| wallento | we need to get the overview pages forward: http://openrisc.io/ | 17:27 |
| wallento | Its a petty we still need to reference the opencores Wiki as overview | 17:28 |
| -!- Netsplit over, joins: foreverska | 18:29 | |
| -!- Netsplit *.net <-> *.split quits: rhythmx, simoncook | 18:29 | |
| -!- Netsplit over, joins: rhythmx | 18:29 | |
| olofk | _franck_: Yeah!!! romcc for OpenRISC is the best idea ever :) | 22:15 |
| --- Log closed Sat Feb 20 00:00:39 2016 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!