From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20160229203343.495CCB82A@mail.bitblocks.com> <998ded302d9f2b5cede4f7f0397a6da3@lilly.quanstro.net> In-Reply-To: <998ded302d9f2b5cede4f7f0397a6da3@lilly.quanstro.net> From: Mark Lee Smith Date: Tue, 1 Mar 2016 10:04:43 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e0117716f8cfc5b052cf9e5b3 Subject: Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)? Topicbox-Message-UUID: 89ab7ece-ead9-11e9-9d60-3106f5b1d025 --089e0117716f8cfc5b052cf9e5b3 Content-Type: text/plain; charset=UTF-8 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, 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 > > --089e0117716f8cfc5b052cf9e5b3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

What about NetBSD drivers? As I understand it the Rump proje= ct 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@quans= tro.net> wrote:
> 10-12 y= ears 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 man= ageable

- erik

--089e0117716f8cfc5b052cf9e5b3--