HN user

LIV2

461 karma
Posts0
Comments182
View on HN
No posts found.
LibrePCB 3 years ago

Yes I have done so several times. 2 layer and 4 layer.

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.

LibrePCB 3 years ago

I am, and I have made a few popular designs.

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?

Not faster the second time around, every time I run each command from the makefile it takes 1 minute before there is even any output too

I will try running things without involving docker and see if that changes anything

This sounds suspicious to me. In my experience, Rosetta is faster on my M1 MBP than natively on my 2015 x86 MBP.

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

YMMV

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

At a previous job we used beaker tests as part of our pipeline to test puppet modules & environments before we would merge to prod. One of the things this tests is that the module applies and doesn't try to change anything / error out on subsequent runs.

The documentation sucks though imo, every different guide you find will show a completely different way of doing it

For me it's fun being able to play around/make hardware for a system that is still simple enough for one to understand broadly how the whole thing works.

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.

This seems to be a common thing in some OSHW stuff I've seen.

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.

Great work!

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!

1. Carbon, due to it's intel chip, can not drive 4K and 2K external monitors via thunderbolt adapter.

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

Amiga disks can't be read by PC floppy controllers whether they're USB or not (barring the 2 drive hack seen here before) because they write a whole track at once and pc floppy controllers can't be programmed to understand their sector headers.

If you want to read/write Amiga disks with a PC you need a greaseweasel or a Kryoflux

Many accelerators add faster CPU, Extra memory and IDE using original Motorola cpus and FPGA/CPLDs - what's cool about this is that it does all of that mostly in software (there's a CPLD to get the 68000 bus timing perfect) in real time without missing a beat.

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

Super toxic is amiga grifters resell open source hardware for massive markups, never contribute back & direct all support requests to the original author.

Pretty understandable why people quit when all they get is abuse and stress from a toxic community