From: Dave Jones <davej@codemonkey.org.uk>
To: Tigran Aivazian <tigran@veritas.com>
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:40:03 +0000 [thread overview]
Message-ID: <20030114174003.GB9469@codemonkey.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0301141726280.1241-100000@einstein31.homenet>
On Tue, Jan 14, 2003 at 05:29:58PM +0000, Tigran Aivazian wrote:
> No, because cat is using 4K chunks and the data has to be written in one
> large chunk, like this:
>
> # dd if=microcode of=/dev/cpu/microcode bs=141312 count=1
>
> This actually works fine but you need to convert microcode data from human
> readable (what Intel distribute) to binary format first. Easily done with
> microcode_ctl utility.
What about the dumps Christian Ludhoff put at ftp.sandpile.org/mcupdate ?
These are binary data, but are they in the right format to be used ?
I'm curious if these are newer than the ones described in microcode.dat,
but haven't had time to dig through the dates on them.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-01-14 17:34 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
2003-01-14 17:29 ` Tigran Aivazian
2003-01-14 17:40 ` Dave Jones [this message]
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=20030114174003.GB9469@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=arjanv@redhat.com \
--cc=hch@lst.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
--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 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.