9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] apropos of the glendix post
Date: Fri,  5 Sep 2008 06:59:02 -0700	[thread overview]
Message-ID: <3e1162e60809050659i38ac3d3dqfc029e65d0bab592@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40809050159p6258b587jfdadce676bd10927@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

On Fri, Sep 5, 2008 at 1:59 AM, Francisco J Ballesteros <nemo@lsub.org>wrote:

> me too.
> Not that I wrote any driver since long ago, but I'm interested.


I'd be pretty interested in learning how to write device drivers for *any*
OS at this point.  I've take a few passes at drivers for things in the past
in Plan 9, unsuccessfully, then always seemed to get very busy at work and
had to put stuff like that aside.  (I looked at OHCI USB drivers for Plan 9
at one point, but never got very far with it...)

I think a lot of my problem was not understanding the kernel's structures,
and the right way to do things.

Dave


>
>
> On Fri, Sep 5, 2008 at 6:33 AM,  <lucio@proxima.alt.za> wrote:
> >> Is there anyone out there who's gonna be in Volos and wants to
> >> participate in a driver-writing BOF?
> >
> > Me, kinda goes without saying.
> >
> > ++L
> >
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 1531 bytes --]

  reply	other threads:[~2008-09-05 13:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 23:09 ron minnich
2008-09-02 23:22 ` Uriel
2008-09-02 23:43   ` ron minnich
2008-09-03  1:38 ` Skip Tavakkolian
2008-09-03  3:42   ` ron minnich
2008-09-03 13:02     ` erik quanstrom
2008-09-03 17:40       ` Anant Narayanan
2008-09-03 17:45         ` erik quanstrom
2008-09-03 18:06           ` lucio
2008-09-03 18:17           ` Anant Narayanan
2008-09-03 21:12             ` Latchesar Ionkov
2008-09-03 22:03               ` ron minnich
2008-09-03 22:19                 ` Geoffrey Avila
2008-09-04  2:52                 ` Latchesar Ionkov
2008-09-04  5:47                   ` lucio
2008-09-04  6:10                     ` hiro
2008-09-04 14:51                     ` Michaelian Ennis
2008-09-04 15:15                       ` erik quanstrom
2008-09-05  4:27                       ` lucio
2008-09-04 14:52                     ` Tim Wiess
2008-09-05  4:25                       ` lucio
2008-09-04 23:03                     ` dave.l
2008-09-04 23:18                       ` ron minnich
2008-09-05  0:41                       ` Uriel
2008-09-05  0:44                         ` Uriel
2008-09-05  3:22                           ` ron minnich
2008-09-05  4:33                       ` lucio
2008-09-05  8:59                         ` Francisco J Ballesteros
2008-09-05 13:59                           ` David Leimbach [this message]
2008-09-05 15:36                           ` Mathieu Lonjaret
2008-09-05 15:31                             ` ron minnich
2008-09-05 16:03                       ` Zak B. Elep
2008-09-05 16:41                         ` ron minnich
2008-09-03 21:13       ` Latchesar Ionkov

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=3e1162e60809050659i38ac3d3dqfc029e65d0bab592@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@9fans.net \
    /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).