From: Andrey Panin <pazke@pazke.donpac.ru>
To: Adrian Bunk <bunk@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
tglx@linutronix.de, James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org
Subject: Re: Status of SGI 320/540 (Visual Workstation) support?
Date: Tue, 22 Apr 2008 10:19:04 +0400 [thread overview]
Message-ID: <20080422061904.GA6423@pazke.donpac.ru> (raw)
In-Reply-To: <20080421141058.GH6011@cs181133002.pp.htv.fi>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
On 112, 04 21, 2008 at 05:10:58PM +0300, Adrian Bunk wrote:
> On Mon, Apr 21, 2008 at 08:55:36AM -0400, H. Peter Anvin wrote:
> >...
> > VISWS is another matter. It's entirely possible I have the only
> > remaining VISWS in my garage; we have at least not been able to locate
> > another. Not that we have tried all that hard.
> >
> > If there are no VISWS' left, we should just unload the code.
>
> Googling a bit around 320/540 hardware does not seem to have completely
> vanished from the earth, and there are still people who'd like to
> install Linux on them.
>
> Looking through the archives of the mailing list in MAINTAINERS there
> seem to be some older 2.6 kernels that worked on some Visual
> Workstations, but no indication that recent kernels work.
>
> Andrey, what is the status of recent 2.6 kernels on the SGI 320/540?
Right now it doesn't work, but there is a hope. I recovered my SGI 320
recently and I plan to start hacking kernel on it Real Soon Now.
--
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-22 6:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 0:02 Voyager phys_cpu_present_map compile error Adrian Bunk
2008-04-21 8:53 ` Adrian Bunk
2008-04-21 12:00 ` Ingo Molnar
2008-04-21 12:55 ` H. Peter Anvin
2008-04-21 14:10 ` Status of SGI 320/540 (Visual Workstation) support? Adrian Bunk
2008-04-22 6:19 ` Andrey Panin [this message]
2008-04-22 13:29 ` Voyager phys_cpu_present_map compile error Andrew Morton
2008-04-22 15:25 ` Andy Whitcroft
2008-04-21 13:00 ` H. Peter Anvin
2008-04-21 15:42 ` James Bottomley
2008-04-21 20:03 ` Ingo Molnar
2008-04-21 23:08 ` James Bottomley
2008-04-21 19:55 ` Ingo Molnar
2008-04-21 20:03 ` H. Peter Anvin
2008-04-21 20:11 ` Ingo Molnar
2008-04-21 20:10 ` H. Peter Anvin
2008-04-23 8:53 ` Pavel Machek
2008-04-21 13:27 ` Adrian Bunk
2008-04-21 20:14 ` Ingo Molnar
2008-04-21 21:57 ` James Bottomley
2008-04-25 14:50 ` James Bottomley
2008-04-25 16:17 ` Adrian Bunk
2008-04-25 16:33 ` James Bottomley
2008-04-28 17:59 ` Ingo Molnar
2008-04-28 19:09 ` James Bottomley
2008-04-21 15:58 ` James Bottomley
2008-04-21 19:51 ` Ingo Molnar
2008-04-21 20:09 ` Adrian Bunk
2008-04-21 20:13 ` Ingo Molnar
2008-04-21 20:26 ` Adrian Bunk
2008-04-21 20:29 ` Ingo Molnar
2008-04-21 21:02 ` Adrian Bunk
2008-04-21 22:31 ` Ingo Molnar
2008-04-26 7:43 ` Pavel Machek
2008-04-27 0:44 ` H. Peter Anvin
2008-04-27 1:06 ` Adrian Bunk
2008-04-27 1:45 ` H. Peter Anvin
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=20080422061904.GA6423@pazke.donpac.ru \
--to=pazke@pazke.donpac.ru \
--cc=James.Bottomley@HansenPartnership.com \
--cc=astarikovskiy@suse.de \
--cc=bunk@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®