From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Consindering eBox-4854 for Plan9
Date: Fri, 15 Feb 2008 07:38:21 -0500 [thread overview]
Message-ID: <72b9b7fd1c8395d1a04a5282d43b9eff@quanstro.net> (raw)
In-Reply-To: <e33a1cf2-e79f-4b75-9c64-4f7637b937fe@h11g2000prf.googlegroups.com>
> The eBox-4854 box features Realtek RTL8100B 10/100 Base-T Ethernet.
> This is not listed on the Plan9 hardware compatiblilty page. Perusing
> online forums suggests that this adapter can be driven on some Linux
> distros with 8139too. How likely is Plan9 to similary drive this
> ethernet adapter?
should work with the 8139 driver.
> It also features integrated VIA UniChrome Pro II video to which the
> Plan9 hardware compatibility page suggests it can be driven in VESA
> mode. However, I do not know if there are key differences between
> UniChrome and UniChrome Pro II that would prevent this. Are there any
> such differences? Notwithstanding said differences, at what maximum
> resolution would Plan9 enable on this adapter?
vesa mode works. unichrome II is propritary and you can't get the
programming docs without an nda.
> Rather than a traditional hard disk, the eBox-4854 fits an IDE Flash
> SDD. I imagine that this would pose no problem for Plan9, since such
> devices usually internally manage translation from Flash to standard
> IDE. Am I about right in this assumption?
this might be a problem. these boxes typically have 30 or 40w power
supplies. you might not have enough juce to run a hard drive. but
we use similar machines for terminals.
- erik
next prev parent reply other threads:[~2008-02-15 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 9:51 TheAbysmal
2008-02-15 12:38 ` erik quanstrom [this message]
2008-02-15 18:39 ` ron minnich
2008-02-15 18:47 ` erik quanstrom
2008-02-15 18:51 ` ron minnich
2008-02-15 18:56 ` erik quanstrom
2008-02-15 19:01 ` ron minnich
2008-02-15 19:16 ` erik quanstrom
2008-02-15 21:09 ` John Barham
2008-02-15 21:16 ` John Barham
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=72b9b7fd1c8395d1a04a5282d43b9eff@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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).