All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@twiddle.net>
To: ultralinux@vger.kernel.org
Subject: Re: RedHat 6.0 runs on UltraSPARC?
Date: Wed, 28 Apr 1999 15:15:25 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-92531296404684@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92530848032119@msgid-missing>

   From: mc@ainsystems.com
   Date: Wed, 28 Apr 1999 08:06:16 -0700

   So the previous issues concerning the memory limitations on the
   AXmp

There are no memory limitation on AXmp, we support the maximum
configuration of 2GB and 4 processors, I've had it running here
myself.

   Also has RedHat done any work on peripheral support for the Ultra
   line? I do not believe it would be effective to release 6.0 without
   supporting the newer Sparc Linux peripherals.

There is nothing "newer" than what was shipped in RH6.0, up until the
very last moment fixes were constantly being made up to date in the
release, I made sure of this.

I cannot parse what you are saying though, anything which is supported
in _any_ Sparc/Linux kernel available is supported in RH6.0, what
exactly are you particularly after?

Jakub and myself are still the two people doing any of the work, so if
we've added support for the peripheral, the distributions will have it
as well.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~1999-04-28 15:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-28 13:58 RedHat 6.0 runs on UltraSPARC? Randy Carpenter
1999-04-28 14:09 ` Jakub Jelinek
1999-04-28 14:46 ` Randy Carpenter
1999-04-28 14:51 ` Nicholas S. Wourms
1999-04-28 14:55 ` David Miller
1999-04-28 15:06 ` mc
1999-04-28 15:10 ` Anton Blanchard
1999-04-28 15:15 ` David Miller [this message]
1999-04-28 15:41 ` Matthew Kirkwood
1999-04-28 15:55 ` canavan
1999-04-28 16:13 ` Nils Lohner
1999-04-28 21:38 ` Bob Van Cleef

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=marc-linux-ultrasparc-92531296404684@msgid-missing \
    --to=davem@twiddle.net \
    --cc=ultralinux@vger.kernel.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.