IRC logs for #openrisc Wednesday, 2015-01-28

--- Log opened Wed Jan 28 00:00:16 2015
-!- radii_ is now known as radii02:18
olofk_I see that is back online06:43
-!- olofk_ is now known as olofk06:43
sb0_trying to build or1k binutils09:09
sb0_gcc -g -O2  -o sysinfo sysinfo.o syslex_wrap.o09:09
sb0_syslex_wrap.o: In function `main':09:09
sb0_sysinfo.o:/home/sb/or1k-src/build/binutils/sysinfo.c:1: first defined here09:09
sb0_is that something you are familiar with?09:10
olofksb0_: Which build instructions do you use?09:10
olofkDon't know about the error unfortunately09:10
sb0_it works fine on arch linux, not on linux mint apparently09:10
olofkDon't know if it helps, but you could try the build instructions here:
olofkI updated the instructions for the newlib and musl toolchains to use the upstream binutils instead of or1k-src09:12
sb0_looks like this
sb0_stupid error message indeed09:14
sb0_recompiling ...09:14
olofkFantastic domain name :)09:14
olofkah ok. Yes. Missing bison or flex has given me weird errors before09:15
sb0_works now09:16
wallentoolofk and sb0_: I updated also those
wallentoupstream continuous buils still fail due to "connection reset by peer"10:59
olofkwallento: You really killed sourceware :(12:38
wallentoI feel guilty12:41
olofkI got a little tricky Linux question. I have a board with two completely DDR2 memories. Can I somehow use one of them as a normal memory and the other one exclusively as a DMA buffer?15:01
ysionneauI guess it depends on how you layout the A[] connections15:02
ysionneauif you can have something where the low addresses of the SoC are all mapped to the 1st chip , and then higher addresses on the second chip15:03
ysionneauthen you can declare those memory regions in Linux as DMAable / high memory15:03
olofkThat sounds like what I want to do15:04
ysionneauand then you increase the burst size to compensate the fact that you have less bits out per cycle since you now only talk to one DDR2 chip at a time15:05
olofkThey already have separate control pins15:06
olofkSo I just need to find out how to do it in Linux15:06
ysionneaus/burst size/burst length/15:06
ysionneau <=15:07
ysionneausomething like that (zones)15:07
ysionneaubut I guess this page is not up to date anymore15:07
Me1234Why does linux compiled with or1k-linux-gnu works only on qemu? (Does not work on or1ksim). Is it because of atomic15:11
poke53282Which QEMU version? The official one?15:30
poke53282or the one from blueCmd? Or the static one from the or1k Debian website?15:32
poke53282the patches for QEMU for the atomic instructions were accepted today.15:33
poke53282or1ksim is the reference implementation and should always work.15:55
-!- clopez_ is now known as clopez16:34
stekernMe1234: if you use or1ksim from current head, atomic instructions are supported17:02
stekernolofk: which peripheral do you want to DMA with?17:04
Me1234Ok, it was just linux configured for 1GB ram in the dts.17:44
--- Log closed Thu Jan 29 00:00:17 2015

Generated by 2.15.2 by Marius Gedminas - find it at!