From: Richard Miller <miller@hamnavoe.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] porting from vs. porting to Plan 9
Date: Sat, 18 Oct 2003 20:19:35 +0100 [thread overview]
Message-ID: <400be6b918a68bbf172e27d1706352b6@hamnavoe.com> (raw)
In-Reply-To: <ce8e73cfd3b84f47eb4301326ce99d76@caldo.demon.co.uk>
>>>It might be possible to construct a cage such that Linux drivers could
>>>be compiled and run in Plan 9 kernels without causing too much damage
>>>to the running system.
Coincidentally, QNX Software Systems have just produced a white paper
on a case study of converting a Linux driver (for the SMC9452TX
ethernet adapter) to use with QNX. They report a successful result,
largely because that particular Linux driver is "well-structured" with
a clean division between hardware-specific code (which could be reused
without changes) and OS-specific code (which was mostly rewritten).
The hardware-specific and OS-specific parts were 7400 lines and 2030
lines of code respectively.
The largest Plan 9 ethernet driver has 2117 lines of code in total.
-- Richard
next prev parent reply other threads:[~2003-10-18 19:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 15:20 mirtchov
2003-10-17 16:34 ` Skip Tavakkolian
2003-10-17 17:08 ` Joel Salomon
2003-10-17 18:55 ` Brantley Coile
2003-10-17 19:05 ` matt
2003-10-17 20:17 ` ron minnich
2003-10-17 20:20 ` Christopher Nielsen
2003-10-17 20:26 ` Brantley Coile
2003-10-17 20:41 ` Charles Forsyth
2003-10-17 20:54 ` Brantley Coile
2003-10-20 10:33 ` Douglas A. Gwyn
2003-10-20 16:03 ` Skip Tavakkolian
2003-10-21 6:07 ` Adrian Tritschler
2003-10-17 22:18 ` ron minnich
2003-10-20 1:38 ` okamoto
2003-10-17 21:36 ` Roman Shaposhnick
2003-10-20 10:33 ` Douglas A. Gwyn
2003-10-21 0:10 ` [9fans] Re: your mail Roman Shaposhnick
2003-10-17 23:38 ` [9fans] porting from vs. porting to Plan 9 Geoff Collyer
2003-10-18 1:21 ` bs
2003-10-21 10:14 ` Martin C.Atkins
2003-10-18 8:27 ` Charles Forsyth
2003-10-18 8:48 ` Richard Miller
2003-10-18 11:09 ` Geoff Collyer
2003-10-18 13:09 ` Tristan Seligmann
2003-10-19 8:25 ` C H Forsyth
2003-10-20 3:28 ` mirtchov
2003-10-20 7:04 ` Tristan Seligmann
2003-10-20 17:17 ` mirtchov
2003-10-20 10:35 ` Patrick R. Wade
2003-10-21 1:14 ` david parsons
2003-10-19 16:27 ` Charles Forsyth
2003-10-20 10:35 ` bs
2003-10-18 19:19 ` Richard Miller [this message]
2003-10-19 15:10 ` I RATTAN
2003-10-19 15:54 ` Richard Miller
2003-10-20 14:03 ` ron minnich
2003-10-20 17:03 ` jmk
2003-10-20 21:40 ` splite
2003-10-17 16:43 ` Ronald G. Minnich
2003-10-17 17:01 ` Fco.J.Ballesteros
2003-10-17 20:17 ` Christopher Nielsen
2003-10-20 10:33 ` Douglas A. Gwyn
2003-10-17 15:36 steve-simon
2003-10-17 16:05 Richard C Bilson
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=400be6b918a68bbf172e27d1706352b6@hamnavoe.com \
--to=miller@hamnavoe.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).