public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Giacomo Catenazzi <cate@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: Microcode update driver
Date: Mon, 29 Apr 2002 11:39:25 +0100	[thread overview]
Message-ID: <3CCD22DD.E263949B@redhat.com> (raw)
In-Reply-To: <fa.fn3ukrv.1ghovg0@ifi.uio.no> <fa.hho4jnv.11lkl19@ifi.uio.no> <3CCD0B66.4040107@debian.org>

Giacomo Catenazzi wrote:
> 
> arjan@fenrus.demon.nl wrote:
> 
> > In article <m171Yag-000Ga6C@Wasteland> you wrote:
> >
> >>On Saturday 27 April 2002 7:57 pm, Roy Sigurd Karlsbakk wrote:
> >>
> >>>Sorry if this is a FAQ, but where's the microcode.dat supposed to be
> >>>placed? I can't find any information about that in the doc.
> >>>
> >>/usr/share/misc/microcode.dat
> >>
> >
> > hum doesn't the FHS specify that /usr/share shouldn't contain arch
> > specific files ? microcode.dat I can't really call arch neutral....
> 
> Right! But is not a configuration file (in /etc/, like the original sources
> and RH). So it should be in /usr/lib (or in /usr/include, it is really a C/C++
> file, but now we don't use it as a C file).

It's an ascii file for "configuring" the cpu. So I put it in /etc, some
sound firmware
is there anyway (not shipped by RHL but some vendors put it there)

 
> PS: Do you maintain the RH kernel-utils ?

yes

 
> [1] until I find a good new location in FHS

Once I hear a good FHS location I'll change it over to it as well,
/etc/firmware sounded as good as any to me ;(

  reply	other threads:[~2002-04-29 10:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fn3ukrv.1ghovg0@ifi.uio.no>
     [not found] ` <fa.hho4jnv.11lkl19@ifi.uio.no>
2002-04-29  8:59   ` Microcode update driver Giacomo Catenazzi
2002-04-29 10:39     ` Arjan van de Ven [this message]
     [not found] <Pine.LNX.4.44.0204272150130.2833-100000@mustard.heime.net>
2002-04-27 20:01 ` Matthew M
2002-04-27 20:15   ` Tigran Aivazian
2002-04-27 20:34     ` Roy Sigurd Karlsbakk
2002-04-27 20:43       ` Tigran Aivazian
2002-04-27 11:32 Matthew M
2002-04-27 11:42 ` Dave Jones
2002-04-27 12:05   ` François Cami
2002-04-27 18:57   ` Roy Sigurd Karlsbakk
2002-04-27 20:14     ` Matthew M
2002-04-27 19:19       ` arjan
2002-04-27 19:42       ` Roy Sigurd Karlsbakk
2002-04-27 20:04         ` GertJan Spoelman
2002-04-27 20:03       ` Tigran Aivazian
2002-04-27 20:08         ` Matthew M
2002-04-27 20:05 ` 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=3CCD22DD.E263949B@redhat.com \
    --to=arjanv@redhat.com \
    --cc=cate@debian.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