02:46 <whitequark> I think the start address is 0x<memaddr> in misoc

02:51 <sb0> whitequark, seems to contain a bit of hype and buzzwords. they could have simply said "we implemented an artificial neural network in SmNiO3"

02:54 <whitequark> yeah, it's funny

02:54 <whitequark> thinking rocks!

03:03 <GitHub24> [smoltcp] whitequark pushed 2 new commits to master: https://git.io/vdBU5

03:03 <GitHub24> smoltcp/master 067fb2d whitequark: Fix a typo.

03:03 <GitHub24> smoltcp/master 100b57a whitequark: Replace "socket debug identifiers" with just socket handles....

03:05 <travis-ci> m-labs/smoltcp#309 (master - 100b57a : whitequark): The build passed.

03:05 <travis-ci> Change view : https://github.com/m-labs/smoltcp/compare/b0fc1d9542ef...100b57aa669a

03:05 <travis-ci> Build details : https://travis-ci.org/m-labs/smoltcp/builds/283499317

03:23 <mithro> whitequark: You mean you think the mor1kx is configured with a start address of 0x<memaddr> ? soc_core.py does seem to set cpu_reset_address=0x00000000 which is passed into the mor1kx as OPTION_RESET_PC (defined https://github.com/openrisc/mor1kx/blob/477a7c5a8af8b1f52953338992ef7ccbf903447f/rtl/verilog/mor1kx.v#L67-L68 ) which seems to be used here ->

03:23 <mithro> https://github.com/openrisc/mor1kx/blob/75b928a2287ca926d320915fa4ff165957bb0eaf/rtl/verilog/mor1kx_fetch_cappuccino.v#L228

03:28 <whitequark> es

03:28 <whitequark> *yes

03:28 <whitequark> I think it's noncompliant with whatever spec you're reading

03:31 <mithro> whitequark: Yeah -- somewhat seems that way...

03:31 <whitequark> *shrug* feel free to fix

03:32 <whitequark> I think it makes no difference either way

03:34 <mithro> whitequark: It seems like the default value is -- parameter OPTION_RESET_PC = {{(OPTION_OPERAND_WIDTH-13){1'b0}}, `OR1K_RESET_VECTOR,8'd0},

03:35 <whitequark> yeah, I mean fix in misoc

03:48 <GitHub35> [smoltcp] whitequark pushed 1 new commit to master: https://git.io/vdBkD

03:48 <GitHub35> smoltcp/master 096ce02 Egor Karavaev: Implement a SocketRef smart pointer to detect state changes.

03:48 <GitHub43> [smoltcp] whitequark closed pull request #42: Use smart pointers in SocketSet's API (master...socket_ref) https://git.io/v5Dw7

03:48 <GitHub143> [smoltcp] whitequark commented on issue #42: Merged manually with... lots of changes.... https://git.io/vdBky

03:49 <mithro> whitequark: Yeah - I'll asked the openrisc guys what they think first....

03:51 <travis-ci> m-labs/smoltcp#310 (master - 096ce02 : Egor Karavaev): The build passed.

03:51 <travis-ci> Change view : https://github.com/m-labs/smoltcp/compare/100b57aa669a...096ce02ac4c9

03:51 <travis-ci> Build details : https://travis-ci.org/m-labs/smoltcp/builds/283508767

03:54 <GitHub81> [smoltcp] whitequark commented on issue #42: Merged manually with... lots of changes.... https://git.io/vdBky

05:49 <GitHub96> [smoltcp] phil-opp commented on issue #49: > In the future, please discuss such changes with me first, this will save both of us time and effort.... https://git.io/vdBm5

05:54 <GitHub172> [smoltcp] whitequark commented on issue #49: > Well, sometimes it's difficult to anticipate how certain changes would work out without implementing them.... https://git.io/vdBmh

05:58 <GitHub57> [smoltcp] whitequark commented on issue #49: Oh, and please create a meta-issue like [the redox people did](https://github.com/m-labs/smoltcp/issues/50) for whatever it is you want to use smoltcp for. It's handy for me to have a bird's eye view. https://git.io/vdBYY

08:16 <travis-ci> batonius/smoltcp#102 (master - 096ce02 : Egor Karavaev): The build passed.

08:16 <travis-ci> Change view : https://github.com/batonius/smoltcp/compare/d88ef3c8d3c8...096ce02ac4c9

08:16 <travis-ci> Build details : https://travis-ci.org/batonius/smoltcp/builds/283576992

14:29 <rjo> whitequark, sb0, mntng: could you hook up the kcu105 (power and jtag-usb)?

15:48 <sb0> rjo, will be done tomorrow

15:48 <sb0> is that for debugging the 2nd flash issue?

15:54 <rjo> yes. and 4 byte addressing.

20:06 <mithro> If anyone in here is interested, we are running a TimVideos hackfest before LCA2018 here in Sydney, Australia -- We will no doubt be hacking on HDMI2USB, PhotonSDI, Migen/MiSoC, LiteX and similar things -- LCA2018 will also be having a day long "Build your own SoC to run linux (using LiteX)" tutorial event.... -- If you think you might possible want to come can you fill out this form so we can understand how much

20:06 <mithro> funding / sponsorship we need to source for flights / accommodation / etc -> https://goo.gl/forms/1FI041Iat7LgQA9N2

21:25 <mithro> What does `fwft` added to the SyncFIFO in https://github.com/m-labs/migen/commit/8baa957539d965b6548983b177e186a855d8ed5e mean?