[-- Attachment #1: Type: text/plain, Size: 160 bytes --] Now that RPI3 is generally available, I'm wondering if there are any efforts underway to port Plan 9 to it. I would like to help in any way I can. -Skip [-- Attachment #2: Type: text/html, Size: 258 bytes --]
> Now that RPI3 is generally available, I'm wondering if there are any > efforts underway to port Plan 9 to it. "Underway" might be a bit ambitious since it was only announced today. I've ordered one to have a play with. > I would like to help in any way I > can. Finding a programming manual for the BCM43438 wifi/bluetooth chip would be a good start. Incidentally I can confirm that the Raspberry Pi Zero runs Plan 9 happily.
On Mon, 29 Feb 2016 20:28:04 GMT Richard Miller <9fans@hamnavoe.com> wrote:
> > Now that RPI3 is generally available, I'm wondering if there are any
> > efforts underway to port Plan 9 to it.
>
> "Underway" might be a bit ambitious since it was only announced today.
> I've ordered one to have a play with.
>
> > I would like to help in any way I
> > can.
>
> Finding a programming manual for the BCM43438 wifi/bluetooth chip would
> be a good start.
>
> Incidentally I can confirm that the Raspberry Pi Zero runs Plan 9 happily.
In theory one should be able to run the standard 9pi image on
pi3.
10-12 years ago FreeBSD had "project Evil" for an NDIS shim
layer that allowed use of windows network drivers on FreeBSD.
Has anyone considered writing a shim that allows use of a
FreeBSD driver with plan9?
> 10-12 years ago FreeBSD had "project Evil" for an NDIS shim
> layer that allowed use of windows network drivers on FreeBSD.
> Has anyone considered writing a shim that allows use of a
> FreeBSD driver with plan9?
i looked at that a bit, and was not convinced that the surface area was manageable
- erik
[-- Attachment #1: Type: text/plain, Size: 623 bytes --] What about NetBSD drivers? As I understand it the Rump project provides a clean way to run NetBSD drivers in different environments. I guess the bigger problem here is be getting them past the compiler? On Mon, 29 Feb 2016, 22:48 erik quanstrom, <quanstro@quanstro.net> wrote: > > 10-12 years ago FreeBSD had "project Evil" for an NDIS shim > > layer that allowed use of windows network drivers on FreeBSD. > > Has anyone considered writing a shim that allows use of a > > FreeBSD driver with plan9? > > i looked at that a bit, and was not convinced that the surface area was > manageable > > - erik > > [-- Attachment #2: Type: text/html, Size: 895 bytes --]
On Tue, Mar 1, 2016 at 11:04 AM, Mark Lee Smith <netytan@gmail.com> wrote: > What about NetBSD drivers? What about them? NetBSD doesn't support the Pi3. What drivers do we want anyway? > As I understand it the Rump project provides a clean way to run > NetBSD drivers in different environments. I guess the bigger problem > here is be getting them past the compiler? It is unfeasible to use the Plan 9 toolchain for this. Not only is the C dialect different, and the assembly dialect completely different, but the code expects a certain calling convention provided by gcc and different from the Plan 9 calling convention. Doing a rump port with gcc, cross-compiling on Unix and running on Plan 9, should be easy though. -- Aram Hăvărneanu
On Tue, Mar 1, 2016, at 01:58 AM, Richard Miller wrote:
>
> Incidentally I can confirm that the Raspberry Pi Zero runs Plan 9
> happily.
Very nice to know that Richard. Is the image and the code available
somewhere?
--
Ramakrishnan
>> Incidentally I can confirm that the Raspberry Pi Zero runs Plan 9
>> happily.
>
> Very nice to know that Richard. Is the image and the code available
> somewhere?
The normal 9pi image runs on the zero too.
On Wed, Mar 2, 2016, at 02:40 PM, Richard Miller wrote:
> >> Incidentally I can confirm that the Raspberry Pi Zero runs Plan 9
> >> happily.
> >
> > Very nice to know that Richard. Is the image and the code available
> > somewhere?
>
> The normal 9pi image runs on the zero too.
Thank you. PiZero is not yet available in this part of the world, but
hoping that it will be available soon, along with Pi3.
--
Ramakrishnan
Getting Plan 9 to boot on the pi3 (in 32-bit mode) was almost trivial. Plan 9 from Bell Labs board rev: 0xa02082 firmware rev: 1456410415 cpu0: 1200MHz ARM Cortex-A53 r0p4 fp: 32 registers, simd fp: arm arch VFPv3+ with null subarch; rev 4 eMMC external clock 250 Mhz #u/usb/ep1.0: dwcotg: port 0X0 irq 9 992M memory: 200M kernel data, 792M user, 3762M swap cpu1: 1200MHz ARM Cortex-A53 r0p4 cpu2: 1200MHz ARM Cortex-A53 r0p4 cpu3: 1200MHz ARM Cortex-A53 r0p4 usb/hub... usb/ether... etherusb smsc: b827ebXXXXXX version...time... init: starting /bin/rc pi3# The "almost" is because the latest GPU firmware now initialises the ARM cores in HYP mode. This change seems to have been made in October, and affects the pi2 as well. Getting from HYP to SVC mode at boot time is no longer as simple as a MOVW into CPSR, and requires three new instructions that 5a doesn't know about ...
[-- Attachment #1: Type: text/plain, Size: 279 bytes --] On 3 March 2016 at 14:50, Richard Miller <9fans@hamnavoe.com> wrote: > requires three new > instructions that 5a doesn't know about ... > Possibly. I added some of the control instructions where there was consistency in definition and they were needed more than once. [-- Attachment #2: Type: text/html, Size: 653 bytes --]
[-- Attachment #1: Type: text/plain, Size: 128 bytes --] On 3 March 2016 at 14:50, Richard Miller <9fans@hamnavoe.com> wrote: > cpu0: 1200MHz ARM Cortex-A53 r0p4 it's ARMv8-A! [-- Attachment #2: Type: text/html, Size: 415 bytes --]
>> cpu0: 1200MHz ARM Cortex-A53 r0p4
>
> it's ARMv8-A!
When booted in 32-bit mode, it behaves like armv7a.
[-- Attachment #1: Type: text/plain, Size: 504 bytes --] The 32-bit subset of ARMv8 is (supposedly) better specified at the system level than ARMv7 (ie, by the v8 architecture itself). There are some cores that do just the 32-bit subset of v8, but apparently Cortex-A53 will do 64 as well, which I hadn't realised from the Rpi3 announcement I saw. On 3 March 2016 at 15:37, Richard Miller <9fans@hamnavoe.com> wrote: > >> cpu0: 1200MHz ARM Cortex-A53 r0p4 > > > > it's ARMv8-A! > > When booted in 32-bit mode, it behaves like armv7a. > > > [-- Attachment #2: Type: text/html, Size: 895 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --] Now I'm so tempted to get a stack of Raspberry Pi 3 and this case: https://www.amazon.com/GeauxRobot-Raspberry-Model-6-layer-Enclosure/dp/B01D9130QC/ref=sr_1_32 On Thu, Mar 3, 2016 at 6:53 AM Richard Miller <9fans@hamnavoe.com> wrote: > Getting Plan 9 to boot on the pi3 (in 32-bit mode) was almost trivial. > > Plan 9 from Bell Labs > board rev: 0xa02082 firmware rev: 1456410415 > cpu0: 1200MHz ARM Cortex-A53 r0p4 > fp: 32 registers, simd > fp: arm arch VFPv3+ with null subarch; rev 4 > eMMC external clock 250 Mhz > #u/usb/ep1.0: dwcotg: port 0X0 irq 9 > 992M memory: 200M kernel data, 792M user, 3762M swap > cpu1: 1200MHz ARM Cortex-A53 r0p4 > cpu2: 1200MHz ARM Cortex-A53 r0p4 > cpu3: 1200MHz ARM Cortex-A53 r0p4 > usb/hub... usb/ether... > etherusb smsc: b827ebXXXXXX > version...time... > > init: starting /bin/rc > pi3# > > The "almost" is because the latest GPU firmware now initialises the > ARM cores in HYP mode. This change seems to have been made in October, > and affects the pi2 as well. Getting from HYP to SVC mode at boot time > is no longer as simple as a MOVW into CPSR, and requires three new > instructions that 5a doesn't know about ... > [-- Attachment #2: Type: text/html, Size: 1874 bytes --]