From: "Kevin D. Kissell" <kevink@mips.com>
To: "Chip Coldwell" <coldwell@frank.harvard.edu>,
<linux-mips@linux-mips.org>
Subject: Re: NCD900 port?
Date: Thu, 24 Apr 2003 23:51:41 +0200 [thread overview]
Message-ID: <011a01c30aab$b7748ce0$10eca8c0@grendel> (raw)
In-Reply-To: Pine.LNX.4.44.0304241613190.18155-100000@frank.harvard.edu
> I'm facing a ~$1K site license charge for NCD's NCBridge software for
> their NC948 X Terminals, and since my site consists of exactly three
> of these things that I bought for less than $250 each I'm balking a
> bit.
>
> The NC948 consists of a 165 MHz QED RM5231, S3 Savage4 graphics
> controller, and an AMD PCnet NIC of some sort. It doesn't seem like
> there's anything in that set that Linux or XFree86 wouldn't be happy
> to run.
What PCI bridge is being used? Galileo?
> To be completely explicit what I'm proposing is to run Linux on the X
> Terminal (as opposed to the server that provides boot image, xdm,
> etc.). My question is: has anybody done it or does anybody know a
> reason why it can't be done?
I think it's probably doable, but if you want two reasons
why it might not be, I'd say they would be:
1) Undocumented/unsupported PCI or other interface
2) Not enough RAM
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Chip Coldwell <coldwell@frank.harvard.edu>, linux-mips@linux-mips.org
Subject: Re: NCD900 port?
Date: Thu, 24 Apr 2003 23:51:41 +0200 [thread overview]
Message-ID: <011a01c30aab$b7748ce0$10eca8c0@grendel> (raw)
Message-ID: <20030424215141.cBdaqC_YWImF_Ow7reeial9m-xNitgufhiWrHtXmGto@z> (raw)
In-Reply-To: Pine.LNX.4.44.0304241613190.18155-100000@frank.harvard.edu
> I'm facing a ~$1K site license charge for NCD's NCBridge software for
> their NC948 X Terminals, and since my site consists of exactly three
> of these things that I bought for less than $250 each I'm balking a
> bit.
>
> The NC948 consists of a 165 MHz QED RM5231, S3 Savage4 graphics
> controller, and an AMD PCnet NIC of some sort. It doesn't seem like
> there's anything in that set that Linux or XFree86 wouldn't be happy
> to run.
What PCI bridge is being used? Galileo?
> To be completely explicit what I'm proposing is to run Linux on the X
> Terminal (as opposed to the server that provides boot image, xdm,
> etc.). My question is: has anybody done it or does anybody know a
> reason why it can't be done?
I think it's probably doable, but if you want two reasons
why it might not be, I'd say they would be:
1) Undocumented/unsupported PCI or other interface
2) Not enough RAM
next prev parent reply other threads:[~2003-04-24 21:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 20:20 NCD900 port? Chip Coldwell
2003-04-24 20:57 ` Alan Cox
2003-04-24 21:51 ` Kevin D. Kissell [this message]
2003-04-24 21:51 ` Kevin D. Kissell
2003-04-24 21:48 ` Chip Coldwell
2003-04-24 22:48 ` Chip Coldwell
2003-04-25 6:53 ` Kevin D. Kissell
2003-04-25 6:53 ` Kevin D. Kissell
2003-04-25 8:39 ` Sander Wichers
2003-04-25 8:39 ` Sander Wichers
2003-04-25 1:46 ` Brad Parker
2003-04-25 2:17 ` Chip Coldwell
2003-04-27 20:01 ` Brad Parker
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 13:56 Dan Aizenstros
2003-04-25 13:56 ` Dan Aizenstros
[not found] <sea8dc20.085@quicklogic.com>
2003-04-25 14:18 ` Chip Coldwell
2003-04-25 14:18 ` Chip Coldwell
2003-04-27 20:08 ` Brad Parker
2003-04-25 15:04 Dan Aizenstros
2003-04-25 15:04 ` Dan Aizenstros
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='011a01c30aab$b7748ce0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=coldwell@frank.harvard.edu \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.