From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: [ANNOUNCE] PCI-SCI Dolphin Drivers 1.2-2 Released
Date: Sat, 10 Feb 2001 04:51:30 -0700 [thread overview]
Message-ID: <20010210045130.A877@vger.timpanogas.org> (raw)
Linux Kernel,
The Dolphin PCI-SCI Scalable Coherent Interface drivers v1.2-2
have been posted at vger.timpanogas.org:/sci/pci-sci-1.2-2 and are
avaialble for download in tar.gz and .src.rpm (RedHat Package Manager)
formats. These drivers are released under the GPL, and are freely
redistributable in both tar.gz and RPM formats.
Please direct any comments or bug reports to jmerkey@timpanogas.org
or linux-kernel@vger.kernel.org.
NOTES:
This release has some minor changes to the RPM spec files to support
cloned installs more easily. The scripts have been updated to perform
a 'uname -r' search for the linux kernel source tree, and will
automatically create a symbolic link during .src.rpm builds or rebuild
if one does not exist to /usr/src/linux.
The RPM specs have also been made a little smarter, and will allow
binary RPM packages to install in cloned systems that have not been
previoulsy installed with a complete kernel source tree.
These changes are useful for folks who build the rpm drivers on
a master system, then wish to simply perform a binary RPM install
onto a series of cloned cluster nodes without requiring a fully
configured Linux source tree to be present on each target system.
This release also corrects an SMP/non-SMP autodetection error when
attempting to install binary RPM drivers onto a system that does
not have a properly configured kernel source tree present.
Jeff Merkey
Chief Engineer, TRG
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-02-10 10:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010210045130.A877@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=jmerkey@timpanogas.org \
--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
all inboxes | Powered by JetHome®