09:42 <Raito_Bezarius> lofty: thanks

09:42 <Raito_Bezarius> it answer it pretty well

09:46 <lofty> You *can* in theory use nextpnr-mistral to place and route on the largest Cyclone V die (gt300f), which is probably not going to be *fast* but it should run basic code

09:48 <Raito_Bezarius> I was going to ask if the mistral project needs some help and what kind of help can be provided?

09:48 <Raito_Bezarius> assuming I do have a Cyclone V around

09:48 <Raito_Bezarius> lofty: ^

09:52 <lofty> Raito_Bezarius: so, you probably figured I'm the same Lofty mentioned in the post

09:52 <lofty> Here's the thing: the timings in nextpnr are... highly approximate.

09:54 <lofty> Sarayan has - as far as I know - managed to extract the actual timing data, but we're waiting for him to actually put it in databases so that we can make use of that data

09:54 <lofty> (the actual timing data is a bit awkward to use, however)

09:55 <lofty> So the project has been kind of stalled on that.

09:55 <Raito_Bezarius> Is there any open PRs / issues / repos to look on that, lofty ?

09:59 <lofty> See the thing is I'm pretty sure the timing data is going to change the API a large amount, so it feels a bit pointless to work on anything Mistral related until I have an API to use

10:01 <lofty> Like, there is block RAM support in nextpnr, but it was a bit flakey, which makes me think that there might be timing issues

10:02 <lofty> But I can't *check* that unless I have timing information ^^;