1. 22 6月, 2005 11 次提交
    • R
      [PATCH] I2C: documentation update 3/3 · 828621dd
      R.Marek@sh.cvut.cz 提交于
      This patch adds information about available userspace utillities
      for system health monitoring drivers.
      Signed-off-by: NRudolf Marek <r.marek@sh.cvut.cz>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      828621dd
    • R
      [PATCH] I2C: documentation update 2/3 · 7f15b664
      R.Marek@sh.cvut.cz 提交于
      This patch adds missing documentation for system health monitoring chips.
      I would like to thank all people, who helped me with this project.
      Signed-off-by: NRudolf Marek <r.marek@sh.cvut.cz>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7f15b664
    • R
      [PATCH] I2C: documentation update 1/3 · 2bf34a1c
      R.Marek@sh.cvut.cz 提交于
      This patch just changes the extension of Documentation/i2c/chips/smsc47b397.txt
      to none - to conform with naming in i2c subsystem directory.
      Signed-off-by: NRudolf Marek <r.marek@sh.cvut.cz>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      2bf34a1c
    • J
      [PATCH] I2C: Sensors mailing list has moved · cc0b07ed
      Jean Delvare 提交于
      The following patch updates all references to the sensors mailing list,
      so as to reflect the fact that the list recently moved to a new home and
      changed addresses. I'll work out a similar patch for Linux 2.4 soon.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      cc0b07ed
    • G
      [PATCH] I2C: sysfs names: rename to cpu0_vid, take 3 · 937df8df
      Grant Coady 提交于
      This small patch changes two drivers, adm1025 and adm1026, to
      report vid as cpu0_vid sysfs name as used by the other drivers.
      
      Added duplicated names and six month warning for old names to
      be removed as requested.  Compile tested.
      Signed-off-by: NGrant Coady <gcoady@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      937df8df
    • J
      [PATCH] I2C: Kill address ranges in non-sensors i2c chip drivers · b3d5496e
      Jean Delvare 提交于
      Some months ago, you killed the address ranges mechanism from all
      sensors i2c chip drivers (both the module parameters and the in-code
      address lists). I think it was a very good move, as the ranges can
      easily be replaced by individual addresses, and this allowed for
      significant cleanups in the i2c core (let alone the impressive size
      shrink for all these drivers).
      
      Unfortunately you did not do the same for non-sensors i2c chip drivers.
      These need the address ranges even less, so we could get rid of the
      ranges here as well for another significant i2c core cleanup. Here comes
      a patch which does just that. Since the process is exactly the same as
      what you did for the other drivers set already, I did not split this one
      in parts.
      
      A documentation update is included.
      
      The change saves 308 bytes in the i2c core, and an average 1382 bytes
      for chip drivers which use I2C_CLIENT_INSMOD, 126 bytes for those which
      do not.
      
      This change is required if we want to merge the sensors and non-sensors
      i2c code (and we want to do this).
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      Index: gregkh-2.6/Documentation/i2c/writing-clients
      ===================================================================
      b3d5496e
    • S
      [PATCH] intelfb documentation · 4ff45f51
      Sylvain Meyer 提交于
      Add a small documentation of the driver parameters.
      Signed-off-by: NSylvain Meyer <sylvain.meyer@worldonline.fr>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4ff45f51
    • J
      [PATCH] isofs: show hidden files, add granularity for assoc/hidden files flags · 9769f4eb
      Jeremy White 提交于
      The current isofs treatment of hidden files is flawed in two ways.  First,
      it does not provide sufficient granularity; it hides both 'hidden' files
      and 'associated' files (resource fork for Mac files).  Second, the default
      behavior to completely strip hidden files, while an admirable
      implementation of the spec, is a poor choice given the real world use of
      hidden files as a poor mans copy protection scheme for MSDOS and Windows
      based systems.  A longer description of this is available here:
      
         http://www.uwsg.iu.edu/hypermail/linux/kernel/0205.3/0267.html
      
      This patch was originally built after a few private conversations with Alan
      Cox; I shamefully failed to persist in seeing it go forward, I hope to make
      amends now.
      
      This patch introduces granularity by allowing explicit control for both
      hidden and associated files.  It also reverses the default so that by
      default, hidden files are treated as regular files on the iso9660 file
      system.
      
      This allow Wine to process Windows CDs, including those that are hybrid
      Mac/Windows CDs properly and completely, without our having to go muck up
      peoples fstabs as we do now.  (I have tested this with such a hybrid +
      hidden CD and have verified that this patch works as claimed).
      Signed-off-by: NJeremy White <jwhite@codeweavers.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9769f4eb
    • C
      [PATCH] s390: cio documentation · 6fd6e4a4
      Cornelia Huck 提交于
      Some clarifications in the cio documentation.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6fd6e4a4
    • B
      [PATCH] ioc4: Core driver rewrite · 22329b51
      Brent Casavant 提交于
      This series of patches reworks the configuration and internal structure
      of the SGI IOC4 I/O controller device drivers.
      
      These changes are motivated by several factors:
      
      - The IOC4 chip PCI resources are of mixed use between functions (i.e.
        multiple functions are handled in the same address range, sometimes
        within the same register), muddling resource ownership and initialization
        issues.  Centralizing this ownership in a core driver is desirable.
      
      - The IOC4 chip implements multiple functions (serial, IDE, others not
        yet implemented in the mainline kernel) but is not a multifunction
        PCI device.  In order to properly handle device addition and removal
        as well as module insertion and deletion, an intermediary IOC4-specific
        driver layer is needed to handle these operations cleanly.
      
      - All IOC4 drivers are currently enabled by a single CONFIG value.  As
        not all systems need all IOC4 functions, it is desireable to enable
        these drivers independently.
      
      - The current IOC4 core driver will trigger loading of all function-level
        drivers, as it makes direct calls to them.  This situation should be
        reversed (i.e. function-level drivers cause loading of core driver)
        in order to maintain a clear and least-surprise driver loading model.
      
      - IOC4 hardware design necessitates some driver-level dependency on
        the PCI bus clock speed.  Current code assumes a 66MHz bus, but the
        speed should be autodetected and appropriate compensation taken.
      
      This patch series effects the above changes by a newly and better designed
      IOC4 core driver with which the function-level drivers can register and
      deregister themselves upon module insertion/removal.  By tracking these
      modules, device addition/removal is also handled properly.  PCI resource
      management and ownership issues are centralized in this core driver, and
      IOC4-wide configuration actions such as bus speed detection are also
      handled in this core driver.
      
      This patch:
      
      The SGI IOC4 I/O controller chip implements multiple functions, though it is
      not a multi-function PCI device.  Additionally, various PCI resources of the
      IOC4 are shared by multiple hardware functions, and thus resource ownership by
      driver is not clearly delineated.  Due to the current driver design, all core
      and subordinate drivers must be loaded, or none, which is undesirable if not
      all IOC4 hardware features are being used.
      
      This patch reorganizes the IOC4 drivers so that the core driver provides a
      subdriver registration service.  Through appropriate callbacks the subdrivers
      can now handle device addition and removal, as well as module insertion and
      deletion (though the IOC4 IDE driver requires further work before module
      deletion will work).  The core driver now takes care of allocating PCI
      resources and data which must be shared between subdrivers, to clearly
      delineate module ownership of these items.
      Signed-off-by: NBrent Casavant <bcasavan@sgi.com>
      Acked-by: Pat Gefre <pfg@sgi.com
      Acked-by: NJeremy Higdon <jeremy@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      22329b51
    • H
      [PATCH] shmem: restore superblock info · 0edd73b3
      Hugh Dickins 提交于
      To improve shmem scalability, we allowed tmpfs instances which don't need
      their blocks or inodes limited not to count them, and not to allocate any
      sbinfo.  Which was okay when the only use for the sbinfo was accounting
      blocks and inodes; but since then a couple of unrelated projects extending
      tmpfs want to store other data in the sbinfo.  Whether either extension
      reaches mainline is beside the point: I'm guilty of a bad design decision,
      and should restore sbinfo to make any such future extensions easier.
      
      So, once again allocate a shmem_sb_info for every shmem/tmpfs instance, and
      now let max_blocks 0 indicate unlimited blocks, and max_inodes 0 unlimited
      inodes.  Brent Casavant verified (many months ago) that this does not
      perceptibly impact the scalability (since the unlimited sbinfo cacheline is
      repeatedly accessed but only once dirtied).
      
      And merge shmem_set_size into its sole caller shmem_remount_fs.
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0edd73b3
  2. 21 6月, 2005 3 次提交
  3. 18 6月, 2005 4 次提交
  4. 14 6月, 2005 2 次提交
  5. 01 6月, 2005 2 次提交
  6. 31 5月, 2005 3 次提交
  7. 21 5月, 2005 5 次提交
  8. 18 5月, 2005 1 次提交
    • D
      [PATCH] Driver Core: remove driver model detach_state · 0b405a0f
      David Brownell 提交于
      The driver model has a "detach_state" mechanism that:
      
       - Has never been used by any in-kernel drive;
       - Is superfluous, since driver remove() methods can do the same thing;
       - Became buggy when the suspend() parameter changed semantics and type;
       - Could self-deadlock when called from certain suspend contexts;
       - Is effectively wasted documentation, object code, and headspace.
      
      This removes that "detach_state" mechanism; net code shrink, as well
      as a per-device saving in the driver model and sysfs.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      0b405a0f
  9. 17 5月, 2005 8 次提交
  10. 16 5月, 2005 1 次提交
    • K
      [PATCH] Generic HDLC update · b3dd65f9
      Krzysztof Halasa 提交于
      The attached patch updates generic HDLC to version 1.18.
      FR Cisco LMI production-tested. Please apply to Linux 2.6. Thanks.
      
      Changes:
      - doc updates
      - added Cisco LMI support to Frame-Relay code
      - cleaned hdlc_fr.c a bit, removed some orphaned #defines etc.
      - fixed a problem with non-functional LMI in FR DCE mode.
      - changed diagnostic messages to better conform to FR standards
      - all protocols: information about carrier changes (DCD line) is now
        printed to kernel logs.
      Signed-Off-By: NKrzysztof Halasa <khc@pm.waw.pl>
      b3dd65f9