From: Dave Lukes <davel@anvil.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Recent NDIS compat layer discussion
Date: Thu, 22 Sep 2005 12:05:25 +0100 [thread overview]
Message-ID: <43328FF5.1050606@anvil.com> (raw)
In-Reply-To: <20050910044128.Y89530@fledge.watson.org>
> :> I just wanted to hear if there was any work being done on NDIS compat
> :> support; if so, by whom?
No and me respectively.:-)
I put my hand up and said I'd look at it, but, due to the usual
constraints, plus a few more,
it'll be a while before you see any movement, but, as they say, it's on
my list.
Also, Since I haven't written any kernel code (let alone drivers) in >15
years,
it will be an "interesting" experience".
> :> I have a few notes
> ...
> >:I'm sure making these publicly accessible (the wiki, typically)
would :not hurt anyone.
Put 'em there!
(Or send them to someone who can: not me!)
It's all potentially useful.
To be honest, I doubt that PE format (which itself is a variant of my
old enemy COFF)
is going to be a major stumbling block, compared with stuff like memory
allocation, .
(Anyone want to bet on whether a typical NDIS drivers leaks memory or not?)
Also, the nice people at Project Evil have already done that part, thank
goodness.
AFAIK, apart from all the usual BS involved in porting (C syntax,
include files etc.),
the nasty parts are going to be imitating the windoze interfaces, memory
allocation, buffering models etc.
> *nod*; I see your point. I think I'm too much of a n00b with plan9 to
> help with any real development (unfortunately).
<soapbox>
Hey, you're here and you're contributing, so you ain't a n00b in my book!
To me, n00bs are the people who don't read the archives and start
whining about
the lack of curses support and asking when the Seamonkey port will be done.
Also, to give some perspective,
I don't have plan9 running (yet): just got 9ports going on my mac a week
or so ago.
The fact that one doesn't hack code does not mean that one does not
contribute.
e.g. Due to a lack-of-time/illness/divorce/lack-of-tuits/...
I've never done anything with plan9, to my eternal shame.
OTOH, I did host the first tiny plan9 conference,
and I feel myself to be a member of the community in a small way.
so come on in, the water's fine!
</soapbox>
DaveL.
P.S. If plan9 was a village then I'd probably be the village idiot, but
it would still better than living in the city.
next prev parent reply other threads:[~2005-09-22 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 7:02 Andrew R. Reiter
2005-09-10 8:05 ` lucio
2005-09-10 8:42 ` Andrew R. Reiter
2005-09-10 14:29 ` lucio
2005-09-22 11:05 ` Dave Lukes [this message]
2005-09-22 12:19 ` Lucio De Re
2005-09-22 15:08 ` Dave Lukes
2005-09-10 15:28 ` Ronald G Minnich
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=43328FF5.1050606@anvil.com \
--to=davel@anvil.com \
--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).