| @juliusb | olofk: hmm yes, interesting question | 00:24 |
|---|---|---|
| @olofk | I just found out that there is no way to call verilog functions from C | 00:26 |
| @olofk | How large is the SPR space? | 00:26 |
| @olofk | Making a simulator-only flat array that replaces or complements the get_spr function feels like the least crappy way to do it | 00:27 |
| @juliusb | SPR space is big :( | 00:31 |
| @olofk | Crap | 00:33 |
| @olofk | Ok... what's the maximum amount of registers that need to be looked at for a single instruction then? two gpr + one spr? | 00:35 |
| @olofk | Maybe I have to settle for just instruction decoding for now | 00:42 |
| @juliusb | Sorry dude, just distracted a bit, very tired too, had a cold lately, won't be much good tonight :( | 00:55 |
| @juliusb | I forget exactly how the VPI stuff works | 00:56 |
| @juliusb | but, yes I think you can't call back into the Verilog... maybe | 00:58 |
| @juliusb | It's a bit crap that, isn't it? | 00:58 |
| @juliusb | Can't pass a pointer to a Verilog array? | 00:58 |
| @juliusb | Although, you can but the SPRs aren't stored like that | 00:58 |
| @juliusb | Ah, you can return like a command and a value to the Verilog, though | 01:02 |
| @juliusb | to then tell it to fetch an SPR | 01:02 |
| @juliusb | Maybe that's the way to do it - like, pass the instruction and then have the disassembly function set what it needs | 01:03 |
| @juliusb | and then Verilog can use those values to determine what it needs to pass back | 01:03 |
| olofk_htc | Grr.. posted in the wrong channel. I hate using IRC from thia phone | 09:07 |
| olofk_htc | oh well, juliusb, or whoever else is using or1ktrace. Take a look in #opencores. Got some questions there | 09:09 |
| jeremybennett | olofk_htc: sentient phone letting you down again :) | 10:17 |
| @juliusb | whoops | 16:24 |
| -!- juliusb changed the topic of #openrisc to: Official OpenRISC Project channel | http://opencores.org/or1k | http://openrisc.net | wiki: http://opencores.org/or1k/OR1K:Community_portal | Mailing lists: http://lists.openrisc.net/ http://lists.opencores.org/ | forum: http://opencores.org/forum,OpenRISC | git: https://github.com/openrisc | 16:27 | |
| -!- juliusb changed the topic of #openrisc to: Official OpenRISC Project channel | http://opencores.org/or1k | http://openrisc.net | wiki: http://opencores.org/or1k/OR1K:Community_portal | Mailing lists: http://lists.openrisc.net/ http://lists.opencores.org/ | forum: http://opencores.org/forum,OpenRISC | git: https://github.com/openrisc | OpenCores in #opencores | 16:28 | |
| @olofk | juliusb: Do you have the presentation from last year's fscons? | 22:12 |
| @juliusb | olofk: they should be on OpenCores | 22:13 |
| @juliusb | http://opencores.org/or1k/FSCONS2011 | 22:13 |
| @olofk | Great | 22:15 |
| @olofk | I was thinking that we could probably reuse a great deal of the first slides for introduction. There will probably be many people who haven't heard about the project | 22:16 |
| @juliusb | good thinking! | 22:17 |
| @olofk | It's quite fun to see that a few of the biggest items on last year's wishlist have been fulfilled | 22:18 |
| @juliusb | haha cool | 22:18 |
| @juliusb | put a moon landing on this year's then | 22:18 |
| @olofk | qemu, shared objects, increased RTOS usage.. | 22:19 |
| @olofk | lol | 22:19 |
| @juliusb | actually, I shouldn't joke, there's a few boys at Linux Conf AU a couple years ago who were interested | 22:19 |
| @juliusb | doing some lunar landar project | 22:19 |
| @olofk | Well, I'm up for doing a port :) http://en.wikipedia.org/wiki/Lunar_Lander_%28arcade_game%29 | 22:20 |
| @juliusb | :) | 22:21 |
| @olofk | Damn... tithub.com is already taken. I had a great idea for a new career move :( | 22:31 |
| -!- maximi89 is now known as todos | 23:16 | |
| -!- todos is now known as maximi89 | 23:17 | |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!