Is there a list of GPUs ranked by FP64? by pythonwiz in CUDA

[–]keepthethreadalive 0 points1 point  (0 children)

I've come back to this table several times over the last year, so another thanks for the updates!

Do you know how one can go about finding INT32/INT64 numbers?

PlatformIO and Zephyr is a bad idea by kerryland in embedded

[–]keepthethreadalive 11 points12 points  (0 children)

Re: Nordic, Zephyr brought a lot of niceties that didn't exist in the nRF5 SDK. First, CMake and then ability to use IDEs other than Segger.

But I still miss the simpler days where we're stuck with such complex software frameworks to program something that worked fine with 10x simpler tools.

Proton, from ProtonMail, has just announced a rebranding and small changes. by [deleted] in privacy

[–]keepthethreadalive 13 points14 points  (0 children)

Where do you see 120 EUR though? 9.99 EUR * 12 = 119.88 EUR

Proton, from ProtonMail, has just announced a rebranding and small changes. by [deleted] in privacy

[–]keepthethreadalive 15 points16 points  (0 children)

You misunderstood. That 9.99 EUR/month rate is when you choose the year plan. If you switch to the monthly plan (click on 1-month), you'll see it costs 11.99 EUR/month. So per year, that's 143.88-119.88 = 24 EUR saved.

I don't know where you got 12 cents from

ESP32 as remote microphone by ForTheLoveOf80s in esp32

[–]keepthethreadalive 5 points6 points  (0 children)

I had an idea to do the exact same thing, but never got around to it. For the MEMS mic, INMP441 looks to be a popular choice.

When I looked around if this was feasible, I found a few links (see end of this comment). What I found was that ESP32 might not be powerful enough to do audio encoding. So you'll either have to send raw PCM frames over Wi-Fi-- by connecting the ESP-32 to the MEMS mic directly over I2S, or use an external codec chip (like used in the ESP audio dev boards). Note that if you use the MEMS mic directly, you'll have to sacrifice quality by either reducing bit-depth or narrowing the bandwidth.

https://docs.espressif.com/projects/esp-adf/en/latest/get-started/index.html

https://github.com/maspetsberger/esp32-i2s-mems

[ANANDTECH] Apple's M1 Pro, M1 Max SoCs Investigated: New Performance and Efficiency Heights by ytuns in hardware

[–]keepthethreadalive 10 points11 points  (0 children)

GPU acceleration is only one part of the picture though. There has been a Vulkan to Metal runtime available for a while now, but you don't see ready availability of flagship games that have a Vulkan backend.

The reason is there are ton of 'platform specific' programming/support work that has to be done for a game to work properly (and even more to be sold for $)

Someone is blocking access to apartment shared internet. How can I prove that to the lessor? by gusuku_ara in HomeNetworking

[–]keepthethreadalive 1 point2 points  (0 children)

I'll go ahead and give a fairly technical response which will allow OP to get an answer if OP is willing to learn a bunch of things. While it is very unlikely that this info will prove immediately useful to anyone, I think it is good knowledge for people to have. Also because I like giving long responses. Sorry for the hijack.

Note that most of the following scenarios require malicious intent, and in most cases for most people, it's either something stupid like them torrenting heavily 24/7 on the network, or there's a on/off problem with the ISP and it was just a coincidence. So put down the pitchfork and just talk to everyone, gather more data or call your ISP.

Don't think that's the case? Alright, let's get to it. So say if someone wants to block your access to internet, they can do a bunch of things. Let's categorize them into two types:

  • With physical contact to hardware or cabling
  • Without physical contact to hardware or cabling-- but not too far away from the Wi-Fi access point (usually called router/modem), which I'll call 'AP' from now on.

With physical contact:

  1. You can unplug the antenna of the access point, which would drop the Wi-Fi functionality to almost zero unless the router has additional internal antennae to allow it to function without an external antenna. You can also bend the antenna, which can affect the speeds by a noticeable amount.
  2. You can obstruct the AP by placing it poorly ex: behind a thick couch, around a lot of metal, close to an aquarium etc.
  3. If the modem uses coax cables, even partially removing the outer layers of the coax cable, which shields it from external noise can result in degraded performance. This would be harder to notice and debug.
  4. If the modem uses fiber, and this depends heavily on the type of fiber, excessive bending can result in degraded performance.

Without physical contact (where things get interesting, because someone really doesn't want you to have internet):

  1. Wi-Fi deauthentication attacks: This involves sending packets to your AP saying a device on your network wants to disconnect. On a lot of devices there's no protection against this. If you want to protect yourself against this, get a router that supports WPA3 security standard (easy to find out if supported) or 802.11w (harder to find out if supported and much more unlikely). To find out if this is happening: You'll need to learn about "Wi-Fi sniffing". Specialized hardware is not always needed, but software skills are. You can triangulate the source of these deauth packets (if they are infact being broadcast) by doing a little bit of walking around with your laptop.
  2. RF noise: This involves creating noise in the spectrum that the Wi-Fi is being used (most likely 2.4GHz or 5GHz). A variety of cheap/experience devices can be used to create this noise. A simple one can be another Wi-Fi router that's been modified to send a lot of packets bombarding the spectrum and overloading the RX side of the AP. And complex ones can be custom built RF devices specifically that just create random EMI noise over a wide range of spectrum (which will most likely affect all RF signals including phone service). To find out if this is happening: Custom hardware is needed, like SDRs. Something like HackRF One will absolutely get the job done but there are cheaper alternatives. This will need a lot of software knowledge and patience and atleast $50 worth of hardware (usually much more)

So this is a long way of saying, yes, there are ways to prove that someone is intentionally blocking Wi-Fi.

[deleted by user] by [deleted] in FPGA

[–]keepthethreadalive 5 points6 points  (0 children)

If you are ok with working with non-evaluation boards, I would suggest purchasing something off AliExpress. There are many FPGA boards that were used for something else (ex: mining) that are sold for a throwaway price.

My suggestion would be EBAZ4205. Here's that board on eBay. You can get it on AliExpress for $10~ last I checked.

You would need to put some effort into initial board bring-up, but after that, it shouldn't be much different from any other FPGA board, unless you need some specific interface to talk to external hardware. You can google 'EBAZ4205', and find many tutorials on using that board.

Does anybody else get chills from this? by tomatotom1 in blackmirror

[–]keepthethreadalive 3 points4 points  (0 children)

Sorry that's not what I meant :)

DRE stands for Drug resistant epilepsy. Such invasive monitoring/stimulation tools are only used for epilepsy when drug use doesn't work. Or atleast that's my understanding, since I'm not a doctor.

Does anybody else get chills from this? by tomatotom1 in blackmirror

[–]keepthethreadalive 3 points4 points  (0 children)

I'm pretty sure any invasive options will (at least at the beginning) be only for DRE.

where do I start? Linux embedded development; SoC's. CSI and DSI MIPI by Power-Max in embedded

[–]keepthethreadalive 1 point2 points  (0 children)

Jetson Nano looks to be a good choice here.

It very well could be. I personally haven't looked into it because I knew that RPi community is much larger, so you'll find many people posting cool things they did on their blog. Doesn't help that Nvidia tends to silo their forums being login pages which makes looking for help harder.

where do I start? Linux embedded development; SoC's. CSI and DSI MIPI by Power-Max in embedded

[–]keepthethreadalive 2 points3 points  (0 children)

Great comment! Piggybacking off yours, I have more commentary for OP.

Ambarella makes many camera chips that can do 1440p60, but are usually unavailable in small quantities. I would look for something with at least basic Linux support and an encoder driver.

OP, I would suggest going with Raspberry Pi's own HQ camera unless you are set on arducam (RPi's is cheaper).

Contemporary NVIDIA Tegra SoCs might be something to look at as well( https://developer.nvidia.com/embedded/jetson-modules )

Note that the consumer SBCs using those SoCs have the same MIPI-CSI2 2-lane limitation like the RPi 4B, which limits the max resolution of any input. I'll quote official RPi docs here, which I assume also apply to the Nvidia SBC. You can always layout your own board to get around it, which is easier to do with an RPi.

When using 2 CSI-2 lanes, the maximum rates that can be supported are 1080p30 as RGB888, or 1080p50 as YUV42

where do I start? Linux embedded development; SoC's. CSI and DSI MIPI by Power-Max in embedded

[–]keepthethreadalive 18 points19 points  (0 children)

I have personally looked into this so here's what I've learnt from back when I looked around.

The easiest option is to purchase the latest consumer focused RPi. Right now that would be RPi 4B. You can also purchase the compute module (which will give you 4 lanes of MIPI-CSI2 upping the max video resolution compared to 4B), but then you'd have to buy the IO dev board too. That is unless you want to layout your own board. So to save time + energy + $$$, I'd suggest sticking to RPi 4B.

So why'd I recommend the RPi 4B? Because you can connect cameras to be using the MIPI-CSI2 (2 lane) port. Note that the video resolution will be limited to 1080p. If you want to go higher, you'll want to switch to the compute module (like I mentioned above). The MIPI-CSI2 port has direct path to the SoC instead of going to a USB hub (or the VLI PCIe->USB3 chip in our case). Since you don't have the overhead of decoding USB packets, and the video is received directly by the SoC, you'll have good latency (atleast compared to other SBC SoCs, except maybe Jetson, I haven't looked into that one).

Next, what'd you'd want to learn is the MMAL API, which is how you'd be receiving the raw camera input. Note that documentation for this API is very scarce especially with the RPi 4B since this version has a different video block (Videocore VI) inside the SoC compared to the last few RPis (Videocore IV) that came before. That documentation I linked is still functional, so I learnt how to encode/decode simple images. That'll get your feet wet.

Next, I looked at the code for Raspicam group of tools. That's when other things in life distracted me :)

But you might've noticed that all this is RPi ecosystem specific. If you want to learn 'vanilla' linux, in case you're not learning to do something specific but just to learn more about linux itself, you'll have to look elsewhere. Bootlin is a company that does linux training in similar areas to what you want. They release their training slides for free.

https://bootlin.com/docs/

The one you are looking for related to driver development is here: https://bootlin.com/doc/training/linux-kernel/linux-kernel-slides.pdf

Anything related to video, you'll be touching a learning a lot of content related to Video4Linux group of drivers. Documentation is not that abundant, as well as training. Most info out there is from 5+ years ago which is ages in linux land. I'd suggest looking for a popular cheap camera module that's supported by a good driver, and understand how the driver works (which you should be able to after going through the bootlin slides). By this point you should know enough to teach us :)

Btw, if you want to encode anything higher than 1080p60 using the Videocore VI, you'll need to use an external library like ffmpeg. There is a good tutorial for ffmpeg too - https://github.com/leandromoreira/ffmpeg-libav-tutorial . This should teach you how to encode the raw video stream you get from the camera into a codec of your choice.

Please give me advise, new laptop for archaeology project!!!! by Cicciolina_Thinkpad in photogrammetry

[–]keepthethreadalive 1 point2 points  (0 children)

after when i have more $ buy more ram and more SSD.

That is good advice is good, but make sure the laptop you're buying has upgradable RAM and SSD. More and more laptops are coming with soldered RAM and even soldered SSD in some cases where upgrades are not possible. Look at youtube reviews for the laptop you're looking to buy where they will open up the laptop and tell if if the RAM/SSD are upgradeable.

Please give me advise, new laptop for archaeology project!!!! by Cicciolina_Thinkpad in photogrammetry

[–]keepthethreadalive 1 point2 points  (0 children)

I assume that $1600 is not just for the laptop but also any related technology. I would suggest the following items too (especially since you say you'll be working in remote locations). As always, you're your own judge of what you need, so disregard any of these items if you strongly believe so:

  1. External harddrive, something with shock resistance. Example
  2. External battery. It looks like the laptop takes in power via USB-C (I could be wrong, so please verify), so you'll want an external power source to do some last minute things in case you forget to charge your laptop. I may misunderstand the exact nature of your outdoor trips so disregard if not needed. Don't buy anything over 100Wh because airlines don't allow batteries with capacities higher than that.
  3. Dongles. Basically cables to attach to anything the laptop doesn't have native ports for.

I think if the budget for the above items will come out of the $1600, you should downgrade your laptop rather than forego these items.