Message-ID: <63aa2140@news.ausics.net> From: not@telling.you.invalid (Computer Nerd Kev) Subject: Re: Is It Time To Replace SSH ??? Newsgroups: comp.os.linux.misc References: <87r0x0xmre.fsf@usenet.ankman.de> <87mt7mwyvl.fsf@usenet.ankman.de> <871qoywh67.fsf@usenet.ankman.de> <63a68225@news.ausics.net> User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i586)) NNTP-Posting-Host: news.ausics.net Date: 27 Dec 2022 08:33:37 +1000 Organization: Ausics - https://www.ausics.net Lines: 29 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.misc:36607 26C.Z969 <26C.Z969@noaada.net> wrote: > On 12/23/22 11:37 PM, Computer Nerd Kev wrote: >> 26C.Z969 <26C.Z969@noaada.net> wrote: >>> >>> The sad thing about PI's isn't their capabilities, but >>> the POWER CONSUMPTION. That severely limits them for >>> "off grid" uses. Less impressive units like BeagleBone's >>> and esp Arduino's let you turn off basically every >>> peripherial until it's needed, and then cut it off again. [snip] >> Also if you set code running on the GPU, it continues going after >> the CPU is shut down (with access to GPIO signals), at which >> time the board only pulls 50mA (0.25W). If you worked really hard >> you could probably get the GPU to "wake up" the CPU roughly like >> microcontroller sleep-modes, based on the (incomplete) open-source >> GPU firmware for the Pis which needs to start up the CPU at >> power-on anyway. > > I had considered using a microcontroller to wake up a Pi > when needed - and for some kinds of apps that might be > reasonable. What I was doing, no, just stick with > microcontroller-based hardware in the first place. For what you were doing you didn't need any of the Pi's features anyway, so I'm not sure why you were sad that you couldn't use one. -- __ __ #_ < |\| |< _#