| --- Log opened Mon Jan 12 00:00:52 2015 | ||
| -!- FreezingAlt is now known as FreezingCold | 04:24 | |
| olofk | Saw someone on the opencores forum who complained of a missing ___umodsi3. That was fixed quite recently, wasn't it? | 08:58 |
|---|---|---|
| stekern | olofk: no, I don't think there ever been a problem with it | 10:40 |
| olofk | http://www.juliusbaxter.net/openrisc-irc/%23openrisc.2014-07-31.log.html#t09:46 | 10:53 |
| stekern | ok, so there has been bugs fixed that relates to umodsi3, but it was never missing | 10:56 |
| stekern | ;) | 10:56 |
| stekern | I answered the forum guy | 10:56 |
| olofk | cool. I didn't really understand the issue on IRC. Just remembered something about umodsi | 10:56 |
| stekern | it's good that you do, it could have been related | 10:58 |
| olofk | _franck__: Happy birthday! | 11:33 |
| olofk | stekern: You don't happen to have an avalon 32 to 64 bit converter? | 11:34 |
| stekern | no, but doesn't altera have a bunch you can use? | 11:39 |
| olofk | ah.. right | 11:39 |
| stekern | I think if you are using qsys and connect a 64-bit bus to a 32-bit bus, it'll insert converters automatically | 11:39 |
| olofk | That could be an option. Feels like my setup is complicated enough already | 11:41 |
| stekern | I bet you can poke them out manually in some mega-something though | 11:43 |
| olofk | If only my DDR2 controller worked reliably :/ | 11:48 |
| olofk | How do I start qsys? | 11:48 |
| stekern | qsys.edit | 11:56 |
| stekern | ehm.. | 11:56 |
| stekern | qsys-edit | 11:56 |
| olofk | stekern: There's some qsys support in fusesoc, right? | 12:16 |
| _franck__ | olofk: thanks. Who betrayed me ? :) | 12:27 |
| olofk | _franck__: LinkedIn :) | 12:30 |
| stekern | olofk: yup, sure is | 12:44 |
| olofk | stekern: Ok, so I've created a qsys thingie now. What next? | 12:58 |
| olofk | Should I generate verilog files somehow? | 12:58 |
| stekern | you add the qsys file to qsys_files under [quartus] | 13:07 |
| stekern | the when you run fusesoc build, it will generate the verilog files for you in the build dir | 13:08 |
| olofk | great | 13:09 |
| olofk | IIRC you had some manual step as well. Was that because of some special setup in your case? | 13:10 |
| stekern | no, that was before the qsys support was added to fusesoc | 13:11 |
| olofk | ah ok | 13:11 |
| olofk | It always takes something like 10 seconds for emacs to start up. There must be something weird set up. Any tips for debugging? | 13:23 |
| amylaar | blueCmd: We at Embecosm wanted to have a look at the regression test failures of the OpenRISC port. So first we need to reproduce this. Is the gcc in https://github.com/bluecmd/or1k-gcc branch gcc-trunk? | 14:57 |
| stekern | amylaar: it's github.com/openrisc/or1k-gcc | 16:42 |
| blueCmd | the other repo is the staged repo for mainline inclusion. its most probably out of date | 16:44 |
| aburgess | stekern, blueCmd in the or1k-gcc repo, is it the or1k branch that is the interesting one? | 16:52 |
| stekern | aburgess: yes, that should be the most recent | 16:54 |
| aburgess | stekern, thank you | 16:54 |
| stekern | latest sync was against the 4.9.1 release though, so it's slightly dated in terms of following mainline | 16:54 |
| olofk | Has anyone tried to build newlib from upstream? | 17:33 |
| olofk | Haven't seen wallento around lately | 17:33 |
| olofk | Hmm. I must be doing something wrong when I install the newlib toolchain | 19:04 |
| olofk | I'm getting a lot of undefined references | 19:04 |
| olofk | and multiple definitions | 19:04 |
| olofk | /opt/or1k/lib/gcc/or1k-elf/4.9.1/../../../../or1k-elf/lib/libor1k.a(syscalls.o): In function `_write_r': | 19:04 |
| olofk | /home/olof/code/bld/newlib/or1k-elf/libgloss/or1k/../../../../../newlib-2.2.0/libgloss/or1k/syscalls.c:32: multiple definition of `_write_r' | 19:05 |
| olofk | That wasn't a good paste | 19:05 |
| olofk | http://pastie.org/9828003 | 19:06 |
| olofk | This is when I compile a hello world with or1k-elf-gcc | 19:06 |
| olofk | Or is the upstream newlib broken? | 19:20 |
| olofk | Based on previous experience, my first guess is that the fault is on my side | 19:21 |
| ysangkok | poke53282: do you know if gdb would work in or1ksim? | 19:28 |
| poke53282 | ysangkok: Yes, I know the answer. ;) | 20:32 |
| poke53282 | The answer is the same for jor1k. | 20:33 |
| ysangkok | ah :( ok | 20:33 |
| poke53282 | we need better ptrace capabilities of the kernel and further changes in gdb for the openrisc platform. | 20:35 |
| poke53282 | ptrace works already. But only after one weekend of fiddling with the kernel and ptrace. | 20:36 |
| poke53282 | strace works too. | 20:37 |
| poke53282 | sorry, I mean ltrace | 20:38 |
| poke53282 | ltrace works already. But only after one weekend of fiddling with ptrace in the kernel and ltrace. | 20:39 |
| poke53282 | I know it is confusing. | 20:39 |
| poke53282 | strace, ltrace, ptrace. | 20:39 |
| ysangkok | yeah :P | 20:46 |
| -!- Netsplit *.net <-> *.split quits: LoneTech | 21:14 | |
| ysangkok | poke53282: so, i wanted to add the ability to specify fs metadata in the query string, to enable loading thirdparty CORS content (i believe the "src" field is already an url?). but to make it even easier to inject random data, it would be useful if there were a was to specify file content in the filesystem json. this would make it easier to test different changes without changes the urls which are point | 21:47 |
| ysangkok | ed to. | 21:47 |
| ysangkok | poke53282: i have two solutions that i think are both ok: make the "src" field a URI instead, which means one could use Data URI's with optional base64 encoding | 21:48 |
| ysangkok | poke53282: the other solution is to add a new field and mandate the base64 encoding. this frees us from implementing a custom data URI parser (i believe this is also not available to javascript) | 21:49 |
| ysangkok | poke53282: do you have any thoughts on this matter? | 21:49 |
| poke53282 | the src field is a link to a file, if the normal way to determine the link fails. | 22:45 |
| poke53282 | like files which begin with . or _. | 22:45 |
| poke53282 | Of course, this field can be extended for uri. | 22:46 |
| poke53282 | but only as an option. | 22:46 |
| poke53282 | both should be possible. | 22:47 |
| poke53282 | But I don't understand the base64 encoding. Why? | 22:47 |
| ysangkok | poke53282: because it's how people usually put binary data in json? | 23:19 |
| --- Log closed Tue Jan 13 00:00:53 2015 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!