From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] rpi3 wifi
Date: Fri, 16 Oct 2020 14:31:10 -0700 [thread overview]
Message-ID: <CAHwi9bzvGccbYZhvE4M3q-M3B_rYcZQtGNsXSrG7A7Ue74Cymw@mail.gmail.com> (raw)
In-Reply-To: <95EAD3571F321A2E03AF2D2A7E8BCCEB@hera.eonet.ne.jp>
I managed to boot over tls "manually," here is how I did it:
127 holes free
0x0047e000 0x191e6000 416710656
416710656 bytes free
Plan 9 from Bell Labs
board rev: 0xa02082 firmware rev: 1590181998
cpu0: 1200MHz ARM Cortex-A53 r0p4
fp: 32 registers, simd
fp: arm arch VFPv3+ with null subarch; rev 4
#l0: 4330: 10Mbps port 0x0 irq -1 ea 000000000000
998M memory: 402M kernel data, 596M user, 3576M swap
cpu1: 1200MHz ARM Cortex-A53 r0p4
cpu2: 1200MHz ARM Cortex-A53 r0p4
cpu3: 1200MHz ARM Cortex-A53 r0p4
ether4330: chip 43430 rev 1 type 1
ether4330: firmware ready
ether4330: addr ...
/dev/sdM0: BCM SDHost Controller
/dev/sdM0/data
/dev/sdM0/dos dos
/dev/sdM0/fscache cwfs64x
/dev/sdM0/fsworm
/dev/sdM0/nvram
/dev/sdM0/other
/dev/sdM0/plan9
bootargs is (tcp, tls, il, local!device)[local!/dev/sdM0/fscache] !rc
% factotum -u
user[glenda]:
% aux/wpa -2 -p -s ... /net/ether0
!Adding key: essid=... proto=wpapsk
password:
!
% ip/ipconfig
% bootargs is (tcp, tls, il, local!device)[local!/dev/sdM0/fscache] tls
user[glenda]:
fs address is? ...
auth address is? [...]
!Adding key: dom=... proto=dp9ik
user[glenda]:
password:
!
init: starting /bin/rc
...
I think the problem booting over tls automatically may be with the
wificrypt=wpa2 option. I looked in /sys/src/9/boot/net.rc and I don't
think it pays attention to this option, but aux/wpa needs the -2
option to work with this driver. all I have done so far was copy over
enough of Richard Miller's work with very slight changes just to get
it working at all... 9front has a wifi stack this driver doesn't use
at all, etc.
as far as the bcm64 kernel goes, I don't know if anyone has gotten
this working with it. khm and I both tried, but I eventually
encountered a problem with wlreadpkt returning a bad value I couldn't
get past. There must be some difference I can't find for getting it
working with a 64 bit kernel.
- Eli
next prev parent reply other threads:[~2020-10-16 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 5:26 Kurt H Maier
2020-10-13 12:16 ` [9front] " Eli Cohen
2020-10-16 3:42 ` kokamoto
2020-10-16 21:31 ` Eli Cohen [this message]
2020-10-16 22:52 ` kokamoto
2020-10-17 2:41 ` Eli Cohen
2020-10-17 2:49 ` ori
2020-10-17 5:52 ` kokamoto
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=CAHwi9bzvGccbYZhvE4M3q-M3B_rYcZQtGNsXSrG7A7Ue74Cymw@mail.gmail.com \
--to=echoline@gmail.com \
--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).