From: Jens Staal <staal1978@gmail.com>
To: 9front@googlegroups.com
Subject: Re: DDE - interesting or horrible?
Date: Tue, 9 Aug 2011 07:45:27 +0200 [thread overview]
Message-ID: <CAK8RtFozC1XLjhGRkaXKNumdKer=CT7jLFCiQLTBJJ8cqFu5uA@mail.gmail.com> (raw)
In-Reply-To: <CAB8pEY4nGWV8jyoZ7gpE3Ud9v28oxEr_4JQqmg=Ra6eDr7hsSQ@mail.gmail.com>
The DDE does also not only implement an interface to Linux
drivers/subsystems. In addition to DDE/Linux2.6, there is a DDE/FBSD
(FreeBSD), if that would be more appealing.
As was mentioned in another reply regarding drivers: it is hard to
write them without the hardware - so perhaps a "quick and dirty"
interface layer to existing ones could be a stepping stone (like
NDISwrapper was for wifi on linux before).
On the other hand, I do not want to start a lengthy discussion about
these things. I was just curios to hear what people might think about
it. (and perhaps a "Plan9 with DDE drivers" would be easier to
implement using LP49 anyway...).
2011/8/9 Jacob Todd <jaketodd422@gmail.com>:
> Yes. See plan9.ini(8).
>
> On Aug 9, 2011 1:13 AM, "Thomas Pedersen" <twpedersen@gmail.com> wrote:
>> On Mon, Aug 8, 2011 at 9:29 PM, Julius Schmidt <aiju@phicode.de> wrote:
>>>> Is it that bad? Certainly we can do better than rewriting the same
>>>> drivers every time a new OS comes out, no?
>>>
>>> http://aiju.de/up/plan9duck.png
>>
>> mkay, how is wireless driver support in plan9 anyway? Does it even
>> have an 802.11 stack?
>>>
>
next prev parent reply other threads:[~2011-08-09 5:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 12:50 staalmannen
2011-08-07 17:07 ` Uriel
2011-08-09 0:17 ` Thomas Pedersen
2011-08-09 0:37 ` Kurt H Maier
2011-08-09 1:01 ` hiro
2011-08-09 1:58 ` Iruatã Souza
2011-08-09 4:29 ` Julius Schmidt
2011-08-09 5:13 ` Thomas Pedersen
2011-08-09 5:36 ` Jacob Todd
2011-08-09 5:45 ` Jens Staal [this message]
2011-08-09 5:48 ` Steve Simon
2011-08-09 5:50 ` cinap_lenrek
2011-08-10 15:50 ` Ethan Grammatikidis
2011-08-10 17:25 ` yy
2011-08-11 12:18 ` Ethan Grammatikidis
2011-08-11 12:25 ` yy
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='CAK8RtFozC1XLjhGRkaXKNumdKer=CT7jLFCiQLTBJJ8cqFu5uA@mail.gmail.com' \
--to=staal1978@gmail.com \
--cc=9front@googlegroups.com \
/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).