461 karma · joined January 23, 2019
Denmark and Norway are two different countries
I can't see how it would cost me money to do so, on the other hand if I was to blindly autoroute my designs i'd spend more time troubleshooting and way more money doing several revisions before I got something stable.
I would consider it absolutely unnecessary, and invariably results in something that is unreliable at best.
Do you have examples that show how it is essential?
I will try running things without involving docker and see if that changes anything
I'm using an x86_64 container and it's definitely using Rosetta via binfmts because if I remove that the container won't even start
The performance will obviously depend on the workload
> How did you measure this?
Running the exact same docker image based on this: https://github.com/chriz2600/xilinx-ise And the code from this git repo of mine: https://github.com/LIV2/GottaGoFastRAM2000
Inside a Debian vm:
docker run --rm -it -v ${PWD}:/build -w /build xilinx-ise /bin/bash
cd RTL
make clean
time make ../Binary/XC9572XL/gottagofast2000.jed
When I get a chance I will check the timing of each individual step from the makefile.If there is something I'm missing I'd love to know, I'd rather not have to run my builds on another machine
I was excited for this because I thought it'd enable me to compile my HDL projects on my MacBook, since I'm targeting the Xilinx XC9500XL series of CPLDs this requires some an EOL design suite.
Anyway, build times are:
4 minutes with Rosetta 2
11 minutes with qemu-user-static
Whereas it only takes 20 seconds on my early 2013 MacBook Pro.
I think it would also be nice if it were possible to use this with other hypervisors. I believe it is limited to virtualization.framework so it cannot be used inside fusion for instance
> Stop mistaking our country for your own.
I'm Australian
It's also convenient that these suburbs are not the ones being targeted by huge police operations
https://www.theguardian.com/australia-news/2021/jul/08/weste...
Screw everyone else though right?
The documentation sucks though imo, every different guide you find will show a completely different way of doing it
Someone's done the A4000 in an ATX form factor too https://www.retrosummit.com/2018/08/21/a4000tx-atx-amiga-mot...
The schematics are available for them & they're documented really well
People still make software & games for it for presumably the same reason, then there's people who are into it for the nostalgia and the games.
Some people will take your work and sell it for massive markup but the support is expected to be provided by the creator (and a lot of the issues stem from the fact that these sellers might substitute parts for cheaper ones that don't meet some critical specs like timing or TTL compatibility for example)
When those creators say they aren't happy with that arrangement all they get is abuse - sure everything is legal but it doesn't make the behaviour any less immoral or scummy.
I had thought about trying this myself but gave up after realising I'd not have access to Trackdisk.device from Romwack - Didn't know about Coolcapture/Warmcapture. I guess I need to read up some more!
Is this a Linux only issue? I saw people reporting on Reddit that they are using 4k @ 60hz external monitors. Was thinking of getting an X1C but not if it can't do 4k
If you want to read/write Amiga disks with a PC you need a greaseweasel or a Kryoflux
Should big tech be deciding who gets a free trial?
He had some issues with hdmi capturing that he fixed in the second video
System emulators like WinUAE don't have to be perfectly accurate with their timing, you can frame skip and do other tricks to catch up lost time but you can't do that when interfacing with real hardware like this. If you don't get the timing right it will crash
Pretty understandable why people quit when all they get is abuse and stress from a toxic community
I suspect they think they'll have a better chance threatening the Australian government than French/EU ones