00:27 <d1b2> <chuckmcm> Question, a lot of example code passes the platform into elaborate() and in the body of elaborate it requests I/O from the plaform. I it possible to do this outside of elaborate? I want my module code be platform independent and I am trying not to create an out-of-context passing scheme by using special names.

00:30 <whitequark[cis]> yeah, the platform is a normal Python object

05:55 <d1b2> <chuckmcm> So what is the best way to share a bit of source?

05:56 <whitequark[cis]> paste.debian.net or gist.github.com

06:02 <d1b2> <chuckmcm> https://gist.github.com/ChuckM/4eb73a633ee9ea37dd1e4591d04cd0c2

06:03 <d1b2> <chuckmcm> Basically I'm trying to build "components" that I can instantiate and pass in the wiring to them.

06:03 <d1b2> <chuckmcm> As opposed to building the wiring inside of them based on a specific platform.

06:04 <d1b2> <chuckmcm> I was wondering if you could do this, then you could create a KiCad plugin that would let you create "components" and hook them up with a schematic, and poop out an amaranth file.

06:04 <d1b2> <chuckmcm> But I'm basically way out over my skis trying to work along at least three learning curves at the same time 🙂

06:05 <whitequark[cis]> you could certainly do this, though it might work better if you wait until components land in Amaranth as a first class concept (there's an open RFC)

06:05 <d1b2> <chuckmcm> pointer?

06:05 <d1b2> <chuckmcm> And is it anything like what I'm thinking ?

06:06 <whitequark[cis]> no, but it could help you in your pursuit

06:06 <d1b2> <chuckmcm> (oh and it has been pretty amazing to see you're checkins and such). Great stuff.

06:06 <whitequark[cis]> https://github.com/amaranth-lang/rfcs/pull/2

06:06 <whitequark[cis]> checkins?

06:08 <d1b2> <chuckmcm> I've got some reading to do, thanks!

06:09 <d1b2> <chuckmcm> (sorry checkins == commits, also following along on glasgow)