From: Tristan <9p-st@imu.li>
To: 9fans@9fans.net
Subject: Re: [9fans] hardware device (...)
Date: Tue, 13 Mar 2012 17:54:22 -0400 [thread overview]
Message-ID: <2579c0.6486557d.QSTb.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <A14DFD63-53A3-46D7-86D3-2861B3762B95@me.com>
> So, my question: Doesn't it makes sense that some hardware like CAMs or
> USB-Scanners are working with Plan 9. I mean: There is a good system but as I
> understand there is absolutely no device what I can buy and connect to it.
> Is this a stupid question? Sure I could now spend endless times in trying to
> reach such aim myself, but I believe there are so much tec freaks out there,
> that can do such things much better and faster and I could concentrate more
> at starting user programs?
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?
--
All original matter is hereby placed immediately under the public domain.
next prev parent reply other threads:[~2012-03-13 21:54 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 ` Tristan [this message]
2012-03-13 22:09 ` [9fans] hardware device (...) erik quanstrom
2012-03-13 22:27 ` John Floren
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=2579c0.6486557d.QSTb.mx@tumtum.plumbweb.net \
--to=9p-st@imu.li \
--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).