public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce: kdb v2.3 i386 updates for kernels 2.4.18 and 2.4.19
Date: Sat, 10 Aug 2002 19:14:33 +1000	[thread overview]
Message-ID: <11934.1028970873@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Fri, 09 Aug 2002 16:52:18 +1000." <1076.1028875938@kao2.melbourne.sgi.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Updated files in ftp://oss.sgi.com/projects/kdb/download/v2.3/

  kdb-v2.3-2.4.18-common-2.bz2
  kdb-v2.3-2.4.18-i386-3.bz2
  kdb-v2.3-2.4.18-ia64-020722-2.bz2

  kdb-v2.3-2.4.19-common-2.bz2
  kdb-v2.3-2.4.19-i386-3.bz2

These add support for consoles using memory mapped IO instead of
inb/outb, based on a patch by David Mosberger.  Primarily for ia64 zx1
serial i/o but it should work on other memory mapped consoles.

NOTE: These patches go together.

      kdb-v2.3-2.4.18-i386-3 and kdb-v2.3-2.4.18-ia64-020722-2 need
      kdb-v2.3-2.4.18-common-2, and vice versa.

      kdb-v2.3-2.4.19-i386-3 needs kdb-v2.3-2.4.19-common-2, and vice
      versa.

If you get undefined variables kdb_port or kdb_serial then you have
mixed the wrong patches.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE9VNl3i4UHNye0ZOoRAt+UAKClOLtJ+m3uB5KwAGsJsHCPYNbpUgCfXywB
VKjKGpljLryFI2WlNYh8ei8=
=2/Cx
-----END PGP SIGNATURE-----


      reply	other threads:[~2002-08-10  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  6:52 Announce: kdb v2.3 i386 updates for kernels 2.4.18 and 2.4.19 Keith Owens
2002-08-10  9:14 ` Keith Owens [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=11934.1028970873@kao2.melbourne.sgi.com \
    --to=kaos@sgi.com \
    --cc=kdb@oss.sgi.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox