9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Georg Lehner <jorge-plan9@magma.com.ni>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] more little hardware
Date: Sun, 28 Mar 2010 16:33:39 +0200	[thread overview]
Message-ID: <4BAF68C3.9070909@magma.com.ni> (raw)
In-Reply-To: <6e35c0621003241528t6f13168amb12a9f97e9b9e78f@mail.gmail.com>

Jack Johnson wrote:
> Thanks to Google's targeted ads:
>
> http://www.eglobalwireless.com/p-4333-new-7-mini-netbook-laptop-notebook-wifi-windows-2gb-hd.aspx
>
> Also might make a good Inferno device if WinCE isn't too firmly ensconced.
>
> -Jack
>
>
Anybody interested in porting Inferno emu to WinCE?

It should not be hard to do, and the tools are available for free. I
could contribute
some knowledge and ressources, though not much time.

WinCE allows to replace the Windows Shell with something else via a simple
registry setting ( targetting e.g. Mobile Phones with WinCE already
installed).
A lot of commercially evaluation boards provide WinCE board support packages
which would allow one to create a new OS-Image with everything but the WinCE
kernel stripped out and include inferno emu as "GUI-shell".

Porting Plan9 from user space seems somewhat more involved to me (threads
and graphics) while an Inferno emu for (Desktop) Windows already exists
(and should require little porting effort to WinCE APIs).

Regards,

    Jorge-Le�n





  reply	other threads:[~2010-03-28 14:33 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 10:34 maht
2010-03-16 14:54 ` blstuart
2010-03-16 16:44   ` John Floren
2010-03-16 16:17     ` blstuart
2010-03-16 19:35     ` Tim Newsham
2010-03-16 19:46       ` John Floren
2010-03-17  4:03         ` Tim Newsham
2010-03-17  4:50           ` ron minnich
2010-03-17 14:38             ` David Leimbach
2010-03-18  6:59             ` Tim Newsham
2010-03-18  8:04               ` Steve Simon
2010-03-18  9:24                 ` Gabriel Díaz
2010-03-18 14:36                   ` David Leimbach
2010-03-18 15:42                     ` Jorden Mauro
2010-03-24 22:28                       ` Jack Johnson
2010-03-28 14:33                         ` Georg Lehner [this message]
2010-03-18 12:46                 ` erik quanstrom
2010-03-18 14:27                   ` Patrick Kelly
2010-03-16 21:02     ` Patrick Kelly
2010-03-16 23:38       ` ron minnich
2010-03-16 23:47         ` Patrick Kelly
2010-03-17  9:05         ` Charles Forsyth
2010-03-17 14:02           ` Stuart Morrow
2010-03-17  9:35         ` hugh
2010-03-17 15:08           ` ron minnich
2010-03-17  2:05       ` David Arnold
2010-03-17 11:11     ` maht
2010-03-17 13:57     ` Stuart Morrow
2010-03-17 18:06       ` Jack Johnson
2010-03-17 19:13         ` John Floren
2010-03-17 19:49           ` Axel Belinfante
2010-03-17 19:57             ` Axel Belinfante
2010-03-17 20:11               ` John Floren
2010-03-18  6:53         ` Tim Newsham
2010-03-16 16:53   ` Jack Johnson
2010-03-16 17:10     ` Jack Johnson
2010-03-16 16:33       ` blstuart
2010-03-16 18:20         ` ron minnich
2010-03-16 19:24           ` blstuart
2010-03-16 17:12       ` Jack Johnson
2010-03-16 17:52 Jonas Amoson
2010-03-16 17:24 ` blstuart

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=4BAF68C3.9070909@magma.com.ni \
    --to=jorge-plan9@magma.com.ni \
    --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).