9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: michaelian.ennis@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] apropos of the glendix post
Date: Thu,  4 Sep 2008 11:15:26 -0400	[thread overview]
Message-ID: <4b0884274c3eb8d5652e9b8a11ccad21@coraid.com> (raw)
In-Reply-To: <bb9aee10809040751j1e688114m615756a1a525836d@mail.gmail.com>

> Sometimes the binary bits are loaded into the cards, maybe most often,
> and therefore can be done in plan9 as well.  Depending on the vendor
> you may need permission from them to distribute the binary part.

cf. etherm10g.c.  the myricom driver loads a metric ton of firmware into
the card.

> I suspect that some of these drivers are missing still because the
> hardware is not available to the developers who can write them.
>
[...]
>
> I think the one of the BSD projects, OpenBSD perhaps, used to accept
> hardware donations to this end.  If we had a wayto get the hardware
> and the technical documentation in the same place as the developers we
> could get more hardware supported.

good point.  there's plenty of hardware out there with full
documentation that's cheep.  ati has fully documented the 2d
in newer cards, for example.  (a project i never seem to get to.)
intel have done the same.  there are also a number of cards that
aren't really documented but seem straightforward anway — like
the old nvidia propritary sata interface.  if you have such a board
and need >2 drives, this might be a fun and easy project.

writing drivers is an interesting exercize.  on the one hand, small
errors will get you quickly because they typically run millions of
times per second.  this isn't all bad because one finds errors quite
quickly. :-)  on the other hand, they typically follow a
small, constrained interface so it's easy to know when you're done
and you don't need to design an interface.

- erik



  reply	other threads:[~2008-09-04 15:15 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 [this message]
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
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=4b0884274c3eb8d5652e9b8a11ccad21@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@9fans.net \
    --cc=michaelian.ennis@gmail.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).