From: Petri Latvala <petri.latvala@intel.com>
To: "Abodunrin, Akeem G" <akeem.g.abodunrin@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"Aran, Omer" <omer.aran@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Wilson, Chris P" <chris.p.wilson@intel.com>,
"Stewart, David C" <david.c.stewart@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Pathi, Pragyansri" <pragyansri.pathi@intel.com>,
"Bloomfield, Jon" <jon.bloomfield@intel.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"Kuoppala, Mika" <mika.kuoppala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] tools/generate_cb_buffer: Add script to assemble CB kernel
Date: Thu, 20 Feb 2020 12:10:58 +0200 [thread overview]
Message-ID: <20200220101058.GX25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CFEEE81102D91947B9CC368106979EBAC8A1549D@ORSMSX102.amr.corp.intel.com>
On Thu, Feb 20, 2020 at 03:06:09AM +0200, Abodunrin, Akeem G wrote:
> > > +export ASSEMBLY_SOURCE=./tools/assembly_source
> > > +
> > > +function get_help {
> > > + echo "Usage: asm_eu_kernel.sh [options]"
> > > + echo "Remember to run this as root"
> >
> > I can't spot why this would need root.
> Since we are generating new file, and writing to it - the script definitely needs root access... otherwise commands like this " prefix_header $i915_filename "Media CB Kernel for gen7.5 devices"" fails
That's no reason to need root. That's just a reason to need write
access to the directory where you're creating the files.
As you require the script to be run in IGT source root and writing to
$cwd, you need write access to IGT source root. Which shouldn't be
root-owned.
> >
> >
> > > + echo " "
> > > + echo "Please make sure your MESA tool is compiled, and run this script
> > from igt home directory"
> >
> > Mesa written as "Mesa" and IGT written as "IGT". And it's "source root
> > directory", not "home directory".
> >
> > Does the assembler require specific build options for Mesa? Note them here.
>
> Yes, it does - but the options are hardcoded in this script - so, mentioning them in the help function is irrelevant...
I'm asking about the Mesa _build_ options. This script doesn't build
Mesa, it just uses it.
From a quick check that would be -Dtools=intel that is required.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-20 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 16:35 [igt-dev] [PATCH i-g-t 0/1] Support to assemble CB kernel for gen7 devs Akeem G Abodunrin
2020-02-18 16:35 ` [igt-dev] [PATCH i-g-t 1/1] tools/generate_cb_buffer: Add script to assemble CB kernel Akeem G Abodunrin
2020-02-19 11:06 ` Petri Latvala
2020-02-20 1:06 ` Abodunrin, Akeem G
2020-02-20 10:10 ` Petri Latvala [this message]
2020-02-20 20:22 ` Abodunrin, Akeem G
2020-02-21 9:58 ` Petri Latvala
2020-02-19 0:28 ` [igt-dev] ✓ Fi.CI.BAT: success for Support to assemble CB kernel for gen7 devs Patchwork
2020-02-20 12:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20200220101058.GX25209@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=akeem.g.abodunrin@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=daniel.vetter@intel.com \
--cc=david.c.stewart@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jon.bloomfield@intel.com \
--cc=mika.kuoppala@intel.com \
--cc=omer.aran@intel.com \
--cc=pragyansri.pathi@intel.com \
--cc=tony.luck@intel.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