Skip to content
Snippets Groups Projects
  1. Jun 23, 2016
  2. May 30, 2016
    • Jani Nikula's avatar
      Documentation/sphinx: add basic working Sphinx configuration and build · 22cba31b
      Jani Nikula authored
      
      Add basic configuration and makefile to build documentation from any
      .rst files under Documentation using Sphinx. For starters, there's just
      the placeholder index.rst.
      
      At the top level Makefile, hook Sphinx documentation targets alongside
      (but independent of) the DocBook toolchain, having both be run on the
      various 'make *docs' targets.
      
      All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
      that and the Documentation/DocBook/Makefile are now expected to handle
      all the documentation targets, explicitly ignoring them if they're not
      relevant for that particular toolchain. The changes to the existing
      DocBook Makefile are kept minimal.
      
      There is graceful handling of missing Sphinx and rst2pdf (which is
      needed for pdf output) by checking for the tool and python module,
      respectively, with informative messages to the user.
      
      If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
      otherwise gracefully fall back to the Sphinx default theme, with an
      informative message to the user, and slightly less pretty HTML output.
      
      Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
      epubdocs and xmldocs targets. The output documents are written into per
      output type subdirectories under Documentation/output.
      
      Finally, you can pass options to sphinx-build using the SPHINXBUILD make
      variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
      output from Sphinx.
      
      This is based on the original work by Jonathan Corbet, but he probably
      wouldn't recognize this as his own anymore.
      
      Signed-off-by: default avatarJani Nikula <jani.nikula@intel.com>
      22cba31b
  3. Nov 21, 2015
  4. Oct 16, 2015
    • Daniel Vetter's avatar
      drm/doc: Rename docbook to gpu.tmpl · 3a4579b4
      Daniel Vetter authored
      
      DRM is a lot more than a direct rendering manager nowadays, and there's
      also a bunch of things worth documenting for gpu driver developers
      outside of drivers/gpu/drm, like vgaarb, vga_switcheroo or the various
      hardware buses like host1x and ipu-v3.
      
      To avoid further confusion let's rename the top-level to reflect
      reality.
      
      And yes I'm already looking forward to when we need to replace the G
      in GPU with a * ;-)
      
      Inspired by a thread with Lukas since he refused to include the
      vga_switcheroo docs into the drm docs because it's not drm.
      
      Cc: Lukas Wunner <lukas@wunner.de>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@intel.com>
      [Lukas: Drop BUG() easter egg in i915_gem_execbuffer.c spotted by Jani
      and fix typos in commit message.]
      Signed-off-by: default avatarLukas Wunner <lukas@wunner.de>
      Acked-by: default avatarDave Airlie <airlied@gmail.com>
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      3a4579b4
  5. Sep 28, 2015
    • Ben Hutchings's avatar
      DocBook: Use a fixed encoding for output · b479bfd0
      Ben Hutchings authored
      
      Currently the encoding of documents generated by DocBook depends on
      the current locale.  Make the output reproducible independently of
      the locale, by setting the encoding to UTF-8 (LC_CTYPE=C.UTF-8) by
      preference, or ASCII (LC_CTYPE=C) as a fallback.
      
      LC_CTYPE can normally be overridden by LC_ALL, but the top-level
      Makefile unsets that.
      
      Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
      [jc: added check-lc_ctype to .gitignore]
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      b479bfd0
  6. Aug 17, 2015
    • Danilo Cesar Lemes de Paula's avatar
      scripts/kernel-doc: Adding cross-reference links to html documentation. · 5699f871
      Danilo Cesar Lemes de Paula authored
      
      Functions, Structs and Parameters definitions on kernel documentation
      are pure cosmetic, it only highlights the element.
      
      To ease the navigation in the documentation we should use <links> inside
      those tags so readers can easily jump between methods directly.
      
      This was discussed in 2014[1] and is implemented by getting a list
      of <refentries> from the DocBook XML to generate a database. Then it looks
      for <function>,<structnames> and <paramdef> tags that matches the ones in
      the database. As it only links existent references, no broken links are
      added.
      
      [1] - lists.freedesktop.org/archives/dri-devel/2014-August/065404.html
      
      Signed-off-by: default avatarDanilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
      Cc: Randy Dunlap <rdunlap@infradead.org>
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
      Cc: Herbert Xu <herbert@gondor.apana.org.au>
      Cc: Stephan Mueller <smueller@chronox.de>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
      Cc: dri-devel <dri-devel@lists.freedesktop.org>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      5699f871
  7. Aug 14, 2015
    • Ben Hutchings's avatar
      DocBook: Fix non-determinstic installation of duplicate man pages · 9ed71e7a
      Ben Hutchings authored
      
      Some kernel-doc sections are included in multiple DocBook files.  This
      means the mandocs target will generate the same manual page multiple
      times with different metadata (author name/address and manual title,
      taken from the including DocBook file).  If it's invoked in a parallel
      build, the output is non-determinstic.
      
      Build the manual pages in a separate subdirectory per DocBook file,
      then sort and de-duplicate when installing them (which is serialised).
      
      Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
      [jc: fixed conflicts with the docs tree]
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      9ed71e7a
  8. Aug 08, 2015
  9. Aug 06, 2015
  10. Jul 24, 2015
  11. Jul 10, 2015
    • Ben Hutchings's avatar
      DocBook: Avoid building man pages repeatedly and inconsistently · b44158b1
      Ben Hutchings authored
      
      Some kernel-doc sections are included in multiple DocBook files.  This
      means the mandocs target will generate the same manual page multiple
      times with different metadata (author name/address and manual title,
      taken from the including DocBook file).  If it's invoked in a parallel
      build, the output is nondeterminstic.
      
      For each section that is duplicated, mark the less specific manual's
      inclusion as 'extra' and exclude it during conversion to manual pages.
      Use xmlif for this, as that is bundled with xmlto which we already
      use.
      
      I would have preferred to use more conventional markup for this, but
      each of the following approaches failed:
      
      1. Wrap the extra inclusions with a new element and add a template to
         the stylesheet to include/exclude them.  Unfortunately DocBook XSL
         doesn't seem to support foreign elements at an intermediate level
         in the document tree.
      2. Use DocBook profiling.  This works but requires passing an absolute
         path to the profile stylesheet to xmlto, so it's not portable.
      3. Use SGML marked sections.  docbook2x can handle these but xmlto
         chokes on them.
      
      Reported-by: default avatarJérémy Bobbio <lunar@debian.org>
      Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      b44158b1
    • Ben Hutchings's avatar
      DocBook: Don't store mtime (or name) in compressed man pages · 32c1735c
      Ben Hutchings authored
      
      The mtime on a man page is the build time.  As gzip stores the mtime
      and original name in the compressed file by default, this makes
      compressed man pages unreproducible.  Neither of these are important
      metadata in this case, so turn this off.
      
      Reported-by: default avatarJérémy Bobbio <lunar@debian.org>
      Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      32c1735c
  12. Jan 28, 2015
  13. Nov 13, 2014
  14. May 12, 2014
  15. Apr 01, 2014
  16. Mar 29, 2014
  17. Mar 14, 2014
  18. Feb 07, 2014
  19. Dec 02, 2013
  20. May 17, 2012
    • Paul Gortmaker's avatar
      MCA: delete all remaining traces of microchannel bus support. · bb8187d3
      Paul Gortmaker authored
      
      Hardware with MCA bus is limited to 386 and 486 class machines
      that are now 20+ years old and typically with less than 32MB
      of memory.  A quick search on the internet, and you see that
      even the MCA hobbyist/enthusiast community has lost interest
      in the early 2000 era and never really even moved ahead from
      the 2.4 kernels to the 2.6 series.
      
      This deletes anything remaining related to CONFIG_MCA from core
      kernel code and from the x86 architecture.  There is no point in
      carrying this any further into the future.
      
      One complication to watch for is inadvertently scooping up
      stuff relating to machine check, since there is overlap in
      the TLA name space (e.g. arch/x86/boot/mca.c).
      
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: James Bottomley <JBottomley@Parallels.com>
      Cc: x86@kernel.org
      Acked-by: default avatarIngo Molnar <mingo@elte.hu>
      Acked-by: default avatarH. Peter Anvin <hpa@zytor.com>
      Signed-off-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
      bb8187d3
  21. Jul 27, 2011
  22. May 02, 2011
  23. Mar 28, 2011
  24. Mar 22, 2011
    • Laurent Pinchart's avatar
      [media] v4l: v4l2_subdev userspace format API · 333c8b97
      Laurent Pinchart authored
      
      Add a userspace API to get, set and enumerate the media format on a
      subdev pad.
      
      The format at the output of a subdev usually depends on the format at
      its input(s). The try format operation is thus not suitable for probing
      format at individual pads, as it can't modify the device state and thus
      can't remember the format tried at the input to compute the output
      format.
      
      To fix the problem, pass an extra argument to the get/set format
      operations to select the 'try' or 'active' format.
      
      The try format is used when probing the subdev. Setting the try format
      must not change the device configuration but can store data for later
      reuse. Data storage is provided at the file-handle level so applications
      probing the subdev concurently won't interfere with each other.
      
      The active format is used when configuring the subdev. It's identical to
      the format handled by the usual get/set operations.
      
      Signed-off-by: default avatarLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Signed-off-by: default avatarStanimir Varbanov <svarbanov@mm-sol.com>
      Signed-off-by: default avatarSakari Ailus <sakari.ailus@iki.fi>
      Acked-by: default avatarHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      333c8b97
  25. Aug 24, 2010
  26. Aug 11, 2010
  27. Aug 10, 2010
  28. Apr 20, 2010
  29. Dec 16, 2009
  30. Sep 19, 2009
Loading