Thursday, 2019-12-05

*** tpb has joined #litex00:00
*** CarlFK has joined #litex01:55
*** CarlFK has quit IRC02:39
*** nrossi has joined #litex03:14
*** rohitksingh has quit IRC05:46
*** rohitksingh has joined #litex06:55
*** m4ssi has joined #litex07:29
*** davidc__ has quit IRC08:35
*** davidc__ has joined #litex08:39
*** rohitksingh has quit IRC08:54
*** rohitksingh has joined #litex08:56
*** rohitksingh has quit IRC08:59
*** rohitksingh has joined #litex09:01
*** davidc__ has quit IRC09:55
*** shenki has quit IRC09:55
*** spacekookie has quit IRC09:55
*** RaYmAn has quit IRC09:55
*** bonzibuddy has quit IRC09:55
*** kbeckmann has quit IRC09:55
*** _whitelogger has quit IRC09:55
*** futarisIRCcloud has quit IRC09:55
*** Finde has quit IRC09:55
*** flammit has quit IRC09:55
*** st-gourichon-fid has quit IRC09:55
*** gruetzkopf has quit IRC09:55
*** goran-mahovlic has quit IRC09:55
*** rohitksingh has quit IRC09:55
*** m4ssi has quit IRC09:55
*** felix_ has quit IRC09:55
*** keesj has quit IRC09:55
*** Xark has quit IRC09:55
*** Dolu has quit IRC09:55
*** nrossi has quit IRC09:55
*** karol2 has quit IRC09:55
*** scanakci has quit IRC09:55
*** vup has quit IRC09:55
*** guan has quit IRC09:55
*** futarisIRCcloud has joined #litex09:57
*** Finde has joined #litex09:57
*** flammit has joined #litex09:57
*** st-gourichon-fid has joined #litex09:57
*** gruetzkopf has joined #litex09:57
*** goran-mahovlic has joined #litex09:57
*** futarisIRCcloud has quit IRC09:58
*** futarisIRCcloud has joined #litex09:59
*** rohitksingh has joined #litex10:00
*** m4ssi has joined #litex10:00
*** felix_ has joined #litex10:00
*** keesj has joined #litex10:00
*** Xark has joined #litex10:00
*** Dolu has joined #litex10:00
*** futarisIRCcloud has quit IRC10:01
*** Finde has quit IRC10:01
*** flammit has quit IRC10:01
*** st-gourichon-fid has quit IRC10:01
*** gruetzkopf has quit IRC10:01
*** goran-mahovlic has quit IRC10:01
*** futarisIRCcloud has joined #litex10:02
*** Finde has joined #litex10:02
*** flammit has joined #litex10:02
*** st-gourichon-fid has joined #litex10:02
*** gruetzkopf has joined #litex10:02
*** goran-mahovlic has joined #litex10:02
*** _whitelogger has joined #litex10:03
*** davidc__ has joined #litex10:04
*** shenki has joined #litex10:04
*** bonzibuddy has joined #litex10:04
*** spacekookie has joined #litex10:04
*** RaYmAn has joined #litex10:04
*** kbeckmann has joined #litex10:04
*** nrossi has joined #litex10:05
*** karol2 has joined #litex10:05
*** scanakci has joined #litex10:05
*** vup has joined #litex10:05
*** guan has joined #litex10:05
*** rohitksingh has quit IRC12:01
*** rohitksingh has joined #litex12:24
keesjI was wondering about https://github.com/enjoy-digital/litex/blob/master/litex/boards/platforms/arty.py#L11213:34
tpbTitle: litex/arty.py at master · enjoy-digital/litex · GitHub (at github.com)13:34
keesjthere dqs_p and dqs_n and clk_p and clk_n are used13:34
keesjthe clk_p/n are a differential pair (why are they not defined a "subsignal"13:35
keesjand dqs_p and  dqs_n are.. different pairs of differential signals.13:35
keesjon the ddr3 chips I am looking at they are called LDSQ and UDLS (lower an upper byte data strobe)13:36
keesjis there a reason for those names e.g.  dqs_p and dqs_n13:37
keesj?13:48
futarisIRCcloud_florent_: A question from hudson (spispy developer) regarding LiteDRAM:13:56
futarisIRCcloudI need to look into it.  Do you know how many cycles it takes to deliver a read? Most of the DRAM implementations I saw had fairly deep pipelines for their arbitrators and interfaces, which made them unsuitable for spispy.  Others had hardcoded refresh logic that wasn't easily circumventable, or logic that closed pages too quickly for repeated reads.13:56
_florent_keesj: sorry, i'm not sure to understand the question14:03
_florent_https://www.irccloud.com/pastebin/SMoUEU82/14:04
tpbTitle: Snippet | IRCCloud (at www.irccloud.com)14:04
_florent_here the first p/n pair is P(N2)/N(N1)14:04
keesj_florent_: I am wondering about the name. I don't understand why it is called dqs_p14:06
_florent_futarisIRCcloud: i would need to know the DRAM configuration to provides latency cycles and the requirement for spispy but it should be possible to use LiteDRAM (with eventual minor tweaks)14:10
_florent_keesj: dqs is commonly used for the data strobe signals14:11
keesjfutarisIRCcloud: I think that hudson explained that for spi the data is expected to be retured the next clock cycle just after the address is sent. DDR itself (the sate machine) takes quite a few cycles (bank select) and such. This is I think where the times gets spent. I don't really know about the performance of the bus itself14:16
keesj_florent_: and any idea why _p ?14:18
_florent_keesj: but i also remember seeing somewhere that they were knowing the address access pattern and were using that to improve latency (pre-opening rows for example)14:20
_florent_keesj:  _p = positive / _n  = negative14:20
keesjright but in this case dqs_p is not positive. it is a denominator for the upper data strobe line (for the upper 8 bits)14:49
daveshah?14:49
daveshaheach dqs is usually a differential pair14:49
daveshahN2 would be lower DQS positive and U2 upper DQS positive14:50
keesjthanks I understand it now! the dqs_p contains a list of the positive parts and if there would be 4 lanes it would contain 4 items... In the orange crab https://github.com/gregdavill/OrangeCrab the lines are caled UDQS (differential UDQS+ and UDQS-) and LDQS (differential LDQS+ and LDQS-) so the dqs_p wound become "DQSL+ UDSQ+"14:54
tpbTitle: GitHub - gregdavill/OrangeCrab: ECP5 breakout board in a feather physical format (at github.com)14:54
keesjminus the typo14:55
*** m4ssi has quit IRC16:51
*** freeemint has joined #litex16:52
*** freeemint has quit IRC17:07
*** freeemint has joined #litex17:08
*** freeemint has quit IRC17:29
*** freemint has joined #litex21:13
*** nrossi has quit IRC21:16
*** rohitksingh has quit IRC23:14
*** rohitksingh has joined #litex23:32
*** freemint has quit IRC23:43

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!