9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] bounty for 9pi update for 9front
Date: Fri, 14 Sep 2018 13:29:21 +0100	[thread overview]
Message-ID: <1536928161.991441.1508034536.1B666595@webmail.messagingengine.com> (raw)
In-Reply-To: <73056CCE-BB9C-46D6-B826-3659B3AE1494@yahoo.ca>

On Thu, Sep 13, 2018, at 6:40 PM, Chris McGee wrote:
> I had only wireless and minimal peripherals on my pis (keyboard and 
> mouse). I tried different power supplied including battery power to rule 
> out bad power or noise. I could reproduce the problem on both pi2 and 
> pi3 quite reliably and also two other people noticed it too. Pi1 worked 
> fine though.
> 
> The symptom was very strange phantom keyboard key presses and button 
> clicks. They would start at random points in time and even sometimes 
> during boot. I traced it all of the way to the USB debugging the HID 
> packets. At the lowest level it appeared as though the keyboard was 
> actually sending Shift-Ctrl-A/B keypresses. I was expecting some kind of 
> memory corruption type problems due to mulicore but it didn’t seem so.
> 
> I think I finally threw in the towel once I saw that even raspbian/Linux 
> have USB hacks abound and state on their website that not all USB 
> devices may work with it. That and the lack of any good hardware specs 
> on how the controller works.
> 
> I’m now in search of better hardware and left with a bad impression of 
> raspberry pi and USB itself. I hear from some hardware folks that PCIe 
> and Ethernet are much better and Thunderbolt is a dumpster fire. Maybe 
> there will be a riscv dev board soon.

I had a bad impression of the Raspberry Pi from the beginning.  I sort-of assumed Pi 2 & 3 were better due to sheer mass of peer pressure, but, well, thanks for stating the facts before I bought one.  I just can't understand the demented hurricane of enthusiasm generated by these garbage fire computers!

You know what?  When I publish my own OS (ha ha), I'll put a filter into the mailing list (when I get around to it), catching all messages mentioning Raspberry Pi or RPi to insert something like,  "WARNING!  This email mentions Raspberry Pi!  It may be trying to suck us into the demented maelstrom of enthusiasm generated by these garbage fire computers.  Exercise caution and critical thinking.  Remember the principles of rational development." XD

In a different humour, would it make sense to bit-bang ps/2 interfaces with the RPi's GPIO pins?  Or other serial interfaces.


  reply	other threads:[~2018-09-14 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  5:27 Antoni Sawicki
2018-09-13  0:47 ` [9front] " Chris McGee
2018-09-13  6:10   ` Steve Simon
2018-09-13  8:07     ` hiro
2018-09-13 10:18       ` Antoni Sawicki
2018-09-13 12:13       ` Steve Simon
2018-09-13 13:29 ` Julius Schmidt
2018-09-13 15:01   ` Steve Simon
2018-09-13 17:40     ` Chris McGee
2018-09-14 12:29       ` Ethan Gardener [this message]
2018-09-14 13:39         ` Steve Simon
2018-09-14 15:25           ` Ethan Gardener
2018-09-13 20:29   ` Antoni Sawicki
2018-10-21 23:45 cinap_lenrek
2019-01-10 17:55 sl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1536928161.991441.1508034536.1B666595@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).