public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [BK PATCH] rng driver update
Date: Thu, 13 Mar 2003 19:02:18 -0500	[thread overview]
Message-ID: <3E711C0A.40705@pobox.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2: random-2.5.txt --]
[-- Type: text/plain, Size: 2271 bytes --]

Linus, please do a

	bk pull bk://kernel.bkbits.net/jgarzik/random-2.5

This will update the following files:

 Documentation/i810_rng.txt     |  134 ------
 drivers/char/amd768_rng.c      |  295 --------------
 drivers/char/i810_rng.c        |  404 -------------------
 Documentation/hw_random.txt    |  134 ++++++
 arch/i386/kernel/cpu/centaur.c |   47 +-
 arch/i386/kernel/cpu/common.c  |    5 
 arch/i386/kernel/cpu/proc.c    |   15 
 drivers/char/Kconfig           |   37 -
 drivers/char/Makefile          |    3 
 drivers/char/hw_random.c       |  846 +++++++++++++++++++++++++++++++++++------
 include/asm-i386/cpufeature.h  |   10 
 include/asm-i386/msr.h         |    1 
 12 files changed, 940 insertions(+), 991 deletions(-)

through these ChangeSets:

<jgarzik@redhat.com> (03/03/13 1.1109)
   [hw_random] fixes and cleanups
   
   * s/Via/VIA/
   * allow multiple simultaneous open(2)s of the chrdev.  This allows
   us to eliminate some code, without modifying the core code (rng_dev_read)
   at all.
   * s/__exit// in ->cleanup ops, to eliminate link error

<jgarzik@redhat.com> (03/03/13 1.1108)
   [hw_random] add support for VIA Nehemiah RNG ("xstore" instruction)

<jgarzik@redhat.com> (03/03/13 1.1107)
   [ia32] cpu capabilities cleanups and additions
   
   * Add support for new Centaur(VIA) and Intel cpuid feature bits,
     expanding the x86_capability array by two.
   * (cleanup) Move cpu setup for newer Via C3 cpus into its own
     function, init_c3()
   * Add support for RNG control msr on VIA Nehemiah
   * export X86_FEATURE_XSTORE and cpu_has_xstore macros so that
     kernel code may easily test for cpu support of the new
     "xstore" instruction.

<jgarzik@redhat.com> (03/03/13 1.1106)
   [hw_random] update amd768_rng driver to be modular; add Intel support
   
   Take Alan's amd768_rng driver, recently renamed to hw_random.c,
   and convert it's very-simple structure to support multiple
   types of hardware RNG.  Integrate Intel i8xx (ICH) RNG support.

<jgarzik@redhat.com> (03/03/13 1.1105)
   [hw_random] shuffle files in preparation for hw_random driver update
   
   Delete drivers/char/i810_rng.c, superceded.
   Rename Doc/i810_rng.txt to Doc/hw_random.txt.
   Rename drv/char/amd768_rng.c to drv/char/hw_random.c.


             reply	other threads:[~2003-03-13 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14  0:02 Jeff Garzik [this message]
2003-03-14  0:03 ` [PATCH 1/5] rng driver update Jeff Garzik
2003-03-14  0:03 ` [PATCH 2/5] " Jeff Garzik
2003-03-14  0:04 ` [PATCH 3/5] " Jeff Garzik
2003-03-14  0:04 ` [PATCH 4/5] " Jeff Garzik
2003-03-14  0:05 ` [PATCH 5/5] " Jeff Garzik

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=3E711C0A.40705@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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