<cr1901>
Ahhh, I don't want to use it as a platformpicker, but rather a "core variant picker"
<cr1901>
i.e. highlight one variant, it tells you features at a glance, highlight another, it tells you the differences
<whitequark[cis]1>
it doesn't actually care what you consider a "platform"
<whitequark[cis]1>
i was going to add autodetection of linux/windows/whatever so that you get the right platform when you load the page but i never actually implemented it
<cr1901>
Then it's probably fine for what I want and I'll evaluate it
<conventia[m]>
I already have an address showing up via i2c. So, awesome. 🙂
<whitequark[cis]1>
nice
<whitequark[cis]1>
is this with the glasgow core?
<conventia[m]>
No, I'm considering using i2c as part of a tiny tapeout project.
<conventia[m]>
But the i2c implementation in glasgow is an updated version of the one in amlib, it seems.
<cr1901>
How big is the i2c impl approx (both glasgow/amlib)?
<conventia[m]>
122 ICESTORM_LC's?
<cr1901>
oh cool... just curious. Is that with multicontroller support?
<conventia[m]>
Well, this includes blinky and a i2c target, which does nothing but have an address. So, I'd take it with a grain of salt (or a pile).
<cr1901>
Also to answer your RV64 question; Idk any RV64 Amaranth cores offhand. I impl it in principle for Sentinel, but I don't want to lol (for instance, rv32i is better supported in Rust than rv64i) :P.
<conventia[m]>
I think it'd be easier to do in amaranth than verilog/vhdl.
<whitequark[cis]1>
i would hope so :p
<conventia[m]>
Well, they both have generate but the syntactical restrictions involved make it useless for some things.
<cr1901>
.oO (Use three Sentinel cores; one core dispatches RV64I instructions as RV32I ones by using the reg files of the other two behind a private bus)