A new Notice of Proposed Rulemaking (WC Docket No. 26-82) appeared in the Federal docket today. The FCC 'tentatively concluded' that national security risks extend to existing infrastructure. Consequently, they are seeking comment on a new process to retroactively revoke operating authority for companies already on the Covered List. This would close the 'legacy loophole,' legally barring the continued marketing and sale of previously approved hardware currently on retail shelves.
I think, for my use, just having the ability to write to DMA registers would have been a big advantage. It feels wasteful to have A DMA waiting on a FIFO just to write what it gets to DMA registers to do the transfer you actually wanted.
Looking at the Architecture diagram It seems like it could have allowed that and stayed on the same side of the AHB5 splitter.
SDRPlay is using Avalonia for its SDRConnect desktop UI. That's the one native application based on Avalonia I've spent significant time in.
It's ok. I give it pretty high marks. There is a good deal of "lowest common denominator" in it, naturally due to cross platform abstraction. But, it's generally nice, and commercial licenses are affordable.
> And what does the customer do if the vendor has discontinued it? Or charges for an upgrade? Or has gone out of business?
Those can all be filed under Not My Problem (as in, Microsoft's problem,) and safely ignored. On the other hand, when Highly Influential So-And-So upgrades from 3.1 to 95 or whatever, and Very Population Application v4.9.6 starts falling over, Microsoft gets the black eye whether they deserve it or not. The whole equation changes.
Or you desperately need to tag some system object and the system provides no legitimate means to do so. That can be invaluable when troubleshooting things, or even just understanding how things work when the system fails to document behavior or unreasonably conceals things.
I've been there and done it, and I offer no apologies. The platform preferred and the requirements demanded by The Powers That Be were not my fault.
One workaround Microsoft has done for use-after-free is detecting when an application is prone to this and using an allocator that doesn't actually free RAM immediately. It believe that lovely bit of fun is a function of "Heap Quarantine".
Yes, the real, can't say no world of system software is not what one might wish.
"For example, the ASL code published through the A-Profile Arm Architecture Reference Manual, Exploration Tools downloads for A-Profile, or the Armv8-M Architecture Reference Manual."
I hadn't noticed that... wonder if it's new. Just downloaded the Armv8-M ARM (nice acronym) and... this might be helpful, but man extracting this stuff from a PDF seems error-prone and the wrong way to do it.
I suspect you've believed that this didn't exist due to the predominance of pre-Armv8-M devices in the market: there is no ASL for Armv7-M and earlier, and devices based on these older cores remain extremely common (STM32F1x, etc.) The good news is this is changing as new devices appear. The bad news is there probably will never be ASL published for older cores.
reply