1. 29 Mar, 2016 2 commits
    • Linus Walleij's avatar
      Documentation: update the devices.txt documentation · ebdf4040
      Linus Walleij authored
      Alan is no longer maintaining this list through the Linux assigned
      numbers authority. Make it a collective document by referring to
      "the maintainers" in plural throughout, and naming the chardev and
      block layer maintainers in particular as parties of involvement.
      Cut down and remove some sections that pertained to the process of
      maintaining the list at lanana.org and contacting Alan directly.
      
      Make it clear that this document, in the kernel, is the master
      document.
      
      Also move paragraphs around so as to emphasize dynamic major number
      allocation.
      
      Remove paragraph on 2.6 deprecation, that tag no longer appears
      anywhere in the file.
      
      Cc: Jonathan Corbet <corbet@lwn.net>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Alan Cox <alan@linux.intel.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Jens Axboe <axboe@kernel.dk>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ebdf4040
    • Linus Walleij's avatar
      chrdev: emit a warning when we go below dynamic major range · 49db08c3
      Linus Walleij authored
      Currently a dynamically allocated character device major is taken
      from 254 and downward. This mechanism is used for RTC, IIO and a
      few other subsystems.
      
      The kernel currently has no check prevening these dynamic
      allocations from eating into the assigned numbers at 233 and
      downward.
      
      In a recent test it was reported that so many dynamic device
      majors were used on a test server, that the major number for
      infiniband (231) was stolen. This occurred when allocating a new
      major number for GPIO chips. The error messages from the kernel
      were not helpful. (See: https://lkml.org/lkml/2016/2/14/124)
      
      This patch adds a defined lower limit of the dynamic major
      allocation region will henceforth emit a warning if we start to
      eat into the assigned numbers. It does not do any semantic
      changes and will not change the kernels behaviour: numbers will
      still continue to be stolen, but we will know from dmesg what
      is going on.
      
      This also updates the Documentation/devices.txt to clearly
      reflect that we are using this range of major numbers for dynamic
      allocation.
      Reported-by: default avatarYing Huang <ying.huang@linux.intel.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Alan Cox <alan@linux.intel.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      49db08c3
  2. 05 Mar, 2014 1 commit
  3. 28 Feb, 2014 1 commit
  4. 18 Feb, 2014 1 commit
    • Lucas De Marchi's avatar
      Bluetooth: allocate static minor for vhci · b075dd40
      Lucas De Marchi authored
      Commit bfacbb9a (Bluetooth: Use devname:vhci module alias for virtual HCI
      driver) added the module alias to hci_vhci module so it's possible to
      create the /dev/vhci node. However creating an alias without
      specifying the minor doesn't allow us to create the node ahead,
      triggerring module auto-load when it's first accessed.
      
      Starting with depmod from kmod 16 we started to warn if there's a
      devname alias without specifying the major and minor.
      
      Let's do the same done for uhid, kvm, fuse and others, specifying a
      fixed minor. In systems with systemd as the init the following will
      happen: on early boot systemd will call "kmod static-nodes" to read
      /lib/modules/$(uname -r)/modules.devname and then create the nodes. When
      first accessed these "dead" nodes will trigger the module loading.
      Signed-off-by: default avatarLucas De Marchi <lucas.demarchi@intel.com>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarMarcel Holtmann <marcel@holtmann.org>
      b075dd40
  5. 19 Dec, 2013 1 commit
    • Alex Williamson's avatar
      misc: Reserve minor for VFIO · 8dcf94bc
      Alex Williamson authored
      VFIO currently allocates it's own dynamic chardev range, reserving the
      first minor for the control part of the interface (/dev/vfio/vfio) and
      the remainder for VFIO groups (/dev/vfio/$GROUP).  This works, but it
      doesn't support auto loading.  For instance when libvirt checks for
      VFIO support it looks for /dev/vfio/vfio, which currently doesn't
      exist unless the vfio module is loaded.  By converting the control
      device to a misc driver and reserving a static minor, we can enable
      auto loading.
      
      Reserving the minor is a prerequist to that conversion.  Minor 196
      is unused by anything currently in the kernel.
      Suggested-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: default avatarAlex Williamson <alex.williamson@redhat.com>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      8dcf94bc
  6. 01 Oct, 2013 1 commit
  7. 03 Jul, 2013 1 commit
    • Zhang Yanfei's avatar
      /dev/oldmem: Remove the interface · a11edb59
      Zhang Yanfei authored
      /dev/oldmem provides the interface for us to access the "old memory" in
      the dump-capture kernel.  Unfortunately, no one actually uses this
      interface.
      
      And this interface could actually cause some real problems if used on ia64
      where the cached/uncached accesses are mixed.  See the discussion from the
      link: https://lkml.org/lkml/2013/4/12/386.
      
      So Eric suggested that we should remove /dev/oldmem as an unused piece of
      code.
      
      [akpm@linux-foundation.org: mention /dev/oldmem obsolescence in devices.txt]
      Suggested-by: default avatar"Eric W. Biederman" <ebiederm@xmission.com>
      Signed-off-by: default avatarZhang Yanfei <zhangyanfei@cn.fujitsu.com>
      Cc: Vivek Goyal <vgoyal@redhat.com>
      Cc: Dave Hansen <dave@sr71.net>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Matt Fleming <matt.fleming@intel.com>
      Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Tony Luck <tony.luck@intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      a11edb59
  8. 17 May, 2013 1 commit
  9. 21 Nov, 2012 1 commit
  10. 03 Jun, 2012 1 commit
  11. 17 May, 2012 1 commit
    • 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
  12. 08 May, 2012 1 commit
  13. 13 Jan, 2012 1 commit
  14. 09 Dec, 2011 1 commit
  15. 24 Oct, 2010 1 commit
    • Olof Johansson's avatar
      mmc: make number of mmcblk minors configurable · 5e71b7a6
      Olof Johansson authored
      The old limit of number of minor numbers per mmcblk device was hardcoded
      at 8.  This isn't enough for some of the more elaborate partitioning
      schemes, for example those used by Chrome OS.
      
      Since there might be a bunch of systems out there with static /dev
      contents that relies on the old numbering scheme, let's make it a
      build-time option with the default set to the previous 8.
      
      Also provide a boot/modprobe-time parameter to override the config
      default: mmcblk.perdev_minors.
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      Cc: Mandeep Baines <msb@chromium.org>
      Cc: <linux-mmc@vger.kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarChris Ball <cjb@laptop.org>
      5e71b7a6
  16. 22 Oct, 2010 2 commits
  17. 20 Oct, 2010 1 commit
  18. 11 Aug, 2010 1 commit
  19. 04 Aug, 2010 1 commit
    • Justin P. Mattock's avatar
      Documentation: update broken web addresses. · 0ea6e611
      Justin P. Mattock authored
      Below you will find an updated version from the original series bunching all patches into one big patch
      updating broken web addresses that are located in Documentation/*
      Some of the addresses date as far far back as 1995 etc... so searching became a bit difficult,
      the best way to deal with these is to use web.archive.org to locate these addresses that are outdated.
      Now there are also some addresses pointing to .spec files some are located, but some(after searching
      on the companies site)where still no where to be found. In this case I just changed the address
      to the company site this way the users can contact the company and they can locate them for the users.
      Signed-off-by: default avatarJustin P. Mattock <justinmattock@gmail.com>
      Signed-off-by: default avatarThomas Weber <weber@corscience.de>
      Signed-off-by: default avatarMike Frysinger <vapier.adi@gmail.com>
      Cc: Paulo Marques <pmarques@grupopie.com>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Cc: Michael Neuling <mikey@neuling.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      0ea6e611
  20. 25 May, 2010 1 commit
    • Kay Sievers's avatar
      driver core: add devname module aliases to allow module on-demand auto-loading · 578454ff
      Kay Sievers authored
      This adds:
        alias: devname:<name>
      to some common kernel modules, which will allow the on-demand loading
      of the kernel module when the device node is accessed.
      
      Ideally all these modules would be compiled-in, but distros seems too
      much in love with their modularization that we need to cover the common
      cases with this new facility. It will allow us to remove a bunch of pretty
      useless init scripts and modprobes from init scripts.
      
      The static device node aliases will be carried in the module itself. The
      program depmod will extract this information to a file in the module directory:
        $ cat /lib/modules/2.6.34-00650-g537b60d1-dirty/modules.devname
        # Device nodes to trigger on-demand module loading.
        microcode cpu/microcode c10:184
        fuse fuse c10:229
        ppp_generic ppp c108:0
        tun net/tun c10:200
        dm_mod mapper/control c10:235
      
      Udev will pick up the depmod created file on startup and create all the
      static device nodes which the kernel modules specify, so that these modules
      get automatically loaded when the device node is accessed:
        $ /sbin/udevd --debug
        ...
        static_dev_create_from_modules: mknod '/dev/cpu/microcode' c10:184
        static_dev_create_from_modules: mknod '/dev/fuse' c10:229
        static_dev_create_from_modules: mknod '/dev/ppp' c108:0
        static_dev_create_from_modules: mknod '/dev/net/tun' c10:200
        static_dev_create_from_modules: mknod '/dev/mapper/control' c10:235
        udev_rules_apply_static_dev_perms: chmod '/dev/net/tun' 0666
        udev_rules_apply_static_dev_perms: chmod '/dev/fuse' 0666
      
      A few device nodes are switched to statically allocated numbers, to allow
      the static nodes to work. This might also useful for systems which still run
      a plain static /dev, which is completely unsafe to use with any dynamic minor
      numbers.
      
      Note:
      The devname aliases must be limited to the *common* and *single*instance*
      device nodes, like the misc devices, and never be used for conceptually limited
      systems like the loop devices, which should rather get fixed properly and get a
      control node for losetup to talk to, instead of creating a random number of
      device nodes in advance, regardless if they are ever used.
      
      This facility is to hide the mess distros are creating with too modualized
      kernels, and just to hide that these modules are not compiled-in, and not to
      paper-over broken concepts. Thanks! :)
      
      Cc: Greg Kroah-Hartman <gregkh@suse.de>
      Cc: David S. Miller <davem@davemloft.net>
      Cc: Miklos Szeredi <miklos@szeredi.hu>
      Cc: Chris Mason <chris.mason@oracle.com>
      Cc: Alasdair G Kergon <agk@redhat.com>
      Cc: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
      Cc: Ian Kent <raven@themaw.net>
      Signed-Off-By: default avatarKay Sievers <kay.sievers@vrfy.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      578454ff
  21. 07 Apr, 2009 1 commit
  22. 06 Apr, 2009 1 commit
  23. 03 Apr, 2009 1 commit
  24. 12 Mar, 2009 1 commit
  25. 17 Oct, 2008 1 commit
    • Greg Kroah-Hartman's avatar
      USB: add USB test and measurement class driver · 5b775f67
      Greg Kroah-Hartman authored
      This driver was originaly written by Stefan Kopp, but massively
      reworked by Greg for submission.
      
      Thanks to Felipe Balbi <me@felipebalbi.com> for lots of work in cleaning
      up this driver.
      
      Thanks to Oliver Neukum <oliver@neukum.org> for reviewing previous
      versions and pointing out problems.
      
      
      Cc: Stefan Kopp <stefan_kopp@agilent.com>
      Cc: Marcel Janssen <korgull@home.nl>
      Cc: Felipe Balbi <me@felipebalbi.com>
      Cc: Oliver Neukum <oliver@neukum.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      5b775f67
  26. 13 Aug, 2008 1 commit
    • Wolfgang Mües's avatar
      usb: auerswald: remove driver (obsolete) · 88d987d6
      Wolfgang Mües authored
      This patch removes the auerswald USB driver from the linux kernel
      2.6.26.
      
      This driver was included into the kernel mainly to connect to the ISDN
      framework. This was done in linux 2.4.x. For 2.6.x, due to the fragile
      and moving ISDN support, this connection was never realized, and the
      only use of this driver was for device configuration. In the age of DSL,
      the demand of ISDN support is getting very low.
      
      Meanwhile, with the advent of libusb, an userspace driver was done for
      the device configuration which works fine for linux and mac. (Thanks to
      the libusb developers!). The userspace driver is downloadable from the
      auerswald web site.
      
      So this driver is obsolete now and has to be removed. Many thanks to all
      developers which helped me to bring this driver up and working.
      Signed-off-by: default avatarWolfgang Muees <wolfgang@iksw-muees.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      88d987d6
  27. 19 Oct, 2007 1 commit
  28. 01 Oct, 2007 1 commit
  29. 07 Dec, 2006 1 commit
  30. 29 Nov, 2006 1 commit
  31. 03 Oct, 2006 2 commits
  32. 27 Sep, 2006 1 commit
  33. 31 Jul, 2006 1 commit
  34. 25 Jun, 2006 1 commit
  35. 23 Jun, 2006 1 commit
  36. 15 May, 2006 1 commit
  37. 17 Nov, 2005 1 commit