[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C712203AE0B90F@ORSMSX105.amr.corp.intel.com>
Date: Fri, 30 Nov 2012 20:40:24 +0000
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
"Mallick, Asit K" <asit.k.mallick@...el.com>,
Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
Andreas Herrmann <andreas.herrmann3@....com>,
Borislav Petkov <borislav.petkov@....com>,
linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: RE: [PATCH v2 01/10] Documentation/x86: Early load microcode
> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@...or.com]
> Sent: Friday, November 30, 2012 11:46 AM
> To: Yu, Fenghua
> Cc: Ingo Molnar; Thomas Gleixner; Mallick, Asit K; Tigran Aivazian;
> Andreas Herrmann; Borislav Petkov; linux-kernel; x86
> Subject: Re: [PATCH v2 01/10] Documentation/x86: Early load microcode
>
> On 11/29/2012 05:47 PM, Fenghua Yu wrote:
> > +
> > +mkdir initrd
> > +cd initrd
> > +cp ../microcode.hex kernel/x86/microcode/GenuineIntel/microcode.hex
> > +find .|cpio -oc >../ucode.cpio
> > +cd ..
> > +cat ucode.cpio /boot/initrd-3.5.0.img >/boot/initrd-3.5.0.ucode.img
> > +
> > +The generated /boot/initrd-3.5.0.ucode.img can be used as initrd
> file to load
> > +microcode during early boot time.
> >
>
> This is wrong; first of all, this refers to microcode.hex whereas the
> patch refers to microcode.bin, and
Will fix this sentence.
> it misses the mandatory -H newc
> option to cpio.
I think there is no problem here. "-c" is "-H newc".
Quote from man cpio:
'-c' Identical to -H newc, use the new (SVR4) portable format. If you wish the old
portable (ASCII) archive format, use -H odc instead.
>
> Could you update this bit, please?
>
> -hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists