From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] Is the vanilla Plan 9 still alive?
Date: Wed, 27 Nov 2019 08:02:51 +0900 [thread overview]
Message-ID: <18E311E8F13C5A43E5B81B16963BC6D9@hera.eonet.ne.jp> (raw)
In-Reply-To: 5ed6982d452fccf747b6db751a136f8f@hamnavoe.com
Thank you very much Richard san.
> Yes, it does with my two routers (buffalo n300 and fritz!box).
I'm using NEC WARPSTAR WR8170N router, and got the error like:
I compiled 9pi3wifi by using your pi3wifi definition file.
Plan9 from Bell Labs
board rev: 0xa02082 firmware rev: 1521643642
cpu0: 1200MHz ARM Cortex-A53 r0p4
...
#l1: 4330: 10Mbps port 0x0 itq -1: 000000000000
998M memory: 202M kernel data, 795M user, 3780M swap
...
ether4330: chip 43430 rev 1 type 1
ether4330: firmware ready
ether4330: addr <my rpi3's MAC address>
...
user[none]: sys
ether4330: [?] error status 23 flags 0x1 reason 0
event:
10 18 00 01 00 02 00 00 00 00 00 17 00 00 00 00
00 00 00 01 00 00 00 03 00 00 00 00 00 3a 9d 2b
b6 51 77 6c 30 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
event:
10 18 00 01 00 02 00 00 00 00 00 17 00 00 00 00
00 00 00 01 00 00 00 03 00 00 00 00 34 3d c4 ee
1e 68 77 6c 30 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
Kenji
next reply other threads:[~2019-11-26 23:02 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 23:02 kokamoto [this message]
2019-11-27 8:09 ` Richard Miller
-- strict thread matches above, loose matches on Subject: below --
2019-12-09 5:27 kokamoto
2019-12-09 4:05 kokamoto
2019-12-09 4:00 kokamoto
2019-12-09 4:34 ` ori
2019-12-09 8:06 ` Richard Miller
2019-11-27 10:04 kokamoto
2019-11-27 9:44 kokamoto
2019-11-26 9:46 kokamoto
2019-11-26 14:49 ` Richard Miller
2019-11-24 17:32 ori
2019-11-24 23:40 ` Fazlul Shahriar
2019-11-25 8:47 ` David du Colombier
2019-11-25 23:41 ` Steven Stallion
2019-11-26 7:04 ` David du Colombier
2019-11-24 16:30 ori
2019-11-24 17:07 ` David du Colombier
2019-11-24 18:37 ` David Butler
2019-11-24 17:34 ` David L. Craig
2019-11-25 8:39 ` Richard Miller
2019-11-22 23:15 sl
2019-11-22 23:36 ` greemngreek
2019-11-23 3:49 ` Skip Tavakkolian
2019-11-23 9:29 ` Richard Miller
2019-11-23 14:24 ` Steven Stallion
2019-11-23 14:33 ` Aram Hăvărneanu
2019-11-23 14:57 ` Lucio De Re
2019-11-23 17:15 ` Skip Tavakkolian
2019-11-23 18:14 ` Federico Benavento
2019-11-23 18:24 ` hiro
2019-11-23 20:17 ` Kurt H Maier
2019-11-23 20:27 ` Kurt H Maier
2019-11-23 22:35 ` Steven Stallion
2019-11-23 22:43 ` hiro
2019-11-23 22:44 ` hiro
2019-11-24 2:03 ` Kurt H Maier
2019-11-24 6:34 ` Lucio De Re
2019-11-24 7:54 ` Kurt H Maier
2019-11-24 20:32 ` Ori Bernstein
2019-11-25 3:32 ` Lucio De Re
2019-11-25 4:01 ` Lucio De Re
2019-11-25 7:52 ` Richard Miller
2019-11-23 23:08 ` Ori Bernstein
2019-11-23 23:46 ` Skip Tavakkolian
2019-11-24 8:53 ` Richard Miller
2019-11-24 12:41 ` hiro
2019-11-23 18:11 ` hiro
2019-11-24 6:50 ` Lucio De Re
2019-11-23 19:00 ` Kurt H Maier
2019-11-22 6:29 greemngreek
2019-11-22 6:44 ` [9fans] " Nick Owens
2019-11-22 7:42 ` Fazlul Shahriar
2019-11-22 8:00 ` greemngreek
2019-11-22 8:24 ` Richard Miller
2019-11-22 8:53 ` Skip Tavakkolian
2019-11-22 14:55 ` Don A. Bailey
2019-11-22 15:12 ` Jens Staal
2019-11-22 15:30 ` Steven Stallion
2019-11-24 4:40 ` Bakul Shah
2019-11-24 5:25 ` greemngreek
2019-11-24 6:13 ` Bakul Shah
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=18E311E8F13C5A43E5B81B16963BC6D9@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9fans@9fans.net \
/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).