linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tigran Aivazian <tigran@veritas.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Christoph Hellwig <hch@lst.de>, Hugh Dickins <hugh@veritas.com>,
	<torvalds@transmeta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] don't create regular files in devfs (fwd)
Date: Tue, 14 Jan 2003 17:31:37 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0301141730350.1241-100000@einstein31.homenet> (raw)
In-Reply-To: <Pine.LNX.4.33.0301140958391.1025-100000@localhost.localdomain>

On Tue, 14 Jan 2003, Patrick Mochel wrote:
> Out of curiosity, how large are the microcode updates? Or rather, what is
> the range of sizes that you've seen?

Each chunk is 2048 bytes long of which only 2000 bytes are the data bits
sent to the cpus. See struct microcode in <asm/processor.h>

Regards
Tigran


  reply	other threads:[~2003-01-14 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0301131851060.9994-100000@localhost.localdomain>
2003-01-14  9:34 ` [PATCH] don't create regular files in devfs (fwd) Tigran Aivazian
2003-01-14 10:31   ` Christoph Hellwig
2003-01-14 11:48     ` Tigran Aivazian
2003-01-14 11:54       ` Tigran Aivazian
2003-01-14 12:50       ` Christoph Hellwig
2003-01-14 16:32         ` Tigran Aivazian
2003-01-14 16:50           ` Arjan van de Ven
2003-01-14 15:59             ` Patrick Mochel
2003-01-14 17:31               ` Tigran Aivazian [this message]
2003-01-14 17:29             ` Tigran Aivazian
2003-01-14 17:40               ` Dave Jones
2003-01-24  6:19                 ` Tigran Aivazian

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=Pine.LNX.4.33.0301141730350.1241-100000@einstein31.homenet \
    --to=tigran@veritas.com \
    --cc=arjanv@redhat.com \
    --cc=hch@lst.de \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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;
as well as URLs for NNTP newsgroup(s).