| *** tpb <[email protected]> has joined #litex | 00:00 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 01:20 | |
| *** TMM_ <[email protected]> has joined #litex | 01:20 | |
| *** shorne <[email protected]> has quit IRC (Read error: Connection reset by peer) | 01:51 | |
| *** shorne <[email protected]> has joined #litex | 01:53 | |
| *** Degi <[email protected]> has quit IRC (Ping timeout: 256 seconds) | 02:02 | |
| *** Degi <[email protected]> has joined #litex | 02:03 | |
| *** AndrewD <[email protected]> has quit IRC (Quit: Client closed) | 03:31 | |
| *** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has quit IRC (Ping timeout: 256 seconds) | 05:43 | |
| *** FabM <FabM!~FabM@2a03:d604:103:600:2e60:8c7c:e8fb:7990> has joined #litex | 05:43 | |
| *** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has joined #litex | 05:58 | |
| *** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has quit IRC (Ping timeout: 245 seconds) | 06:05 | |
| *** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has joined #litex | 06:08 | |
| MoeIcenowy | got a Tang Mega 138K ES from Sipeed | 07:33 |
|---|---|---|
| MoeIcenowy | going to do some basic LiteX port to test it | 07:34 |
| *** mtretter <[email protected]> has quit IRC (Ping timeout: 245 seconds) | 08:38 | |
| *** mtretter <[email protected]> has joined #litex | 08:44 | |
| josuah | whoa :D I was curious about arora | 08:54 |
| josuah | MoeIcenowy: I have not this board, but would be happy to help with the bringup | 08:55 |
| josuah | I have the distant impression that LiteX could be made much more generic at many places | 10:44 |
| josuah | in particular in the target board definition, where chunk of codes are typically copy-pasted from board to board | 10:45 |
| josuah | for instance, to add a `with_jtagbone` to a board, there are several places where to inject the support | 10:47 |
| josuah | it could be done programatically for all boards who declare a JTAG interface | 10:48 |
| josuah | is this all by design, or is this a matter of slowly geting there as LiteX gets built further? | 10:48 |
| josuah | board definitions would be reduced to declaring the hardware (pins, hardened cores, clocks) and surrounding tooling (platform, command line flags for the adapter...) | 10:50 |
| josuah | hmm, somehow, LiteX board definitions are already that | 10:51 |
| josuah | https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/muselab_icesugar.py#L82-L84 for instance | 10:51 |
| josuah | it would only be a matter of managing the "if with_xxx: add_xxx()" globally rather than per-board: https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/muselab_icesugar.py#L95 | 10:52 |
| josuah | changes that affect all boards are always difficult unless owning the whole hardware | 10:55 |
| whitequark[cis] | there is a desire to improve board definitions dramatically in the next amaranth release | 10:56 |
| josuah | so it could need to be done incrementally: supporting "auto-feature" in enjoy-digital/litex, and make it an opt-in per board | 10:56 |
| josuah | whitequark[cis]: if I get enough time, I'd want to try add a `litex_boards/targets/amaranth_boards.py` :] | 10:56 |
| josuah | which would be a proxy to reuse all of Amaranth boards from LiteX | 10:57 |
| whitequark[cis] | this approach could result in friction, so it's something that needs to be evaluated carefully | 11:05 |
| josuah | I see how bugs in project X reported in project Y could be bothering | 11:20 |
| josuah | might be more fit as an evil experiment in basement lab than an official proposal | 11:20 |
| zyp | the problem I'd like to see a better solution for is when I've got a project that's buildable for multiple different boards that vary in what drivers they need | 11:34 |
| *** pavelow_ <[email protected]> has quit IRC (Quit: No Ping reply in 180 seconds.) | 11:38 | |
| *** pavelow <[email protected]> has joined #litex | 11:38 | |
| zyp | e.g. if I've got one board with a ddr3 memory and one board with a hyperram and I've got a project that doesn't really care what memory technology is available, how do I abstract over the differences? | 11:38 |
| whitequark[cis] | I think you need two toplevels | 11:40 |
| whitequark[cis] | there is no abstraction here that would not be worse than having two toplevels, I think | 11:41 |
| whitequark[cis] | since the difference between the toplevels would be basically "which memory adapter you instantiate" | 11:41 |
| zyp | it gets more complex if you start considering a matrix of generic footprint compatible modules and project specific carriers | 11:47 |
| zyp | like the colorlight stuff -- i5, i9 and i9+ are effectively ecp5-25, ecp5-45 and xc7a50 modules that are footprint compatible | 11:48 |
| josuah | where "two toplevels" could be a single toplevel with "if" branching? | 11:49 |
| zyp | I've put one of them in a fanuc robot arm, and at some point I'll probably put another in a plasma cutter | 11:49 |
| zyp | I figure the project should be the toplevel, since it'll have different functionality depending on the device it's going into, but I'd like to be able to build each of the projects for either of the three modules | 11:51 |
| josuah | They look like having quite the variants themselves https://aloi.com/wp-content/uploads/2016/06/FANUC-ROBOTS.jpg | 11:53 |
| josuah | nice project, this looks to be! | 11:53 |
| zyp | mine is from 1995 or so, probably much older than those :) | 11:54 |
| whitequark[cis] | zyp: you probably still do not want to exercise the entire matrix | 12:19 |
| whitequark[cis] | because there's no real way to find out if your design works properly other than simulation and extensive hardware testing | 12:19 |
| zyp | indeed, I don't need every combination in practice, but I still want it to be easy to make arbitrary combinations | 13:01 |
| whitequark[cis] | this still seems to me like something that can be solved with a bunch of toplevels, or one toplevel and a switch | 13:31 |
| whitequark[cis] | rather than inventing a new abstraction | 13:31 |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 13:39 | |
| *** TMM_ <[email protected]> has joined #litex | 13:40 | |
| *** acathla <[email protected]> has quit IRC (Ping timeout: 245 seconds) | 13:42 | |
| *** acathla <[email protected]> has joined #litex | 14:02 | |
| josuah | in that regard, it would help to allow toplevel be made very concise, making them look much more like a configuration file than anything | 14:16 |
| josuah | with most of the heavy lifting handled downstream, in what is called from them | 14:16 |
| *** so-offish <[email protected]> has joined #litex | 15:36 | |
| *** so-offishul <[email protected]> has joined #litex | 15:37 | |
| *** so-offish1 <so-offish1!~so-offish@2610:148:610:2b10::32> has joined #litex | 15:39 | |
| *** so-offish <[email protected]> has quit IRC (Ping timeout: 244 seconds) | 15:41 | |
| *** so-offishul <[email protected]> has quit IRC (Ping timeout: 244 seconds) | 15:42 | |
| MoeIcenowy | how to debug rgmii? | 15:58 |
| MoeIcenowy | (well a very bad question, but I don't know how to ask it better) | 15:59 |
| *** so-offish1 <so-offish1!~so-offish@2610:148:610:2b10::32> has quit IRC (Quit: Leaving) | 16:36 | |
| *** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Ping timeout: 256 seconds) | 16:44 | |
| josuah | MoeIcenowy: do you have any transceiver attached to it on hardware along with an Ethernet cable plugged to it? | 17:25 |
| josuah | MoeIcenowy: or do you have an RGMII interface on your design, and want to send packets to it in simulation? | 17:25 |
| *** lexano <[email protected]> has joined #litex | 20:25 | |
| *** feldim2425 <feldim2425!~feldim242@2001:871:25a:38bd:8241:f3cf:e6e3:4449> has quit IRC (Quit: ZNC 1.8.2+deb2build5 - https://znc.in) | 20:49 | |
| *** feldim2425 <feldim2425!~feldim242@2001:871:25a:38bd:90:c631:dc8c:54df> has joined #litex | 20:49 | |
| *** vup <[email protected]> has quit IRC (*.net *.split) | 21:21 | |
| *** vup <[email protected]> has joined #litex | 21:22 | |
| *** Degi <[email protected]> has quit IRC (Ping timeout: 240 seconds) | 21:58 | |
| *** Degi <[email protected]> has joined #litex | 22:00 | |
| *** Foxyloxy <Foxyloxy!~foxyloxy@cpc151593-shef16-2-0-cust343.17-1.cable.virginm.net> has quit IRC (Read error: Connection reset by peer) | 23:05 | |
| *** Foxyloxy <Foxyloxy!~foxyloxy@cpc151593-shef16-2-0-cust343.17-1.cable.virginm.net> has joined #litex | 23:06 | |
| *** matoro <matoro!~quassel@user/matoro> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 23:45 | |
| *** matoro <matoro!~quassel@user/matoro> has joined #litex | 23:47 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
