Tuesday, 2022-01-11

*** tpb <[email protected]> has joined #litex00:00
*** nelgau <[email protected]> has joined #litex03:07
*** Degi_ <[email protected]> has joined #litex04:49
*** Degi <[email protected]> has quit IRC (Ping timeout: 240 seconds)04:50
*** Degi_ is now known as Degi04:50
*** nelgau <[email protected]> has quit IRC (Remote host closed the connection)05:17
*** nelgau <[email protected]> has joined #litex05:18
*** nelgau <[email protected]> has quit IRC (Ping timeout: 256 seconds)05:22
*** zjason` <zjason`[email protected]> has joined #litex06:07
*** zjason <[email protected]> has quit IRC (Read error: Connection reset by peer)06:08
jevinskie[m]Does litepcie expose raw LTP packets (or the ability to code this) via MMIO?07:12
jevinskie[m]I’m looking to race my friend doing a hand written verilog version of a TLP bridge for qemu passthrough and device emulation07:13
*** FabM <FabM!~FabM@armadeus/team/FabM> has joined #litex07:37
_florent_tnt: The bitsy arrived this weekend, thanks!08:14
tnt_florent_: Ah nice :)  Watchout for the reset button on the pmod adapter, it's a bit stiff, I think it didn't like the ultrasonic wash too much but that was my last pushbutton.08:24
_florent_jevinskie[m]: not really with LitePCIe directly, but you could probably reuse all this: https://github.com/enjoy-digital/litepcie/tree/master/litepcie/tlp with the Packetizer/Depacketizer and connect it to your own logic08:28
_florent_jevinskie[m]: otherwise, this could be of interest: https://github.com/enjoy-digital/pcie_screamer08:29
_florent_jevinskie[m]: the aim was to redirect the TLP to an external PC and let it handle the TLPs & respond08:30
_florent_tnt: ok thanks, I'll have a look08:34
*** acathla <[email protected]> has joined #litex09:37
*** nelgau <[email protected]> has joined #litex11:20
*** nelgau <[email protected]> has quit IRC (Ping timeout: 256 seconds)11:24
geertua3f: The jh7100 clock/reset definitions have arrived in upstream Linux13:09
*** essele_ <[email protected]> has quit IRC (Read error: Connection reset by peer)13:46
r4d10n[m]1With this https://github.com/litex-hub/litex-boards/pull/321 , I am able to get Led chaser running on Pynq Z1.... Litex Bios is not showing up using litex_term... any hints ??14:14
*** nelgau <[email protected]> has joined #litex15:20
*** nelgau <[email protected]> has quit IRC (Ping timeout: 240 seconds)15:25
SpaceCoaster_florent_: I rigged up an upduino v2 with psram, same FPGA as bitsy. After a disk failure on my Mac I am restarting my psram stuff. Couldn’t get it to play with QSPI so just SPI for now.16:40
somlo_florent_: would it be fair to say that the LiteSDCard gateware doesn't concern itself with the voltage provided to the SD card in any way? (I dug through the migen sources and didn't find anything related to LiteSDCard attempting to manage or control that anywhere)17:34
somloso the voltage is something handled in physical hardware by the dev board or pmod adapter, directly?17:35
somloor am I getting that wrong in some way ?17:35
geertusomlo: I think that's correct.17:48
geertuOn boards with SoCs, you typically have a regulator that can be switched between 1.8V and 3.3V using a GPIO.17:50
geertuSee e.g. what the vmmc-supply and vqmmc-supply properties point to.17:52
somlogeertu: thanks! I'm trying to convince Ulf Hansson to let me get away without adding another (fragile, in my experience) dependency on some sort of voltage-regulator infrastructure, not sure how that's going to go :)18:30
somloI think I'm running into the same issue shorne was with clocks, I'd have to add a depends-on <some-sort-of-kernel-vcc-regulator-thing> to avoid probe getting auto-deferred in its absence, if I'm to do it via DT18:31
geertuWithout a regulator, you're probably doing mmc at 3.3V, but that depends on the board.18:43
geertuat fixed 3.3V.18:43
geertuThis is something LiteX is not yet aware of18:45
geertuSo litex_json2dts.py doesn't know.18:45
geertuFor an mmc bus with suitable voltages, you need both a switchable regulator (controlled by gpio), and switchable pin voltages (through pin control, see pinctrl-names = "default", "state_uhs")18:47
geertuI doubt LiteX supports switching a pin's IOStandard from LVCMOS33 to LVCMOS18 and vice versa at runtime?18:53
geertu_florent_: ^18:53
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Quit: Leaving)19:00
*** nelgau <[email protected]> has joined #litex20:04
*** nelgau <[email protected]> has quit IRC (Remote host closed the connection)20:13
*** nelgau <[email protected]> has joined #litex20:55
*** nelgau <[email protected]> has quit IRC (Ping timeout: 256 seconds)20:59
*** nelgau <[email protected]> has joined #litex21:13
*** nelgau <[email protected]> has quit IRC (Ping timeout: 240 seconds)21:23
*** nelgau <[email protected]> has joined #litex21:29
*** nelgau <[email protected]> has quit IRC (Ping timeout: 256 seconds)21:34
*** nelgau <[email protected]> has joined #litex21:37
*** nelgau <[email protected]> has quit IRC (Ping timeout: 240 seconds)21:42
*** nelgau <[email protected]> has joined #litex21:48
*** nelgau <[email protected]> has quit IRC (Ping timeout: 256 seconds)21:58
_florent_geertu: You need a specific chip or dynamic VIO on the SDCard bank for this, the FPGA can't do it directly.22:10
_florent_geertu: it was supported in the first version of LiteSDCard, but it has been simplified and removed (can be implemented on design requiring it, which are not very common in fact)22:12
somlo_florent_, geertu: if I won't be allowed to hard-code the mmc voltage in the driver probe() and will have to grab it from DTS instead (by adding a dummy voltage regulator set to 3.3v), I'll also have to make the driver depend on REGULATOR_FIXED_VOLTAGE in Kconfig22:24
somloI figured out how to do it, I'm just still not convinced it's worth the added bloat :)22:25

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!