389 karma · joined January 29, 2017
Thanks for posting this; bookmarked.
(*) apart from :q!
Other keys that would have been great to become standard: Load, Save, Undo, Redo
The Australian government was looking for mandatory negotiations with media companies, forcing them to pay for content. They relaxed that "mandatory" clause a bit and added longer periods for notification and negotiation.
In the past year, Facebook has signed revenue-sharing deals with most of the major news platforms in Australia (ongoing) and on Monday of this week, they announced they would be investing $15 million in regional news media. https://www.fool.com.au/2021/05/10/facebook-to-invest-15-mil...
Google has also signed contracts with some of the major media companies.
https://www.reddit.com/r/FluentInFinance/comments/n94az6/i_a...
We have already re-spun PCB designs to work in alternate ICs for some of the ones that we know will become unavailable; dual-footprint in case the originals come back. This took time and effort to design and verify and all that work could have gone into the design of new products, but it had to be done. This has put us some number of months behind our original planned dates for our new products.
The problem is that we can see shortages coming up which we cannot work around. We cannot buy enough parts, the lead-times are astonishing. At some point we are going to have to get lucky or halt production.
"Victims are ethically owed many things: recognition that what was done to them was indeed wrong, a credible indication that the society takes this seriously, an effort to identify, apprehend and punish the perpetrators, and compensation for their ongoing suffering and disadvantage. But beyond this, we have an obligation not to forget, and not to whitewash."
https://www.abc.net.au/religion/is-it-ethical-to-use-data-fr...
As for content, that's tough and I don't have an easy answer.
If that's not a good enough reason, I have a dumb hypothesis that mosquitos have played a part in evolution for millions of years, based on the premise that they spread viruses/retroviruses and retroviruses are capable of modifying DNA. They also spread other diseases which may cause certain genetic lines to survive over others. This hypothesis could be complete junk, but who is going to be able to run a scientific experiment that would take 10,000 years or more?
The food chain reason is immediately obvious, but is anyone considering the impact over massive timescales?
It's also the first true ARM/RiscOS laptop that has been made since the original Acorn A4. That machine was the first portable ARM device ever made.
Operating systems have been born and died between the arrival of these 2 machines.
For those who haven't used it and want to try it, you install "xpra" on your Linux box with "yum" or "apt", then fire up an xpra server with "xpra start" (or "nohup xpra start &"), then make a note of which extra display it has added (like ":1"). It's not replacing the display manager (as far as I'm aware).
Download a windows client from xpra.org, then connect through SSH. Once connected, you get a small icon in the Windows taskbar with lots of menu options. Under the "Start" option, you have sub-menus which give you access to all the Linux desktop programs on the target machine.
For example, I use XPRA to connect to my Ubuntu 20.04 laptop and run "Start -> Accessories -> Terminal Emulator". It opens an XFCE4 terminal on my Windows desktop, looking as if it was a native Windows application. In the terminal, I can type "thunar" and a new Thunar file manager window will open on the Windows desktop, or "xemacs" for a text editor.
It's very fast because it's only sending 1 window at a time, not the whole desktop. I can disconnect, then re-connect and the windows will re-appear as I had left them.
It's not perfect (some dialog boxes don't respond to mouse clicks), but it is worth playing with.
If you're going to try it, I do suggest having a trial run in small groups first because your browser may/may not be happy giving webcam/mic permissions. A few people had to switch to the Brave browser and give camera/mic/autoplay permissions before it worked.
Text Editor: There's a very nice article choosing a text editor, here: https://www.fpgarelated.com/showarticle/37.php
Simulation: ModelSim is the industry-standard simulator and (as someone has already mentioned here), there is a free version on the Intel (was Altera) web site. You will need to sign up to get the download. This version of ModelSim will let you run any design up to a certain number of lines of code, but it's plenty to get started with.
Xilinx Vivado has a built-in simulator, but I have spent most of my career using ModelSim, and I haven't had the need to switch. You also need to sign up to download Vivado; the free version is called Vivado HL WebPACK (Device Limited).
Synthesis and Place/Route: Synthesis turns your HDL code into a netlist which uses the primitive logic blocks of the FPGA that you're targeting and defines how they are logically connected to each other. Place and Route takes those blocks, finds a place for them to go in the FPGA and tries to connect them up so that the logic delay from one flip-flop (through combinatorial logic + wire delays) to the next flip-flop will meet your target clock speed.
When it comes to seeing what your HDL code will turn into once it's been put into an FPGA, I find that Xilinx have the most advanced FPGA toolchain (Vivado) with some excellent visualisation features for learners. Stay away from Vivado HLS for now; if you want to learn HDL code, the HLS tool is a distraction that won't teach you core HDL design concepts. Vivado does not support Spartan-6 parts; only 7-series and newer.
Using Vivado, take a sample piece of code and try running it through synthesis (don't place/route yet). Look at the result in the schematic viewer. Look at the hierarchy viewer, too. Try to trace a line in the source code to its synthesised result. Once you're happy that you can do this, try running place/route (Run Implementation). You can cross-probe from the schematic view to the chip view and highlight wires and blocks with your choice of bright colours. Take a look at how the schematic primitive blocks end up getting placed and routed in the chip.
Note: If you don't care about connecting up I/O pins in Vivado and you just want to see what a small bit of logic looks like, you can specify "-mode out_of_context" under "Project Manager -> Settings -> Project Settings -> Synthesis -> Options -> More options".
Advanced Stuff: Anyone can make an FPGA design work at 10MHz or 20MHz, so try something harder. Start off by setting a slow clock speed constraint (50MHz), then try increasing the speed in 50 or 100MHz increments until you hit 300MHz (400MHz or 500MHz if you're adventurous). When does your timing fail? What do you need to do to your logic to make it meet timing?