From: Andrey Panin <pazke@orbita1.ru>
To: Robin Johnson <robbat2@orbis-terrarum.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SGI Visual Support?
Date: Thu, 24 Oct 2002 09:52:49 +0400 [thread overview]
Message-ID: <20021024055249.GA303@pazke.ipt> (raw)
In-Reply-To: <20021024001332.GA6151@cherenkov.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Wed, Oct 23, 2002 at 05:13:32PM -0700, Robin Johnson wrote:
> Greetings list
>
> I am writing to enquire of the status of SGI Visual Workstation support
> in the 2.5 series.
Non functional at this moment :(
> The Linux VISWS page on sourceforge
> http://sourceforge.net/projects/linux-visws
> Has a patch for 2.5.24
> This currently doesn't apply 2.5.44 due to the i386 arch split in
> 2.5.37.
>
> It seems the patch on the site developed from this thread, but ends
> inconclusively:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=102465834001728&w=2
>
> Did anybody get it working more than this?
> Does anybody have any more input about the VISWS code working/not
> working?
I'm working on it, but lack of time makes my progress very slow.
> I ask because I have a lot of VISWS 320 boxes at my disposal now and I
> am interested in using them because of the really nice SCSI system they
> have. I've got one connected to a 20Gb DLT drive for doing backups
> presently, running 2.2.10 (the only kernel I could get to work). But I
> need a more recent kernal with netfilter for some firewalling issues.
Are you ready to test new kernels ?
I'm interested in dual cpu VISWS because mine has 1 cpu and it's
impossible(?) to buy a VRM in Russia.
--
Andrey Panin | Embedded systems software developer
pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-10-24 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 0:13 SGI Visual Support? Robin Johnson
2002-10-24 5:52 ` Andrey Panin [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=20021024055249.GA303@pazke.ipt \
--to=pazke@orbita1.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=robbat2@orbis-terrarum.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).