<threeflour[m]>
Nice! That looks like a really nice interface. I'm definitely going to take inspiration from it. How are you sending the 2232H JTAG commands? Are you using a library or are you interfacing with it directly?
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #amaranth-lang
anubis has joined #amaranth-lang
Degi has quit [Ping timeout: 252 seconds]
Degi has joined #amaranth-lang
anubis has quit [Remote host closed the connection]
anubis has joined #amaranth-lang
anubis has quit [Remote host closed the connection]
Seb[m] has joined #amaranth-lang
<Seb[m]>
<zyp[m]> "anyway, now I have a ~~pile of..." <- very cool, interested in trying this out if you ever decide to push it up
<zyp[m]>
yeah, I'm making a library out of it
<zyp[m]>
<threeflour[m]> "Nice! That looks like a really..." <- currently based on pyftdi, but I ran into enough issues with it that it's tempting to write my own at some point
frgo_ has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
jjsuperpower has joined #amaranth-lang
peepsalot has quit [Remote host closed the connection]
peepsalot has joined #amaranth-lang
<anuejn>
is there any way in which to publish packages that need amaranth-boards on pypi?
<anuejn>
as I understand it, git dependencies are now forbidden and packages that need them cannot be uploaded
<anuejn>
and as there is no amaranth-boards on pypi that poses kinda a problem
<zyp[m]>
I guess worst case you could just omit it from the dependencies list and raise a runtime error with instructions on how to manually install the appropriate version
<whitequark[cis]>
we could probably publish them if we had a versioning policy
<zyp[m]>
0.x.y, do a new y release after any significant addition, bump x whenever there's any breaking changes?
<zyp[m]>
it's not a very big library, so a strict deprecation policy with regular major releases seems unnecessary and kinda counterproductive
<zyp[m]>
as a user, I'd rather deal with the occasional sudden breaking change, than wait a long time for a new release that includes a particular board definition I'm interested in
<jeanthomas>
zyp[m]: +1
Ekho has quit [Quit: CORE ERROR, SYSTEM HALTED.]
Ekho has joined #amaranth-lang
nyanotech has quit [Quit: No Ping reply in 180 seconds.]
nyanotech has joined #amaranth-lang
<whitequark[cis]>
we could do that
<whitequark[cis]>
do you think you could formalize that as an RFC?
<whitequark[cis]>
then in a week or two i'd set up the infra if no concerns emerge
<zyp[m]>
I probably could, unless somebody else wants to
nyanotech has quit [Quit: No Ping reply in 180 seconds.]
nyanotech has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]