From: ben bodley <benb@m2tech.co.nz>
To: "Johnson, Stephen B." <stevebj@artesyncp.com>
Cc: embedded list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: emacs and X on embedded Linux
Date: Mon, 04 Sep 2000 11:05:12 +1200 [thread overview]
Message-ID: <39B2D928.2BCF9CB@m2tech.co.nz> (raw)
In-Reply-To: F9102D41F595D311ACA7009027DE2C84967344@c3po.heurikon.com
"Johnson, Stephen B." wrote:
> I've only seen one version of embedded Linux the runs emacs & X on the PPC
> architecture. I used it on the Artesyn PM/PPC running a distribution from
> Protologos (www.protologos.com). I know the guys at Protologos and they had
> to fix some things in the kernel to get it all working, but it only took a
> couple of hours to get everything working.
>
> In this case, everything can be done with a native PPC instead of the cross
> development involved with Monte Vista.
>
> Doesn't anybody else want this capability?
>
>
a lot of people develop boards running a bit slower than 450MHz.. hence
'embedded linux'.. sure if developing an extremely powerful custom board that
comfortably runs X, development tools, etc, it would probably be helpful, but
gets away from many peoples reasons for using embedded hardware (ie. low
ram/flash usage, small size, low cost cpu, etc)..
our custom board runs far slower than 450MHz, still, it runs X and
applications.. however, i would never bother compiling software on it, as i
have a G4 for that..
cheers,
ben
--
/\\------------------------------------------------------------------
ben.bodley/.m2technologyltd.nz/.benb@m2tech.co.nz/.64.9.4448307ext130
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-09-03 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 17:41 emacs and X on embedded Linux Johnson, Stephen B.
2000-09-03 23:05 ` ben bodley [this message]
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=39B2D928.2BCF9CB@m2tech.co.nz \
--to=benb@m2tech.co.nz \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stevebj@artesyncp.com \
/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).