All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Daniele Ceraolo Spurio" <daniele.ceraolospurio@intel.com>,
	"Dafna Hirschfeld" <dhirschfeld@habana.ai>,
	"Matt Roper" <matthew.d.roper@intel.com>,
	"Niranjana Vishwanathapura" <niranjana.vishwanathapura@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH] drm/xe: Generate oob before compiling anything
Date: Fri, 12 Apr 2024 17:39:20 +0300	[thread overview]
Message-ID: <87h6g64pd3.fsf@intel.com> (raw)
In-Reply-To: <2vhlfwcxjtpjjlj6ddpfuunkqanfrvbdzw76mfsoa4rtjmm2gl@aaqz5bxidaa6>

On Fri, 12 Apr 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Apr 12, 2024 at 09:56:05AM +0300, Jani Nikula wrote:
>>On Thu, 11 Apr 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>>> Instead of keep adding more dependencies as WAs are needed in different
>>> places of the driver, just add a rule with all the objects so the code
>>> generation happens before anything else.
>>
>>What's "oob" and why is it used unexplained everywhere?
>
> from xe_wa.c kernel-doc:
>
>   * platform. There are some basic categories of workarounds, depending on
>   * how/when they are applied:
>
>    ( ... )
>   * - Other/OOB:  There are WAs that, due to their nature, cannot be applied from    
>   *   a central place. Those are peppered around the rest of the code, as needed.    
>   *   Workarounds related to the display IP are the main example.                    
>
> This can certainly be improved and the link to wa_oob.c made. But it's
> not that it was not explained anywhere :)

Yeah, but... what does OOB mean? Out-of-band?

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-04-12 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 21:07 [PATCH] drm/xe: Generate oob before compiling anything Lucas De Marchi
2024-04-11 21:33 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-11 21:34 ` ✓ CI.checkpatch: " Patchwork
2024-04-11 21:34 ` ✗ CI.KUnit: failure " Patchwork
2024-04-24 23:49   ` Lucas De Marchi
2024-04-12  6:56 ` [PATCH] " Jani Nikula
2024-04-12 14:18   ` Lucas De Marchi
2024-04-12 14:39     ` Jani Nikula [this message]
2024-04-12 17:08       ` Lucas De Marchi
2024-04-25 11:19 ` Jani Nikula
2024-04-25 12:48   ` Lucas De Marchi

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=87h6g64pd3.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=dhirschfeld@habana.ai \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=nathan@kernel.org \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=thomas.hellstrom@linux.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 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.