Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-23 Thread Jani Nikula
On Wed, 22 Mar 2017, Dylan Baker wrote: > Quoting Jani Nikula (2017-03-22 01:24:19) >> Right. That helps avoid many of the issues e.g. Sphinx has with the >> configuration files being pure python. > > Yes, sphinx's configuration files are awful for just that reason. Of

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-22 Thread Jani Nikula
On Tue, 21 Mar 2017, Dylan Baker wrote: > Quoting Jani Nikula (2017-03-21 07:44:55) >> How does meson handle build file backwards compatibility between meson >> versions? I don't intend to flame, but I've found for some reason many >> python projects don't seem

Re: [Mesa-dev] [RFC libdrm 0/2] Replace the build system with meson

2017-03-21 Thread Jani Nikula
eatest version would be rather annoying. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Documenting with Sphinx

2016-12-15 Thread Jani Nikula
On Thu, 15 Dec 2016, Robert Bragg wrote: > On Wed, Dec 14, 2016 at 7:17 PM, Jani Nikula > wrote: >> On Wed, 14 Dec 2016, Robert Bragg wrote: >> The AST does include comments right above each cursor, but it falls >> short for comments not attached to cursors. You have t

Re: [Mesa-dev] Documenting with Sphinx

2016-12-14 Thread Jani Nikula
e skeptical of sphinx due to not being able to extract docs >>> From C comments in code in the base tool. Apparently Breathe can chain >>> doxygen into sphinx, so hopefully a "let's get excited about sphinx" >>> patch series would convert our doxygen-based doc

Re: [Mesa-dev] [Intel-gfx] [PATCH 2/2] drm/i915: Removing PCI IDs that are no longer listed as Kabylake.

2016-06-29 Thread Jani Nikula
NTEL_VGA_DEVICE(0x593B, info), /* Halo GT4 */ \ > - INTEL_VGA_DEVICE(0x593A, info), /* SRV GT4 */ \ > - INTEL_VGA_DEVICE(0x593D, info) /* WKS GT4 */ > + INTEL_VGA_DEVICE(0x593B, info) /* Halo GT4 */ > > #define INTEL_KBL_IDS(info) \ > INTEL_KBL_GT1_IDS(info), \ -

Re: [Mesa-dev] [Intel-gfx] [PATCH] list-workarounds: Extend the script to Mesa

2016-02-04 Thread Jani Nikula
% kernel_path) > + sys.exit(1) > + > + i915_dir = os.path.join('drivers', 'gpu', 'drm', 'i915') > + print ("List of workarounds found in kernel:") > + print_workarounds(kernel_path, i915_dir) > + > + # --- list mesa workarounds if path is provided --- > + if options.mesa_path != None: > + # reset workarounds array > + workarounds = {} > + > + mesa_path = options.mesa_path > + i965_dir = os.path.join('src', 'mesa', 'drivers', 'dri', 'i965') > + mesa_dir = os.path.join(mesa_path, i965_dir) > + if not os.path.exists(mesa_dir): > + sys.stderr.write("error: %s does not point to a valid > mesa path \n" > + % mesa_path) > + sys.exit(1) > + > + print ("\nList of workarounds found in Mesa:") > + print_workarounds(mesa_path, i965_dir) -- Jani Nikula, Intel Open Source Technology Center ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [Intel-gfx] [PATCH i-g-t] list-workarounds: Extend the script to Mesa

2016-02-04 Thread Jani Nikula
On Thu, 04 Feb 2016, "Kibey, Sameer" wrote: > Thanks for the input. I changed the subject prefix for this thread, > let me know if you would like me to send a new email with "PATCH > i-g-t" instead. Not necessary; I meant to say, "for future reference".