9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Writing drivers in Plan 9
Date: Tue, 15 Apr 2008 09:23:24 -0400	[thread overview]
Message-ID: <85762e850e20aa70ed81917896404ca3@quanstro.net> (raw)
In-Reply-To: <138575260804150140h43c3c030nd5a9809ecc1468da@mail.gmail.com>

> Hello:
> I've been using Inferno and Plan 9 for almost a year. I certainly love
> Plan 9's ideas and concepts, and I'd be glad to finally move forward
> and leave Unix behind, but for now it is imposible for me, since my
> work does not allow me this (I do data analysis for some physics
> experiment using Cern's ROOT).
> Anyway, I've always wanted to learn to write drivers and I did try it
> a few years ago, using NetBSD, but I could not find time to complete
> the task, so I leaved it unfinished. I want to start again, but this
> time using Plan 9. So, I want to ask you for some pointers about how
> doing this. Please, bear in mind, that I am a complete newbie when it
> comes about writing drivers.
> Saludos

a few thoughts from inexperience

0.  pick something you want to use.
1.  you must have a datasheet.  reading other drivers for the same
h/w can be very misleading before you're done.
2.  implement as few features as you need to get the hardware
working for your purposes.  it's likely the other stuff will never
be needed,
3.  set up an whole plan 9 environment which can pxeboot
your target machine.  if you're like me, you'll be rebooting
quite a bit.
4,  this is still true
	The most effective debugging tool is still careful thought,
	coupled with judiciously placed print statements.
		-Kernighan, 1978

- erik



  parent reply	other threads:[~2008-04-15 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15  8:40 hugo rivera
2008-04-15 11:28 ` a
2008-04-15 13:43   ` erik quanstrom
2008-04-15 16:07     ` a
2008-04-15 18:27       ` hugo rivera
2008-04-15 18:31         ` erik quanstrom
2008-04-15 18:50           ` hugo rivera
2008-04-15 18:54             ` erik quanstrom
2008-04-15 19:06               ` hugo rivera
2008-04-15 13:23 ` erik quanstrom [this message]
2008-09-03 21:50 ` Tom Lieber
2008-09-04  6:36   ` hugo rivera

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=85762e850e20aa70ed81917896404ca3@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).