9front - general discussion about 9front
 help / color / mirror / Atom feed
From: suharik <gleb.ax.sh@gmail.com>
To: 9front@googlegroups.com
Subject: Re: Another hardware problem
Date: Wed, 10 Aug 2011 13:59:16 +0000	[thread overview]
Message-ID: <CAF9FGtSTW1s0shsR_=EwkJLoE=Zc6VU+=zPZTLOw2ApB0m+dXA@mail.gmail.com> (raw)
In-Reply-To: <CAB8pEY6RHL29HrhNbE0qh7QN4hXGo4Z_5pX4wAi3B7HKMYo8MQ@mail.gmail.com>

Linux kernel have various documentation for its libs, for examle, for libata.
It helps to understand a driver and to write a driver (at least, I hope).
A Plan 9 drivers uses a functions, I don't know, #include a having no
documentation libs,
and you want me written a driver to device, which is MUCH more
difficult, then UART/RS-232.
I'm not a shaman.

  parent reply	other threads:[~2011-08-10 13:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  9:28 suharik
2011-08-08 11:22 ` Julius Schmidt
2011-08-08 14:00   ` suharik
2011-08-08 17:25     ` Julius Schmidt
2011-08-10 10:43       ` suharik
2011-08-10 10:58         ` yy
2011-08-10 11:42           ` suharik
2011-08-10 12:01             ` suharik
2011-08-10 12:43               ` Jacob Todd
2011-08-10 13:41                 ` suharik
2011-08-10 13:59                 ` suharik [this message]
2011-08-10 15:41                   ` Julius Schmidt
2011-08-10 16:49                     ` suharik
2011-08-10 17:00                       ` cinap_lenrek
2011-08-10 17:23                         ` Kurt H Maier
2011-08-10 17:38                         ` suharik
2011-08-10 17:39                           ` Jacob Todd
2011-08-12  3:20                             ` Uriel
2011-08-12  3:24                               ` cinap_lenrek
2011-08-12  8:46                               ` suharik
2011-08-17 11:23                                 ` Ethan Grammatikidis
2011-08-10 17:30                       ` 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='CAF9FGtSTW1s0shsR_=EwkJLoE=Zc6VU+=zPZTLOw2ApB0m+dXA@mail.gmail.com' \
    --to=gleb.ax.sh@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).