| *** tpb <[email protected]> has joined #litex | 00:00 | |
| *** Hammdist <[email protected]> has joined #litex | 02:15 | |
| *** Degi_ <[email protected]> has joined #litex | 03:34 | |
| *** Degi <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 03:34 | |
| *** Degi_ is now known as Degi | 03:34 | |
| lambda | am I just being blind or is litex (and migen in general) pretty, uh, light on documentation? I'm trying to understand how to use liteeth (whose only documentation seems to be its sparsely commented source code) for a not-quite-standard usecase, which also means understanding migen, but I've only been able to find the out-of-date https://m-labs.hk/migen/manual/ so far | 07:28 |
|---|---|---|
| tpb | Title: Migen manual — Migen 0.8.dev0 documentation (at m-labs.hk) | 07:28 |
| lambda | basically I want to have a high-speed UDP pipe in gateware, but also have a softcore running a DHCP client - the UDPCore might work for the former, but I don't think it'll work for DHCP, so I'm trying to figure out what I need to hook up there instead. | 07:31 |
| lambda | I've briefly used liteeth with just the wishbone MAC interface before and it worked pretty well, would be great to have something similar but with UDP already handled by liteeth :) | 07:38 |
| *** rubberworm <[email protected]> has joined #litex | 07:46 | |
| *** rubberworm <[email protected]> has left #litex | 07:46 | |
| swetland | My experience is similar -- a lot of stuff works great Out of the Box, but if there's good docs for doing more complex or custom things I have not stumbled over them. Trying to setup a Litex SoC with two LiteEth MACs was an adventure in clock domain naming/plumbing that I'm not entirely sure I got right | 08:02 |
| swetland | and migen has this unfortunate habit of "reporting" errors by means of python backtraces from its internals which I don't find very comprehensible | 08:03 |
| swetland | asking questions here is at least one viable path to getting answers or pointers to resources when you're stuck | 08:04 |
| *** indy_ <[email protected]> has joined #litex | 10:24 | |
| *** indy <[email protected]> has quit IRC (Ping timeout: 248 seconds) | 10:25 | |
| *** indy_ <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 10:31 | |
| *** indy <[email protected]> has joined #litex | 10:35 | |
| *** Hammdist <[email protected]> has quit IRC (Quit: Client closed) | 13:02 | |
| *** Hammdist <[email protected]> has joined #litex | 15:32 | |
| *** lexano <[email protected]> has quit IRC (Ping timeout: 244 seconds) | 15:55 | |
| *** lexano <[email protected]> has joined #litex | 16:08 | |
| mithro | _florent_: I added a profile page to the LiteX-Hub - https://github.com/litex-hub | 16:14 |
| mithro | lambda: Helping improve the documentation would be great | 16:14 |
| lambda | mithro: that kind of requires knowing how things work to begin with... | 16:15 |
| mithro | swetland: Having useful, user actionalable error messages when things go wrong is was one of the reasons that whitequark started the Amaranth language. | 16:15 |
| lambda | any plans to port litex to Amaranth? :p | 16:17 |
| mithro | lambda: Not to my knowledge, it would be a pretty big job | 16:27 |
| mithro | lambda: In fact there seems to be a page about this -> https://github.com/enjoy-digital/litex/wiki/Migen-Amaranth | 16:28 |
| lambda | yeah, was mostly meant as a joke | 16:35 |
| *** Hammdist <[email protected]> has quit IRC (Quit: Client closed) | 16:42 | |
| zyp | orbtrace is mixed litex/migen and amaranth, with a glue layer to make them play together | 19:40 |
| zyp | I'm intending to eventually split out the glue layer so it can be reused in other projects too | 19:41 |
| *** Wolfvak <Wolfvak!~Wolfvak@user/wolfvak> has quit IRC (Ping timeout: 276 seconds) | 20:55 | |
| *** Wolfvak <[email protected]> has joined #litex | 21:14 | |
| *** peepsalot <peepsalot!~peepsalot@openscad/peepsalot> has quit IRC (Ping timeout: 244 seconds) | 22:50 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!