| --- Log opened Mon Sep 19 00:00:18 2016 | ||
| wallento | olofk, I see | 01:49 |
|---|---|---|
| wallento | but I am still a bit concerned about the filesets in this context. They were kind of transparent to he backend so far, right? | 01:50 |
| olofk | Not sure what you mean | 02:22 |
| wallento | So far all sources, includes etc. were flattened | 02:32 |
| wallento | so there is no simple way to distinct two dpi libraries via filesets, right? | 02:35 |
| olofk | No, exactly. That needs to be solved if we want multiple dpi sections | 02:35 |
| wallento | even, one library may be split over multiple filesets | 02:35 |
| wallento | I am not sure if we want them, but lets assume so | 02:35 |
| olofk | I think we could assume that. One reason could be that we want to load different files depending on the simulator | 02:36 |
| wallento | is there any restriction or plan to restrict filesets? | 02:36 |
| olofk | restrict how? | 02:36 |
| wallento | so far its only a structural element on the input side | 02:36 |
| wallento | exactly, via the usage | 02:36 |
| wallento | but then it will not appear in one simulator, right? | 02:36 |
| wallento | so its virtually only one | 02:36 |
| olofk | Can you elaborate? | 02:37 |
| wallento | two DPI: the usage will filter out which files to use, right? | 02:38 |
| wallento | regarding restriction: Like saying all DPI files must be in one fileset if they form a library | 02:38 |
| wallento | but actually it may not be necessary | 02:38 |
| wallento | one last thing: how to distinct DPI and VPI then? | 02:38 |
| wallento | cSource can be both, right? | 02:39 |
| wallento | actually it can also be none of both, but a file to be compiled with verilator | 02:39 |
| wallento | I will do the fileset stuff, but it would be great if you could send me an example fileset | 02:39 |
| wallento | how DPI vs. verilator should look like | 02:39 |
| wallento | afk for some hours | 02:40 |
| olofk | Yes. I'm starting to think that maybe we should have both | 02:44 |
| olofk | Put the files in filesets to get the automatic export, usage, scope etc. And then mark them as source files in the respective vpi/dpi sections | 02:44 |
| olofk | The drawback will of course be that they need to be specified twice, so I'm not sure it's the best solution | 02:45 |
| olofk | If anyone happens to be in Stockholm 13 October, I'll be doing a talk on FOSSi stuff http://www.qamcom.se/media/event/breakfastseminar/ | 04:26 |
| olofk | wallento: Looking through the IP-XACT standard to see if there is anything there that can be useful for the DPI stuff | 06:06 |
| olofk | Once again I'm reminded of what a complete disaster of a standard that is | 06:06 |
| olofk | I'm amazed how they specify some things so hard, while other are completely left open | 06:06 |
| olofk | So far FuseSoC has only used the sane parts of the standard, and it will remain like that | 06:07 |
| olofk | Design by comittee taken to its extreme | 06:08 |
| olofk | For example, they have decided to enumerate the valid return types of a function. The list contains of int and void | 06:09 |
| stekern | olofk: is that breakfeast seminar open for everybody? (i.e. do you mind if I hint about it to some friends in sthlm?) | 06:41 |
| olofk | stekern: Please spread the word. It's open to everyone and I hope to see some new faces | 06:44 |
| stekern | cool, will do | 06:44 |
| stekern | I'll be on the other side of the pond at that date, otherwise I might have tried to attend | 06:47 |
| olofk | Ah ok, but when I said it's open for everybody, I didn't mean it's open for you | 06:48 |
| olofk | We do have some standards | 06:48 |
| stekern | oh, I should have figured :( | 06:48 |
| stekern | I would of course been coming disguised | 06:49 |
| olofk | =) | 06:53 |
| stekern | ...and you know, asking obnoxious questions, just like your friends did during your thesis presentation. | 07:27 |
| stekern | (or mine at least) | 07:28 |
| olofk | My thesis presentation was so bad that no one knew where to begin asking questions :) | 07:38 |
| SMDwrk | olofk: what was the topic? | 07:39 |
| olofk | SMDwrk: Turning simulink models into HDL code and execute them in LabVIEW's FPGA environment | 07:48 |
| olofk | Spend six months drawing blocks and wires and struggling with really crappy and expensive tools | 07:49 |
| shorne | stekern: some interesting responses came in from Jonas on the kernel patches I sent | 10:38 |
| -!- Mentally_Ill is now known as hammond | 10:45 | |
| shorne | wallento: thanks for you replies on the mailing list, maybe jeremybennett can help us get those last assignments and we can get our toolchains upstreamed | 12:11 |
| jeremybennett | shorne: I've pinged Damjan on LinkedIn | 12:43 |
| jeremybennett | However I'm not sure how effective that will be. He is shown as CEO of Kulfun Games, but that appears to be defunct - looks like the games were acquired by another company. He may be running a company called Kulone in Belgrade now, but I couldn't easily track it down. | 12:44 |
| stekern | shorne: yes, I saw | 12:48 |
| jeremybennett | stekern: shorne: Had a reply straight back from Damjan. He did a FSF copyright assignment years ago, which the FSF should have on file. | 13:34 |
| stekern | jeremybennett: yes, it wasn't he that was missing | 13:37 |
| jeremybennett | stekern: Have you checked if Matjaz has an assignment on file already. He might do if the Flextronics guys submitted en masse. | 13:50 |
| jeremybennett | There might even be a generic Flextronics assignment. | 13:50 |
| stekern | I haven't checked anything ;) | 14:00 |
| stekern | but I know that much that he didn't do that | 14:00 |
| stekern | just noticed that github reviews have got some nice features | 14:00 |
| stekern | nice *new* features | 14:00 |
| jeremybennett | stekern: shorne: Just emailed you a little more info that may help. | 14:04 |
| -!- hammond is now known as hammond-ey | 16:30 | |
| shorne | jeremybennett: Damjan replied and said he alrady assigned hit copyrights to fsf. Thank you very much | 17:06 |
| shorne | jeremybennett: I see, you also had got a reply | 17:09 |
| olofk | Hmm.... looks like the embedded wb_sdram_ctrl in wb_altera_ddr_wrapper is killing much of my memory bandwidth | 17:11 |
| olofk | I think I have some improvements I made two years ago somewhere | 17:12 |
| olofk | But I don't know if that's enough | 17:12 |
| olofk | Might have an idea now | 17:17 |
| olofk | If I expose the burst length from mor1kx, I could just use a regular arbiter with an avalon interface on the downstream side | 17:17 |
| olofk | stekern: burst lengths are static or at least easily predictable in mor1kx, right? | 17:18 |
| olofk | Wishbone really needs a burst length field. It would make interfacing with other protocols so much easier | 17:19 |
| -!- Netsplit *.net <-> *.split quits: wallento, andrzejr | 17:51 | |
| -!- Netsplit over, joins: wallento | 17:51 | |
| -!- Netsplit over, joins: andrzejr | 17:51 | |
| stekern | olofk: burst lengths depend on cache line width | 22:37 |
| stekern | so, yes they are static (for a given setup) | 22:38 |
| --- Log closed Tue Sep 20 00:00:20 2016 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!