From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cmo-0001.xspmail.jp ([202.238.198.170]) by ewsd; Sun Nov 17 18:34:23 EST 2019 Received: from cmr-0002.xspmail.jp ([202.238.198.119]) by cmo with ESMTP id WTwCiDo9eajWUWU3fir7k6; Mon, 18 Nov 2019 08:34:19 +0900 Received: from pi3L.jitaku.localdomain ([180.146.252.131]) by cmr with ESMTPA id WU3fiNkHbWSOFWU3fiVlko; Mon, 18 Nov 2019 08:34:19 +0900 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hera.eonet.ne.jp; s=x01; t=1574033659; i=kokamoto@hera.eonet.ne.jp; bh=+EBzSe3l0iNN8UbzO39uMVZ6i35Qce5sGp5C9q7+R2o=; h=To:Subject:Date:From:In-Reply-To; b=HUvQFjpOH059lBcOoZ0KC/K9fvXQJ/3ieKtfqObjCfQ7/JB6kij2E5vAo44DzoKd+ ++yWh83F7/6rMEuSByiMXDpn8u1X4fqOiHDJfWN+GFYFWtEQ9H6v9qfX/JEWLG+E04 mzgf2dvx7NISd6I/zUcAnNeH+MaRmW9CkGxPKg24d3EjSQpyvfrXy+A2XjWyZZ0+Fs KxvKILpXEb0c01KVpO1ulnarh5q4iIr5AG0rGmUsRvyQ3Z9RLReRCeIAvpOA/BmYeg cqK8ta7r/zO1u5Mbsdh+PV3sNmu8g7zSwcng7qEWwNRHv1NuextkMlTEYWnHSSUOhM FxmP1knypWK9Q== Message-ID: <084F4A7EE0E9E2857F726BB3B79BA544@hera.eonet.ne.jp> To: 9front@9front.org Subject: Re: [9front] unofficial sdcard image for raspberry pi 4 testing Date: Mon, 18 Nov 2019 08:34:17 +0900 From: kokamoto@hera.eonet.ne.jp In-Reply-To: 966798852513255AE0B6121DF6590C73@felloff.net MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-rotfqjfkhdnvpvfzriqkqnaihc" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: patented ACPI over ORM pipelining-aware high-performance backend This is a multi-part message in MIME format. --upas-rotfqjfkhdnvpvfzriqkqnaihc Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit >but the goal should be to have the raspberry pi wifi driver expose >a compatible interface to aux/wpa. I know your way, and agree with you. I'm now trying to have a working model for rpi3 wifi network. I first tried to port it into 64bit /sys/src/9/bcm64 with your port/wifi.c. It is very complicated, one is related to 32bit/64bit difference where I have to know the hardware knowledge of rpi3 completely. To combine the Richard's driver with port/wifi.c is based on above assumption that I know rpi3 hardware deeply, such as gpio etc... It's not possible to me now, so I abandoned this course temporally. A more combenient course to me is take the Richard's codes with small changes as possible as, and have a working model at first. After make it done, I'll return to the course you suggested. This is my roadmap for making rpi3 wifi network here. Kenji PS. I can't find your new net.rc on 9front tree. I can find only the same net.rc as my /sys/src/9/boot/net.rc. --upas-rotfqjfkhdnvpvfzriqkqnaihc Content-Type: message/rfc822 Content-Disposition: inline Return-Path: 9front-bounces@ewsd.inri.net Received: from cmi-0000.m.xspmail.jp (LHLO cmi-0000.xspmail.jp) (100.120.21.1) by zmbs-0041.m.xspmail.jp with LMTP; Mon, 18 Nov 2019 03:34:06 +0900 (JST) Received: from ewsd.inri.net ([107.191.116.128]) by cmi with ESMTP id WPN6iLMJQR4JzWPN6iyYRa; Mon, 18 Nov 2019 03:34:05 +0900 X-Country-Code: US Authentication-Results: cmi-0000.xspmail.jp; dmarc=none header.from=felloff.net; x-token-a=none; x-token-b=none Received-SPF: PASS identity=mailfrom; envelope-from="9front-bounces@ewsd.inri.net" Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Sun Nov 17 13:33:51 EST 2019 Message-ID: <966798852513255AE0B6121DF6590C73@felloff.net> Date: Sun, 17 Nov 2019 19:33:41 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: 97C9B1C68E00FDE011306B2CA8588800@hera.eonet.ne.jp MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: structured lossless wrapper software SQL rich-client-based framework base Subject: Re: [9front] unofficial sdcard image for raspberry pi 4 testing Reply-To: 9front@9front.org Precedence: bulk i pushed a net.rc change now which lets you set the wpa password in plan9.ini so there wont be a prompt. i currently have no wireless network nor a monitor for raspberry pi to help kenji with his attempt on getting millers wifi driver ported. but the goal should be to have the raspberry pi wifi driver expose a compatible interface to aux/wpa. and i dont want to maintain two completely separate boot methods for raspberry pi. putting wifi keys in the kernel is just wrong. we want ONE sdcard image, that you might configure by editing plan9.ini, but thats it. no kernel recompile just for setting up wifi. -- cinap --upas-rotfqjfkhdnvpvfzriqkqnaihc--