From: "岡本 健二" <kokamoto@hera.eonet.ne.jp>
To: 9front@9front.org
Subject: Re: [9front] rpi kernel silliness
Date: Fri, 24 Feb 2017 14:16:21 +0900 [thread overview]
Message-ID: <788E7C0E-7E75-4771-A741-D4C51AFF44E9@hera.eonet.ne.jp> (raw)
In-Reply-To: <alpine.LNX.2.00.1702231933590.4258@phi>
Regarding this, I sent a mail to sirnewton_01, but my mail was rejected due to our network
provider’s problem.
I’ll write here it instead (sorry sirnewton_01).
It’s danger to use new 9pif image for pi3 module.
We discussed a problem of strange behavior of keyboard input, and guessed some
problem in usb driver for the rpi3. I’m using 9pif2 image on root from tcp mode.
I found this does not restricted only to keyboard, but extended to MicroSD Ram itself.
I corrupted two new MicroSD ram cards when I tried to wrote a large file such as
new 9pif image. This is very dangerous, because the damaged card cannot be
repaired.
Kenji
PS. of course, it’s very dangerous to use it as cpu server. :-)
> 2017/02/24 3:35、Julius Schmidt <aiju@phicode.de>のメール:
>
> why do we have pif and picpuf kernels when you can just use service= in plan9.ini? there are also some random stupid changes in pif vs picpuf (like gpio is gone in the cpu server)
>
> aiju
prev parent reply other threads:[~2017-02-24 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 18:35 Julius Schmidt
2017-02-24 5:16 ` 岡本 健二 [this message]
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=788E7C0E-7E75-4771-A741-D4C51AFF44E9@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--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).