- CIX P1/CD8180 + 32 GB RAM with 30 TOPS integrated NPU
- Houmo M50 + 48 GB RAM with 160 TOPS INT8
Anyone know more?
3,422 karma · joined January 24, 2011
- CIX P1/CD8180 + 32 GB RAM with 30 TOPS integrated NPU
- Houmo M50 + 48 GB RAM with 160 TOPS INT8
Anyone know more?
Toggling it again to turn it off immediately after (which I assume most people will miss) seems to guard against this.
Does anyone know if this is correct?
My approach is evolving due to NixOS and home-manager with vibe coding to do the lifting. I increasing lean on vibe coding to handle simple details to safely write shell scripts (escaping strings, fml) and C/C++ apps. The complexity is minimized, allowing me to almost one-shot small utilities, and Nix handles long-term maintenance.
With NixOS, a simple C/C++ application can often replace a Python one. Nix manages reading the source, pulling dependencies, and effectively eliminating the overhead that used to favor scripting languages while marking marginal power savings during everyday use.
Docs at `man gethostbyname`
Here's an example:
> cat hosts
198.51.100.33 test.tld
2001:db8::33 test.tld
198.51.100.12 test4.tld
2001:db8::12 test6.tld
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts getent ahosts test.tld
198.51.100.33 DGRAM test.tld
198.51.100.33 STREAM test.tld
2001:db8::33 DGRAM
2001:db8::33 STREAM
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts getent ahosts test4.tld
198.51.100.12 DGRAM test4.tld
198.51.100.12 STREAM test4.tld
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts getent ahosts test6.tld
2001:db8::12 DGRAM test6.tld
2001:db8::12 STREAM test6.tld
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts curl -v test.tld
* Host test.tld:80 was resolved.
* IPv6: 2001:db8::33
* IPv4: 198.51.100.33
* Trying [2001:db8::33]:80...
* Trying 198.51.100.33:80...
[0] https://cwrap.org/nss_wrapper.htmlThis looks like a great project!
yourname+servicename@gmail.com
From my experience, many (bad) websites consider "+" an invalid character and prevent you from using the address in this form.
Smart spammers can just strip the service name since it works the same for all Gmail users.
Really need dedicated addresses like Fastmail's Masked Addresses.
I wonder how readily things like this are known within the HW security community?
Some earlier HN discussion here [0]
> By using the newly introduced dm-writecache device mapper Linux kernel module
Looked for a publication date, but nothing anywhere on the page other then timestamps in the command output mentioning 2019. Wayback machine confirms this as well[0]
[0] https://web.archive.org/web/20191124065801/https://www.admin...
> Intel's internal tests show that the 0x12B update does not noticeably affect performance. Benchmarks and gaming tests, including popular titles like Cyberpunk 2077 and Shadow of the Tomb Raider, showed results within normal expected variations when compared to the earlier 0x125 update.
I loaded the page expecting to see some arbitrary binary data version control tool and was caught off guard by all the references to SQL.
If you select lockdown you'll be required to use a pin or password to unlock the phone.
I actually mean that the service need not care if it's in the cloud or on-premise as opposed to whose cloud. Many of my services don't need to do anything in the cloud.
If you look at things like awesome-selfhosted[0] you'll see that this is the prevailing expectation of things describing themselves as "self-hosted".
[0] https://github.com/awesome-selfhosted/awesome-selfhosted
Was excited to hear about self-hosted secrets management, but expected "self-hosted" to mean I can host anywhere, but the depends specific AWS features.
Perhaps "unmanaged" is a more appropriate term.
Unfortunately from the article it's hard to tell anything from power consumption other then the Snapdragon X Elite 8 has a roughly 28W "TDP" and that the Elite A has 80W "TDP" and is only slightly faster. Still, this doesn't translate to real world power usage.
I'd love to see a real world benchmark that measures actual power consumption of these chips.
Really feel that should've made it to the title other it feels like click bait.
Google has created a self fulfilling prophecy.
* RISC-V CPU: 4x 64-bit RV64GC application cores & 1x 64-bit RV64IMAC monitor/boot core
* FPGA: 23K logic elements (4-input LUT + DFF), 68 Math blocks (18×18 MACC), and 4 SerDes lanes of 12.7 Gbps.
[0] https://www.beagleboard.org/blog/2023-11-02-beaglev-fire-ann...
Upstream commit is here[1]
Glad to see it has been root caused and worked around in such short order.
[0] https://news.ycombinator.com/item?id=37812556
[1] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/...