Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Aug 10, 2010
  1. @gregkh

    Linux 2.6.34.3

    gregkh authored
  2. @ming1 @gregkh

    USB: add missing "{}" in map_urb_for_dma

    ming1 authored gregkh committed
    commit f537da6 upstream.
    
    Obviously, {} is needed in the branch of
    	"else if (hcd->driver->flags & HCD_LOCAL_MEM)"
    for handling of setup packet mapping.
    
    Signed-off-by: Ming Lei <tom.leiming@gmail.com>
    Acked-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  3. @lwfinger @gregkh

    ssb: Handle alternate SSPROM location

    lwfinger authored gregkh committed
    commit 9d1ac34 upstream.
    
    In kernel Bugzilla #15825 (2 users), in a wireless mailing list thread
    (http://lists.infradead.org/pipermail/b43-dev/2010-May/000124.html), and on a
    netbook owned by John Linville
    (http://marc.info/?l=linux-wireless&m=127230751408818&w=4), there are reports
    of ssb failing to detect an SPROM at the normal location. After studying the
    MMIO trace dump for the Broadcom wl driver, it was determined that the affected
    boxes had a relocated SPROM.
    
    This patch fixes all systems that have reported this problem.
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  4. @ch-f @gregkh

    ssb: fix NULL ptr deref when pcihost_wrapper is used

    ch-f authored gregkh committed
    commit da1fdb0 upstream.
    
    Ethernet driver b44 does register ssb by it's pcihost_wrapper
    and doesn't set ssb_chipcommon. A check on this value
    introduced with commit d53cdbb
    and ea2db49 triggers:
    
    BUG: unable to handle kernel NULL pointer dereference at 00000010
    IP: [<c1266c36>] ssb_is_sprom_available+0x16/0x30
    
    Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Cc: Larry Finger <Larry.Finger@lwfinger.net>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  5. @Zajec @gregkh

    ssb: Look for SPROM at different offset on higher rev CC

    Zajec authored gregkh committed
    commit ea2db49 upstream.
    
    Our offset handling becomes even a little more hackish now. For some reason I
    do not understand all offsets as inrelative. It assumes base offset is 0x1000
    but it will work for now as we make offsets relative anyway by removing base
    0x1000. Should be cleaner however.
    
    Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Cc: Larry Finger <Larry.Finger@lwfinger.net>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  6. @linvjw @gregkh

    ssb: do not read SPROM if it does not exist

    linvjw authored gregkh committed
    commit d53cdbb upstream.
    
    Attempting to read registers that don't exist on the SSB bus can cause
    hangs on some boxes.  At least some b43 devices are 'in the wild' that
    don't have SPROMs at all.  When the SSB bus support loads, it attempts
    to read these (non-existant) SPROMs and causes hard hangs on the box --
    no console output, etc.
    
    This patch adds some intelligence to determine whether or not the SPROM
    is present before attempting to read it.  This avoids those hard hangs
    on those devices with no SPROM attached to their SSB bus.  The
    SSB-attached devices (e.g. b43, et al.) won't work, but at least the box
    will survive to test further patches. :-)
    
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
    Cc: Larry Finger <Larry.Finger@lwfinger.net>
    Cc: Michael Buesch <mb@bu3sch.de>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  7. @gregkh

    Revert "ssb: Handle Netbook devices where the SPROM address is changed"

    gregkh authored
    Turns out this isn't the best way to resolve this issue.  The
    individual patches will be applied instead.
    
    Cc: Larry Finger <Larry.Finger@lwfinger.net>
    Cc: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  8. @ickle @gregkh

    drm/i915: Check overlay stride errata for i830 and i845

    ickle authored gregkh committed
    commit a1efd14 upstream.
    
    Apparently i830 and i845 cannot handle any stride that is not a multiple
    of 256, unlike their brethren which do support 64 byte aligned strides.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  9. @gregkh

    drm/radeon/kms/r7xx: add workaround for hw issue with HDP flush

    Alex Deucher authored gregkh committed
    commit 812d046 upstream.
    
    Use of HDP_*_COHERENCY_FLUSH_CNTL can cause a hang in certain
    situations.  Add workaround.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  10. @gregkh

    drm/radeon: add new pci ids

    Alex Deucher authored gregkh committed
    commit 1297c05 upstream.
    
    New evergreen and r7xx ids.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  11. @gregkh

    drm/radeon/kms/igp: sideport is AMD only

    Alex Deucher authored gregkh committed
    commit 4c70b2e upstream.
    
    Intel variants don't support it.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  12. @gregkh

    xen: drop xen_sched_clock in favour of using plain wallclock time

    Jeremy Fitzhardinge authored gregkh committed
    commit 8a22b99 upstream.
    
    xen_sched_clock only counts unstolen time.  In principle this should
    be useful to the Linux scheduler so that it knows how much time a process
    actually consumed.  But in practice this doesn't work very well as the
    scheduler expects the sched_clock time to be synchronized between
    cpus.  It also uses sched_clock to measure the time a task spends
    sleeping, in which case "unstolen time" isn't meaningful.
    
    So just use plain xen_clocksource_read to return wallclock nanoseconds
    for sched_clock.
    
    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  13. @gregkh

    KVM: MMU: flush remote tlbs when overwriting spte with different pfn

    Xiao Guangrong authored gregkh committed
    (cherry picked from commit 9154635)
    
    After remove a rmap, we should flush all vcpu's tlb
    
    Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
    Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  14. @gregkh

    GFS2: rename causes kernel Oops

    Bob Peterson authored gregkh committed
    commit 728a756 upstream.
    
    This patch fixes a kernel Oops in the GFS2 rename code.
    
    The problem was in the way the gfs2 directory code was trying
    to re-use sentinel directory entries.
    
    In the failing case, gfs2's rename function was renaming a
    file to another name that had the same non-trivial length.
    The file being renamed happened to be the first directory
    entry on the leaf block.
    
    First, the rename code (gfs2_rename in ops_inode.c) found the
    original directory entry and decided it could do its job by
    simply replacing the directory entry with another.  Therefore
    it determined correctly that no block allocations were needed.
    
    Next, the rename code deleted the old directory entry prior to
    replacing it with the new name.  Therefore, the soon-to-be
    replaced directory entry was temporarily made into a directory
    entry "sentinel" or a place holder at the start of a leaf block.
    
    Lastly, it went to re-add the replacement directory entry in
    that leaf block.  However, when gfs2_dirent_find_space was
    looking for space in the leaf block, it used the wrong value
    for the sentinel.  That threw off its calculations so later
    it decides it can't really re-use the sentinel and therefore
    must allocate a new leaf block.  But because it previously decided
    to re-use the directory entry, it didn't waste the time to
    grab a new block allocation for the inode.  Therefore, the
    inode's i_alloc pointer was still NULL and it crashes trying to
    reference it.
    
    In the case of sentinel directory entries, the entire dirent is
    reused, not just the "free space" portion of it, and therefore
    the function gfs2_dirent_find_space should use the value 0
    rather than GFS2_DIRENT_SIZE(0) for the actual dirent size.
    
    Fixing this calculation enables the reproducer programs to work
    properly.
    
    Signed-off-by: Bob Peterson <rpeterso@redhat.com>
    Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  15. @gregkh

    SCSI: enclosure: fix error path - actually return ERR_PTR() on error

    James Bottomley authored gregkh committed
    commit a91c1be upstream.
    
    we also need to clean up and free the cdev.
    
    Reported-by: Jani Nikula <ext-jani.1.nikula@nokia.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  16. @linvjw @gregkh

    mac80211: avoid scheduling while atomic in mesh_rx_plink_frame

    linvjw authored gregkh committed
    commit c937019 upstream.
    
    While mesh_rx_plink_frame holds sta->lock...
    
    mesh_rx_plink_frame ->
    	mesh_plink_inc_estab_count ->
    		ieee80211_bss_info_change_notify
    
    ...but ieee80211_bss_info_change_notify is allowed to sleep.  A driver
    taking advantage of that allowance can cause a scheduling while
    atomic bug.  Similar paths exist for mesh_plink_dec_estab_count,
    so work around those as well.
    
    http://bugzilla.kernel.org/show_bug.cgi?id=16099
    
    Also, correct a minor kerneldoc comment error (mismatched function names).
    
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  17. @jmberg @gregkh

    cfg80211: don't get expired BSSes

    jmberg authored gregkh committed
    commit ccb6c13 upstream.
    
    When kernel-internal users use cfg80211_get_bss()
    to get a reference to a BSS struct, they may end
    up getting one that would have been removed from
    the list if there had been any userspace access
    to the list. This leads to inconsistencies and
    problems.
    
    Fix it by making cfg80211_get_bss() ignore BSSes
    that cfg80211_bss_expire() would remove.
    
    Fixes http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2180
    
    Reported-by: Jiajia Zheng <jiajia.zheng@intel.com>
    Tested-by: Jiajia Zheng <jiajia.zheng@intel.com>
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  18. @jmberg @gregkh

    cfg80211: ignore spurious deauth

    jmberg authored gregkh committed
    commit 643f82e upstream.
    
    Ever since mac80211/drivers are no longer
    fully in charge of keeping track of the
    auth status, trying to make them do so will
    fail. Instead of warning and reporting the
    deauthentication to userspace, cfg80211 must
    simply ignore it so that spurious
    deauthentications, e.g. before starting
    authentication, aren't seen by userspace as
    actual deauthentications.
    
    Reported-by: Paul Stewart <pstew@google.com>
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  19. @sgruszka @gregkh

    iwlwifi: fix scan abort

    sgruszka authored gregkh committed
    commit d28232b upstream.
    
    Fix possible double priv->mutex lock introduced by commit
    a69b03e
    "iwlwifi: cancel scan watchdog in iwl_bg_abort_scan" .
    We can not call cancel_delayed_work_sync(&priv->scan_check) with
    priv->mutex locked because workqueue function iwl_bg_scan_check()
    take that lock internally.
    
    We do not need to synchronize when canceling priv->scan_check work.
    We can avoid races (sending double abort command or send no
    command at all) using STATUS_SCAN_ABORT bit. Moreover
    current iwl_bg_scan_check() code seems to be broken, as
    we should not send abort commands when currently aborting.
    
    Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  20. @nbd168 @gregkh

    ath9k: fix yet another buffer leak in the tx aggregation code

    nbd168 authored gregkh committed
    commit 4cee786 upstream.
    
    When an aggregation session is being cleaned up, while the tx status
    for some frames is being processed, the TID is flushed and its buffers
    are sent out.
    
    Unfortunately that left the pending un-acked frames unprocessed, thus
    leaking buffers. Fix this by reordering the code so that those frames
    are processed first, before the TID is flushed.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  21. @nbd168 @gregkh

    ath9k: fix TSF after reset on AR913x

    nbd168 authored gregkh committed
    commit f860d52 upstream.
    
    When issuing a reset, the TSF value is lost in the hardware because of
    the 913x specific cold reset. As with some AR9280 cards, the TSF needs
    to be preserved in software here.
    
    Additionally, there's an issue that frequently prevents a successful
    TSF write directly after the chip reset. In this case, repeating the
    TSF write after the initval-writes usually works.
    
    This patch detects failed TSF writes and recovers from them, taking
    into account the delay caused by the initval writes.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Reported-by: Björn Smedman <bjorn.smedman@venatech.se>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  22. @nbd168 @gregkh

    ath9k_hw: fix an off-by-one error in the PDADC boundaries calculation

    nbd168 authored gregkh committed
    commit 03b4776 upstream.
    
    PDADC values were only generated for values surrounding the target
    index, however not for the target index itself, leading to a minor
    error in the generated curve.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  23. @nbd168 @gregkh

    ath9k: fix a potential buffer leak in the STA teardown path

    nbd168 authored gregkh committed
    commit 2b40994 upstream.
    
    It looks like it might be possible for a TID to be paused, while still
    holding some queued buffers, however ath_tx_node_cleanup currently only
    iterates over active TIDs.
    Fix this by always checking every allocated TID for the STA that is being
    cleaned up.
    
    Signed-off-by: Felix Fietkau <nbd@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  24. @linvjw @gregkh

    ath9k: enable serialize_regmode for non-PCIE AR9160

    linvjw authored gregkh committed
    commit 4c85ab1 upstream.
    
    https://bugzilla.kernel.org/show_bug.cgi?id=16476
    
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Acked-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  25. @gregkh

    igb: Use only a single Tx queue in SR-IOV mode

    Greg Rose authored gregkh committed
    commit 5fa8517 upstream.
    
    The 82576 expects the second rx queue in any pool to receive L2 switch
    loop back packets sent from the second tx queue in another pool.  The
    82576 VF driver does not enable the second rx queue so if the PF driver
    sends packets destined to a VF from its second tx queue then the VF
    driver will never see them.  In SR-IOV mode limit the number of tx queues
    used by the PF driver to one. This patch fixes a bug reported in which
    the PF cannot communciate with the VF and should be considered for 2.6.34
    stable.
    
    Signed-off-by: Greg Rose <gregory.v.rose@intel.com>
    Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  26. @error27 @gregkh

    9p: strlen() doesn't count the terminator

    error27 authored gregkh committed
    commit 5c4bfa1 upstream.
    
    This is an off by one bug because strlen() doesn't count the NULL
    terminator.  We strcpy() addr into a fixed length array of size
    UNIX_PATH_MAX later on.
    
    The addr variable is the name of the device being mounted.
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  27. @gregkh

    e1000e: 82577/82578 PHY register access issues

    Bruce Allan authored gregkh committed
    commit ff847ac upstream.
    
    The MAC-PHY interconnect on 82577/82578 uses a power management feature
    (called K1) which must be disabled when in 1Gbps due to a hardware issue on
    these parts.  The #define bit setting used to enable/disable K1 is
    incorrect and can cause PHY register accesses to stop working altogether
    until the next device reset.  This patch sets the register correctly.
    
    This issue is present in kernels since 2.6.32.
    
    Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
    Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  28. @gregkh

    e1000e: don't inadvertently re-set INTX_DISABLE

    Dean Nelson authored gregkh committed
    commit 36f2407 upstream.
    
    Should e1000_test_msi() fail to see an msi interrupt, it attempts to
    fallback to legacy INTx interrupts. But an error in the code may prevent
    this from happening correctly.
    
    Before calling e1000_test_msi_interrupt(), e1000_test_msi() disables SERR
    by clearing the SERR bit from the just read PCI_COMMAND bits as it writes
    them back out.
    
    Upon return from calling e1000_test_msi_interrupt(), it re-enables SERR
    by writing out the version of PCI_COMMAND it had previously read.
    
    The problem with this is that e1000_test_msi_interrupt() calls
    pci_disable_msi(), which eventually ends up in pci_intx(). And because
    pci_intx() was called with enable set to 1, the INTX_DISABLE bit gets
    cleared from PCI_COMMAND, which is what we want. But when we get back to
    e1000_test_msi(), the INTX_DISABLE bit gets inadvertently re-set because
    of the attempt by e1000_test_msi() to re-enable SERR.
    
    The solution is to have e1000_test_msi() re-read the PCI_COMMAND bits as
    part of its attempt to re-enable SERR.
    
    During debugging/testing of this issue I found that not all the systems
    I ran on had the SERR bit set to begin with. And on some of the systems
    the same could be said for the INTX_DISABLE bit. Needless to say these
    latter systems didn't have a problem falling back to legacy INTx
    interrupts with the code as is.
    
    Signed-off-by: Dean Nelson <dnelson@redhat.com>
    Tested-by: Emil Tantilov <emil.s.tantilov@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  29. @gregkh

    amd64_edac: Fix operator precendence error

    Borislav Petkov authored gregkh committed
    commit 962b70a upstream.
    
    The bitwise AND is of higher precedence, make that explicit.
    
    Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  30. @gregkh

    amd64_edac: Correct scrub rate setting

    Borislav Petkov authored gregkh committed
    commit bc57117 upstream.
    
    Exit early when setting scrub rate on unknown/unsupported families.
    
    Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
    Acked-by: Doug Thompson <dougthompson@xmission.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  31. @gregkh

    amd64_edac: Fix DCT base address selector

    Borislav Petkov authored gregkh committed
    commit 9975a5f upstream.
    
    The correct check is to verify whether in high range we're below 4GB
    and not to extract the DctSelBaseAddr again. See "2.8.5 Routing DRAM
    Requests" in the F10h BKDG.
    
    Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
    Acked-by: Doug Thompson <dougthompson@xmission.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  32. @jkkm @gregkh

    parisc: pass through '\t' to early (iodc) console

    jkkm authored gregkh committed
    commit d9b68e5 upstream.
    
    The firmware handles '\t' internally, so stop trying to emulate it
    (which, incidentally, had a bug in it.)
    
    Fixes a really weird hang at bootup in rcu_bootup_announce, which,
    as far as I can tell, is the first printk in the core kernel to use
    a tab as the first character.
    
    Signed-off-by: Kyle McMartin <kyle@parisc-linux.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  33. @baruchsiach @gregkh

    arm/imx/gpio: add spinlock protection

    baruchsiach authored gregkh committed
    commit 14cb0de upstream.
    
    The GPIO registers need protection from concurrent access for operations that
    are not atomic.
    
    Cc: Juergen Beisert <j.beisert@pengutronix.de>
    Cc: Daniel Mack <daniel@caiaq.de>
    Reported-by: rpkamiak@rockwellcollins.com
    Signed-off-by: Baruch Siach <baruch@tkos.co.il>
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  34. @gregkh

    PARISC: led.c - fix potential stack overflow in led_proc_write()

    Helge Deller authored gregkh committed
    commit 4b4fd27 upstream.
    
    avoid potential stack overflow by correctly checking count parameter
    
    Reported-by: Ilja <ilja@netric.org>
    Signed-off-by: Helge Deller <deller@gmx.de>
    Acked-by: Kyle McMartin <kyle@mcmartin.ca>
    Cc: James E.J. Bottomley <jejb@parisc-linux.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  35. @ian-abbott @gregkh

    comedi: Uncripple 8255-based DIO subdevices

    ian-abbott authored gregkh committed
    (Note: upstream comedi configuration has been overhauled, so this patch
    does not apply there.)
    
    Several comedi drivers call subdev_8255_init() (declared in
    "drivers/staging/comedi/drivers/8255.h") to set up one or more DIO
    subdevices.  This should be provided by the 8255.ko module, but unless
    the CONFIG_COMEDI_8255 or CONFIG_COMEDI_8255_MODULE macro is defined,
    the 8255.h header uses a dummy inline version of the function instead.
    This means the comedi devices end up with an "unused" subdevice with 0
    channels instead of a "DIO" subdevice with 24 channels!
    
    This patch provides a non-interactive COMEDI_8255 option and selects it
    whenever the COMEDI_PCI_DRIVERS or COMEDI_PCMCIA_DRIVERS options are
    selected.
    
    Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Something went wrong with that request. Please try again.