Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jun 2018 01:46:34 +0200
From:      Oliver Pinter <oliver.pinter@hardenedbsd.org>
To:        Ed Maste <emaste@freebsd.org>
Cc:        Sean Bruno <sbruno@freebsd.org>, src-committers <src-committers@freebsd.org>,  "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>,  "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>
Subject:   Re: svn commit: r334046 - head/tools/tools/intel-ucode-split
Message-ID:  <CAPQ4ffsKFKMtDX=PiQ6MONy_Sk4OAGgT%2BAbK-N__yQMA9dXHQg@mail.gmail.com>
In-Reply-To: <CAPyFy2B3FgB_MwphmZMg4eqhnygVBS5HacaJXM7aGuOhy8LE9w@mail.gmail.com>
References:  <201805221435.w4MEZXnW041963@repo.freebsd.org> <CAPQ4ffuciB50cdr3MP1H9xYzM1Y_SqFhCP6QVkaDiaYeTcHyNQ@mail.gmail.com> <de0d9337-5587-07bf-5ce4-84c855eeec41@freebsd.org> <CAPyFy2B3FgB_MwphmZMg4eqhnygVBS5HacaJXM7aGuOhy8LE9w@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

On Wednesday, June 13, 2018, Ed Maste <emaste@freebsd.org> wrote:

> On Tue, 12 Jun 2018 at 18:17, Sean Bruno <sbruno@freebsd.org> wrote:
> >
> > On 06/12/18 16:05, Oliver Pinter wrote:
> > > On 5/22/18, Ed Maste <emaste@freebsd.org> wrote:
> > >> Author: emaste
> > >> Date: Tue May 22 14:35:33 2018
> > >> New Revision: 334046
> > >> URL: https://svnweb.freebsd.org/changeset/base/334046
> > >>
> > >> Log:
> > >>   intel-ucode-split: add -n flag to skip creating output files
> > >>
> > >>   Sponsored by:      The FreeBSD Foundation
> > >>
> > >> Modified:
> > >>   head/tools/tools/intel-ucode-split/intel-ucode-split.c
> > >
> > > Hi!
> > >
> > > Could you please MFC the intel-ucode-split related commits to
> 11-STABLE?
> > >
> > > Thanks,
> > > op
> >
> > Do you need it in base for some reason?  This code is already in the
> > devcpu-data port and is used when the port is built.  Its not needed for
> > anything AFAIK.
>
> Indeed, the real use in FreeBSD is via the devcpu-data port; I
> committed it to src/tools/ for collaboration and testing. I'll merge
> it to stable/11 if it will be useful for someone, but am curious about
> the use case.
>


I'm considering to write an in kernel microcode update facility, based on
firmware(9), and in first idea it would be nice during the generation of
firmware modules.


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPQ4ffsKFKMtDX=PiQ6MONy_Sk4OAGgT%2BAbK-N__yQMA9dXHQg>