Skip to content
Snippets Groups Projects
  1. Jan 12, 2024
    • Thomas Zimmermann's avatar
      fbdev/intelfb: Remove driver · 689237ab
      Thomas Zimmermann authored
      
      From looking at the PCI IDs, every device supported by intelfb is
      also supported by i915. Anyone still using intelfb should please
      move on to i915, which does everything intelfb does but better.
      
      Removing intelfb is motivated by the driver's excessive use of the
      global screen_info state. The state belongs to architecture and
      firmware code; device drivers should not attempt to access it. But
      fixing intelfb would require a significant change in the driver's
      probing logic. As intelfb has been obsolete for nearly 2 decades,
      it is probably not worth the effort. Let's just remove it. Also
      remove the related documentation.
      
      Signed-off-by: default avatarThomas Zimmermann <tzimmermann@suse.de>
      Acked-by: default avatarMaik Broemme <mbroemme@libmpq.org>
      Signed-off-by: default avatarHelge Deller <deller@gmx.de>
      689237ab
  2. Aug 18, 2023
  3. Nov 24, 2022
  4. Nov 15, 2022
  5. Sep 27, 2022
  6. Mar 31, 2021
  7. Oct 19, 2020
  8. Sep 24, 2020
  9. Sep 08, 2020
  10. Jul 23, 2020
  11. Jul 20, 2020
  12. May 20, 2020
  13. Apr 23, 2020
  14. Apr 14, 2020
  15. Jan 03, 2020
  16. Dec 16, 2019
  17. Jul 15, 2019
  18. Jun 20, 2019
  19. Jun 19, 2019
  20. Jun 14, 2019
  21. Jan 16, 2019
  22. Sep 26, 2018
  23. Sep 09, 2018
    • Henrik Austad's avatar
      Drop all 00-INDEX files from Documentation/ · a7ddcea5
      Henrik Austad authored
      
      This is a respin with a wider audience (all that get_maintainer returned)
      and I know this spams a *lot* of people. Not sure what would be the correct
      way, so my apologies for ruining your inbox.
      
      The 00-INDEX files are supposed to give a summary of all files present
      in a directory, but these files are horribly out of date and their
      usefulness is brought into question. Often a simple "ls" would reveal
      the same information as the filenames are generally quite descriptive as
      a short introduction to what the file covers (it should not surprise
      anyone what Documentation/sched/sched-design-CFS.txt covers)
      
      A few years back it was mentioned that these files were no longer really
      needed, and they have since then grown further out of date, so perhaps
      it is time to just throw them out.
      
      A short status yields the following _outdated_ 00-INDEX files, first
      counter is files listed in 00-INDEX but missing in the directory, last
      is files present but not listed in 00-INDEX.
      
      List of outdated 00-INDEX:
      Documentation: (4/10)
      Documentation/sysctl: (0/1)
      Documentation/timers: (1/0)
      Documentation/blockdev: (3/1)
      Documentation/w1/slaves: (0/1)
      Documentation/locking: (0/1)
      Documentation/devicetree: (0/5)
      Documentation/power: (1/1)
      Documentation/powerpc: (0/5)
      Documentation/arm: (1/0)
      Documentation/x86: (0/9)
      Documentation/x86/x86_64: (1/1)
      Documentation/scsi: (4/4)
      Documentation/filesystems: (2/9)
      Documentation/filesystems/nfs: (0/2)
      Documentation/cgroup-v1: (0/2)
      Documentation/kbuild: (0/4)
      Documentation/spi: (1/0)
      Documentation/virtual/kvm: (1/0)
      Documentation/scheduler: (0/2)
      Documentation/fb: (0/1)
      Documentation/block: (0/1)
      Documentation/networking: (6/37)
      Documentation/vm: (1/3)
      
      Then there are 364 subdirectories in Documentation/ with several files that
      are missing 00-INDEX alltogether (and another 120 with a single file and no
      00-INDEX).
      
      I don't really have an opinion to whether or not we /should/ have 00-INDEX,
      but the above 00-INDEX should either be removed or be kept up to date. If
      we should keep the files, I can try to keep them updated, but I rather not
      if we just want to delete them anyway.
      
      As a starting point, remove all index-files and references to 00-INDEX and
      see where the discussion is going.
      
      Signed-off-by: default avatarHenrik Austad <henrik@austad.us>
      Acked-by: default avatar"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
      Just-do-it-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      Reviewed-by: default avatarJens Axboe <axboe@kernel.dk>
      Acked-by: default avatarPaul Moore <paul@paul-moore.com>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Acked-by: default avatarMark Brown <broonie@kernel.org>
      Acked-by: default avatarMike Rapoport <rppt@linux.vnet.ibm.com>
      Cc: [Almost everybody else]
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      a7ddcea5
  24. Aug 31, 2018
  25. Aug 10, 2018
  26. Jun 28, 2018
    • Hans de Goede's avatar
      console/fbcon: Add support for deferred console takeover · 83d83beb
      Hans de Goede authored
      
      Currently fbcon claims fbdevs as soon as they are registered and takes over
      the console as soon as the first fbdev gets registered.
      
      This behavior is undesirable in cases where a smooth graphical bootup is
      desired, in such cases we typically want the contents of the framebuffer
      (typically a vendor logo) to stay in place as is.
      
      The current solution for this problem (on embedded systems) is to not
      enable fbcon.
      
      This commit adds a new FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER config option,
      which when enabled defers fbcon taking over the console from the dummy
      console until the first text is displayed on the console. Together with the
      "quiet" kernel commandline option, this allows fbcon to still be used
      together with a smooth graphical bootup, having it take over the console as
      soon as e.g. an error message is logged.
      
      Note the choice to detect the first console output in the dummycon driver,
      rather then handling this entirely inside the fbcon code, was made after
      2 failed attempts to handle this entirely inside the fbcon code. The fbcon
      code is woven quite tightly into the console code, making this to only
      feasible option.
      
      Reviewed-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
      83d83beb
  27. Nov 08, 2017
Loading