9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hardware device (...)
Date: Tue, 13 Mar 2012 15:27:01 -0700	[thread overview]
Message-ID: <CAL4LZyiUiF0wET_1LFYE-ymBivZTMJyaVQNSBU2GQom=AAuhLw@mail.gmail.com> (raw)
In-Reply-To: <072d1db9787b42047b3f8428d3a2f2bd@chula.quanstro.net>

On Tue, Mar 13, 2012 at 3:09 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>> folks don't write code until they want it. until now, nobody has cared
>> enough about cameras or scanners or printers (though i thought ethernet
>> connected printers work more or less (but i've never printed anything))
>> to do anything. now you care, maybe you'll write them. the beauty of plan
>> 9 is that it's easy to write drivers if you have decent documentation.
>> which you will for at least some of the devices you listed.
>>
>> or maybe some common user-oriented device support like this would make a
>> good Google Summer of Code project?
>
> you'd do much better in gsoc if you limited your scope.
>
> - erik
>

I'd also like to recommend that projects take place outside the kernel
when possible. It's a lot easier to do things in userland on a single
Plan 9 box (or VM), while I've found that kernel work is best done
with at least a CPU server, a "victim" PC with serial output so we can
catch crash messages, and then another box where you can sit to
actually write code--a much more complex thing for a student with no
hardware budget to set up!

John



  reply	other threads:[~2012-03-13 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 16:21 [9fans] hardware device line -> what about the "file resource hardware devices" that are supported Christoph Paschke
2012-03-13 17:24 ` Nemo
2012-03-13 17:27   ` erik quanstrom
2012-03-13 21:54 ` [9fans] hardware device (...) Tristan
2012-03-13 22:09   ` erik quanstrom
2012-03-13 22:27     ` John Floren [this message]
2012-03-13 22:55       ` Tristan
2012-03-14  1:38   ` Jeff Sickel
2012-03-14 13:02     ` erik quanstrom
2012-03-14 13:13       ` erik quanstrom

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='CAL4LZyiUiF0wET_1LFYE-ymBivZTMJyaVQNSBU2GQom=AAuhLw@mail.gmail.com' \
    --to=john@jfloren.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).