From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] bounty for 9pi update for 9front
Date: Thu, 13 Sep 2018 16:01:51 +0100 [thread overview]
Message-ID: <FD1889DE-6490-4ACC-8125-438E6A161643@quintile.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1809131529010.15422@phi>
i would try it at the very least.
i have been looking for an excuse to install 9front.
personally i would like audio support, and a prebuilt image which tracks the 9front 386/amd64 distribution.
my 2p’s worth
-Steve
> On 13 Sep 2018, at 2:29 pm, Julius Schmidt <aiju@phicode.de> wrote:
>
> Sending hardware to cinap is the best way to ensure that it works with the least amount of effort and will continue to work in the future.
>
>> On Wed, 12 Sep 2018, Antoni Sawicki wrote:
>>
>> Hi all
>>
>> Here is my pledge. Recently (April 2018) Richard Miller posted an update of a 9pi image supporting Raspbbery PI 3B+ with USB, Eth, Video etc. I would like to see this integrated in to 9front. What I offer:
>>
>> Hardware (Raspberry PI 3B+) for you to keep forever.
>> $100 for a first working image for RPI 3B+ with latest 9front.
>> $100 for a permanent integration to build process so it will be automatically build with every 9front release in future. You get that on a subsequent 9front release.
>>
>> By a working image I mean something akin to 9pi.img that you dd to the sd card and just works
>>
>> I will only sponsor RPI hardware to serious contenders. Please email me ahead of time.
>>
>> a
>>
next prev parent reply other threads:[~2018-09-13 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 5:27 Antoni Sawicki
2018-09-13 0:47 ` [9front] " Chris McGee
2018-09-13 6:10 ` Steve Simon
2018-09-13 8:07 ` hiro
2018-09-13 10:18 ` Antoni Sawicki
2018-09-13 12:13 ` Steve Simon
2018-09-13 13:29 ` Julius Schmidt
2018-09-13 15:01 ` Steve Simon [this message]
2018-09-13 17:40 ` Chris McGee
2018-09-14 12:29 ` Ethan Gardener
2018-09-14 13:39 ` Steve Simon
2018-09-14 15:25 ` Ethan Gardener
2018-09-13 20:29 ` Antoni Sawicki
2018-10-21 23:45 cinap_lenrek
2019-01-10 17:55 sl
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=FD1889DE-6490-4ACC-8125-438E6A161643@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/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).