06:08 <mithro> sb00: So, what is "PlatformInfo" object (in migen/build/generic_platform.py) used for?

06:14 <mithro> sb00: I was also wondering if you had an examples of the ConnectorManager and how it is suppose to be used...

06:16 <mithro> I'm looking at https://github.com/m-labs/artiq/blob/df4f38a1e4d6eeee04c81a60e8b37f2982417ec6/artiq/gateware/nist_clock.py for example and not quite sure about what is going on...

13:32 <mithro> sb0: Is PlatformInfo meant to be used for doing things like adding sillkscreen labels on connectors?

13:35 <sb0> nothing uses that anymore. i think it should be removed.

13:37 <mithro> sb0: I'm looking for the right way to add annotations about things like silkscreen labels

13:37 <sb0> silkscreen labels in migen?

13:37 <sb0> why?

13:37 <sb0> put them in source code comments?

13:37 <sb0> or docstring?

13:38 <mithro> sb0: So they can be exported into the firmware code and provide aliases for things

13:38 <sb0> exported how?

13:40 <mithro> Maybe through things like CSRConstants? For example in micropython we want to be able to do "l1 = LED('LD0')" were 'LD0' comes from the silkscreen. For the HDMI2USB being able to do things like "matrix connect <silkscreen label for hdmi input> <silkscreen label for hdmi output>"...

13:44 <sb0> I'd handle that with some simple hardcoded map in firmware

13:44 <sb0> you don't need to integrate that into migen

13:46 <sb0> you can generate that map with your build script or something

13:47 <mithro> sb0: I also think it is useful documentation in platform file - This is what we are doing at the moment - https://github.com/timvideos/HDMI2USB-litex-firmware/blob/master/platforms/opsis.py#L474-L497

13:47 <sb0> \\r\\n?

13:53 <mithro> sb0: I was thinking adding something like a "Label()" or "Info()" type thing in the platform files that I can attach directly to the _io things to keep things together... That is when I discovered PlatformInfo thing

13:54 <sb0> yes, but you still have to handle it in your build script

13:54 <mithro> sb0: Allowing modules to export the information in what ever way they wanted (IE It would also be useful for things like device-tree generation)

13:55 <sb0> migen/misoc does nothing with it

13:58 <mithro> sb0: I guess it's like the new type annotations in Python, Python doesn't do anything with it directly, but it enables other things to do stuff with them because it is structured... -- How would you attach a docstring to the stuff inside "_io = []"?

13:59 <sb0> you cannot. i meant the docstring for the module.

14:09 <mithro> sb0: I don't really understand how _connectors / add_extension / ConnectorManager stuff works? I was looking at artiq and it seems like there is something about how the pins are labeled - https://github.com/m-labs/artiq/blob/master/artiq/gateware/nist_clock.py and https://github.com/m-labs/artiq/blob/master/artiq/gateware/nist_qc2.py ?

14:28 <sb0> it's quite simple, a connector is a connector pin -> FPGA pin map, and then you can use the <connector name>:<connector pin> notation in IOs