Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: v2.6.31.9
Commits on Dec 18, 2009
  1. Greg Kroah-Hartman

    Linux 2.6.31.9

    gregkh authored
  2. Greg Kroah-Hartman

    drm/i915: Fix sync to vblank when VGA output is turned off

    Li Peng authored gregkh committed
    commit 778c902 upstream
    
    In current vblank-wait implementation, if we turn off VGA output,
    drm_wait_vblank will still wait on the disabled pipe until timeout,
    because vblank on the pipe is assumed be enabled. This would cause
    slow system response on some system such as moblin.
    
    This patch resolve the issue by adding a drm helper function
    drm_vblank_off which explicitly clear vblank_enabled[crtc], wake up
    any waiting queue and save last vblank counter before turning off
    crtc. It also slightly change drm_vblank_get to ensure that we will
    will return immediately if trying to wait on a disabled pipe.
    
    Signed-off-by: Li Peng <peng.li@intel.com>
    Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
    [anholt: hand-applied for conflicts with overlay changes]
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Cc: Stefan Bader <stefan.bader@canonical.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  3. Greg Kroah-Hartman

    powerpc/therm_adt746x: Record pwm invert bit at module load time]

    Darrick J. Wong authored gregkh committed
    commit 1496e89 upstream.
    
    In commit 0512a9a, we unilaterally zero the
    "pwm invert" bit in the fan behavior configuration register.  On my PowerBook
    G4, this results in the fans going to full speed at low temperature and
    shutting off at high temperature because the pwm invert bit is supposed to be
    set.
    
    Therefore, record the pwm invert bit at driver load time, and write the bit
    into the fan behavior control register.  This restores correct behavior on my
    PBG4 and should work around the bit being set to the wrong value after
    suspend/resume (which is what the original patch was trying to fix).  It also
    fixes a minor omission where the pwm invert bit correction is NOT performed
    when switching into automatic mode.
    
    Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  4. Rafał Miłecki Greg Kroah-Hartman

    V4L/DVB (13116): gspca - ov519: Webcam 041e:4067 added.

    Zajec authored gregkh committed
    commit 518c8df upstream.
    
    Signed-off-by: Rafal Milecki <zajec5@gmail.com>
    Signed-off-by: Jean-Francois Moine <moinejf@free.fr>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
    Cc: Surbhi Palande <surbhi.palande@canonical.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  5. Henrique de Moraes Holschuh Greg Kroah-Hartman

    thinkpad-acpi: preserve rfkill state across suspend/resume

    hmh authored gregkh committed
    commit 208b996 upstream.
    
    Since the rfkill rework in 2.6.31, the driver is always resuming with
    the radios disabled.
    
    Change thinkpad-acpi to ask the firmware to resume with the radios in
    the last state.  This fixes the Bluetooth and WWAN rfkill switches.
    
    Note that it means we respect the firmware's oddities.  Should the
    user toggle the hardware rfkill switch on and off, it might cause the
    radios to resume enabled.
    
    UWB is an unknown quantity since it has nowhere the same level of
    firmware support (no control over state storage in NVRAM, for
    example), and might need further fixing.  Testers welcome.
    
    This change fixes a regression from 2.6.30.
    
    Reported-by: Jerone Young <jerone.young@canonical.com>
    Reported-by: Ian Molton <ian.molton@collabora.co.uk>
    Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
    Tested-by: Ian Molton <ian.molton@collabora.co.uk>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  6. Henrique de Moraes Holschuh Greg Kroah-Hartman

    thinkpad-acpi: fix default brightness_mode for R50e/R51

    hmh authored gregkh committed
    commit a9f8eac upstream.
    
    According to a report, the R50e wants EC-based brightness control,
    even if it uses an Intel GPU.  The current driver default was reported
    to not work at all.
    
    This bug can be worked around by the "brightness_mode=3" module
    parameter.
    
    Change the default of the R50e and R51 2xxx models (which use the same
    EC firmware, 1V) to TPACPI_BRGHT_Q_EC, but keep TPACPI_BRGHT_Q_ASK set
    for now, as I'd like to get more reports.
    
    This fixes a regression caused by commit
    59fe4fe,
    "thinkpad-acpi: fix incorrect use of TPACPI_BRGHT_MODE_ECNVRAM"
    
    Kernel 2.6.31 also needs this fix.
    
    Reported-by: Ferenc Wagner <wferi@niif.hu>
    Tested-by: Ferenc Wagner <wferi@niif.hu>
    Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
    Cc: stable@kernel.org
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  7. ebiederm Greg Kroah-Hartman

    net: Fix userspace RTM_NEWLINK notifications.

    ebiederm authored gregkh committed
    commit d90a909 upstream.
    
    I received some bug reports about userspace programs having problems
    because after RTM_NEWLINK was received they could not immeidate
    access files under /proc/sys/net/ because they had not been
    registered yet.
    
    The problem was trivailly fixed by moving the userspace
    notification from rtnetlink_event to the end of register_netdevice.
    
    Signed-off-by: Eric W. Biederman <ebiederm@aristanetworks.com>
    Cc: David Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  8. Greg Kroah-Hartman

    matroxfb: fix problems with display stability

    Alan Cox authored gregkh committed
    commit 8c65131 upstream.
    
    Regression caused in 2.6.23 and then despite repeated requests never fixed
    or dealt with (Petr promised to sort it in 2008 but seems to have
    forgotten).
    
    Enough is enough - remove the problem line that was added.  If it upsets
    someone they've had two years to deal with it and at the very least it'll
    rattle their cage and wake them up.
    
    Addresses http://bugzilla.kernel.org/show_bug.cgi?id=9709
    
    Signed-off-by: Alan Cox <alan@linux.intel.com>
    Reported-by: Damon <account@bugzilla.kernel.org.juxtaposition.net>
    Tested-by: Ruud van Melick <rvm1974@raketnet.nl>
    Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>
    Cc: Pekka Enberg <penberg@cs.helsinki.fi>
    Cc: Paul A. Clarke <pc@us.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  9. dwmw2 Greg Kroah-Hartman

    jffs2: Fix long-standing bug with symlink garbage collection.

    dwmw2 authored gregkh committed
    commit 2e16cfc upstream.
    
    Ever since jffs2_garbage_collect_metadata() was first half-written in
    February 2001, it's been broken on architectures where 'char' is signed.
    When garbage collecting a symlink with target length above 127, the payload
    length would end up negative, causing interesting and bad things to happen.
    
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  10. Greg Kroah-Hartman

    ipw2100: fix rebooting hang with driver loaded

    Zhu Yi authored gregkh committed
    commit 52ce3e9 upstream.
    
    Add PCI .shutdown method so that we can disable the device during
    shutdown or reboot. Without this, the reboot doesn't work well on
    some platforms.
    
    This fixes http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2124
    
    Tested-by: pablo <pablolm2005@gmail.com>
    Signed-off-by: Zhu Yi <yi.zhu@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  11. Simon Horman Greg Kroah-Hartman

    ipvs: zero usvc and udest

    horms authored gregkh committed
    commit 258c889 upstream.
    
    Make sure that any otherwise uninitialised fields of usvc are zero.
    
    This has been obvserved to cause a problem whereby the port of
    fwmark services may end up as a non-zero value which causes
    scheduling of a destination server to fail for persisitent services.
    
    As observed by Deon van der Merwe <dvdm@truteq.co.za>.
    This fix suggested by Julian Anastasov <ja@ssi.bg>.
    
    For good measure also zero udest.
    
    Cc: Deon van der Merwe <dvdm@truteq.co.za>
    Acked-by: Julian Anastasov <ja@ssi.bg>
    Signed-off-by: Simon Horman <horms@verge.net.au>
    Signed-off-by: Patrick McHardy <kaber@trash.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  12. Jan Kara Greg Kroah-Hartman

    ext3: Fix data / filesystem corruption when write fails to copy data

    jankara authored gregkh committed
    commit 68eb3db upstream.
    
    When ext3_write_begin fails after allocating some blocks or
    generic_perform_write fails to copy data to write, we truncate blocks already
    instantiated beyond i_size. Although these blocks were never inside i_size, we
    have to truncate pagecache of these blocks so that corresponding buffers get
    unmapped. Otherwise subsequent __block_prepare_write (called because we are
    retrying the write) will find the buffers mapped, not call ->get_block, and
    thus the page will be backed by already freed blocks leading to filesystem and
    data corruption.
    
    Reported-by: James Y Knight <foom@fuhm.net>
    Signed-off-by: Jan Kara <jack@suse.cz>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  13. Greg Kroah-Hartman

    drm/i915: PineView only has LVDS and CRT ports

    Zhenyu Wang authored gregkh committed
    commit 103a196 upstream.
    
    PineView only has 2 ports for LVDS and CRT. Don't enable other
    ports for it.
    
    Cc: Shaohua Li <shaohua.li@intel.com>
    Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  14. Greg Kroah-Hartman

    drm/i915: save/restore BLC histogram control reg across suspend/resume

    Jesse Barnes authored gregkh committed
    commit 0eb96d6 upstream.
    
    Turns out some machines, like the ThinkPad X40 don't come back if you
    don't save/restore this register.
    
    Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Cc: Stefan Bader <stefan.bader@canonical.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  15. Greg Kroah-Hartman

    drm/i915: Fix LVDS stability issue on Ironlake

    Zhenyu Wang authored gregkh committed
    commit 1b3c7a4 upstream.
    
    In disable sequence, all output ports on PCH have to be disabled
    before PCH transcoder, but LVDS port was left always enabled. This
    one fixes that by disable LVDS port properly during pipe disable
    process, and resolved stability issue seen on Ironlake. Also move
    panel fitting disable time just after pipe disable to align with
    the spec.
    
    Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  16. Greg Kroah-Hartman

    drm/i915: Fix CRT hotplug detect by checking really no channels attached

    Zhenyu Wang authored gregkh committed
    commit 8e9e0ee upstream.
    
    For CRT hotplug detect status, we have four test results as blue
    channel only, green channel only, both blue and green channel, and
    no channel attached. Origin code only marks both blue and green channel
    case as connected, but ignore other possible connected states. This one
    trys to detect CRT by checking no channel attached case instead.
    
    Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  17. ickle Greg Kroah-Hartman

    drm/i915: Avoid NULL dereference with component_only tv_modes

    ickle authored gregkh committed
    commit d271817 upstream.
    
    In commit d2d9f23, the guard for a valid video mode was removed. This
    caused the regression:
    
      kernel crash during kms graphic boot on Intel GM4500 platform
      https://bugzilla.redhat.com/show_bug.cgi?id=540218
    
    This patches changes the logic slightly not to rely on a coupled
    variable, but to just check whether the video_modes is valid before
    dereferencing.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: David Woodhouse <dwmw2@infradead.org>
    Cc: Zhenyu Wang <zhenyu.z.wang@intel.com>
    [ickle: Actually reference the correct bug report]
    Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  18. Greg Kroah-Hartman

    backlight: lcd - Fix wrong sizeof

    Jean Delvare authored gregkh committed
    commit 1e0fa6b upstream.
    
    Which is why I have always preferred sizeof(struct foo) over
    sizeof(var).
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  19. Corentin Chary Greg Kroah-Hartman

    asus-laptop: change light sens default values.

    iksaif authored gregkh committed
    commit d951d4c upstream.
    
    The light sensor disable brightness key and
    /sys/class/backlight/ control. There was a lot of report
    from users who didn't understand why they couldn't change their
    brightness, including:
    
    https://bugs.launchpad.net/bugs/222171
    https://bugzilla.novell.com/show_bug.cgi?id=514747
    http://bugzilla.kernel.org/show_bug.cgi?id=13671
    http://bugzilla.kernel.org/show_bug.cgi?id=14432
    
    Now the light sensor is disabled, and if the user want to enable
    it, the level should be ok.
    
    The funny thing is that comments where ok, not code.
    
    Cc: stable@kernel.org
    Cc: Thomas Renninger <trenn@suse.de>
    Cc: Peter Küppers <peter-mailbox@web.de>
    Cc: Michael Franzl <michaelfranzl@gmx.at>
    Cc: Ian Turner <vectro@vectro.org>
    Signed-off-by: Corentin Chary <corentincj@iksaif.net>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  20. Greg Kroah-Hartman

    ACPI: Use the ARB_DISABLE for the CPU which model id is less than 0x0f.

    Zhao Yakui authored gregkh committed
    commit 03a05ed upstream.
    
    Currently, ARB_DISABLE is a NOP on all of the recent Intel platforms.
    For such platforms, reduce contention on c3_lock by skipping the fake
    ARB_DISABLE.
    
    The cpu model id on one laptop is 14. If we disable ARB_DISABLE on this box,
    the box can't be booted correctly. But if we still enable ARB_DISABLE on this
    box, the box can be booted correctly.
    
    So we still use the ARB_DISABLE for the cpu which mode id is less than 0x0f.
    
    http://bugzilla.kernel.org/show_bug.cgi?id=14700
    
    Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
    Acked-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    Signed-off-by: Len Brown <len.brown@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  21. Greg Kroah-Hartman

    x86: Under BIOS control, restore AP's APIC_LVTTHMR to the BSP value

    Yong Wang authored gregkh committed
    Upstream commit a2202aa.
    
    On platforms where bios handles the thermal monitor interrupt,
    APIC_LVTTHMR on each logical CPU is programmed to generate a SMI and OS
    can't touch it.
    
    Unfortunately AP bringup sequence using INIT-SIPI-SIPI clear all
    the LVT entries except the mask bit. Essentially this results in
    all LVT entries including the thermal monitoring interrupt set to masked
    (clearing the bios programmed value for APIC_LVTTHMR).
    
    And this leads to kernel take over the thermal monitoring interrupt
    on AP's but not on BSP (leaving the bios programmed value only on BSP).
    
    As a result of this, we have seen system hangs when the thermal
    monitoring interrupt is generated.
    
    Fix this by reading the initial value of thermal LVT entry on BSP
    and if bios has taken over the control, then program the same value
    on all AP's and leave the thermal monitoring interrupt control
    on all the logical cpu's to the bios.
    
    Signed-off-by: Yong Wang <yong.y.wang@intel.com>
    Reviewed-by: Suresh Siddha <suresh.b.siddha@intel.com>
    Cc: Borislav Petkov <borislav.petkov@amd.com>
    Cc: Arjan van de Ven <arjan@infradead.org>
    LKML-Reference: <20091110013824.GA24940@ywang-moblin2.bj.intel.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  22. lwfinger Greg Kroah-Hartman

    p54usb: Remove DMA buffer from stack

    lwfinger authored gregkh committed
    commit 21d6c27 upstream.
    
    On 2.6.32-rc6 from wireless-testing, the following warning is emitted:
    
    ------------[ cut here ]------------
    WARNING: at lib/dma-debug.c:860 check_for_stack+0xaa/0xe0()
    Hardware name: HP Pavilion dv2700 Notebook PC
    ehci_hcd 0000:00:02.1: DMA-API: device driver maps memory fromstack
    	 [addr=ffff8800b6e2bca8]
    Modules linked in: <Removed>
    Pid: 16378, comm: modprobe Not tainted 2.6.32-rc6-wl #244
    Call Trace:
     [<ffffffff81049698>] warn_slowpath_common+0x78/0xb0
     [<ffffffff8104972c>] warn_slowpath_fmt+0x3c/0x40
     [<ffffffff811ae52a>] check_for_stack+0xaa/0xe0
     [<ffffffff811afc8d>] debug_dma_map_page+0xfd/0x170
     [<ffffffffa006297a>] usb_hcd_submit_urb+0x3da/0x9c0 [usbcore]
     [<ffffffff81076e6f>] ? lockdep_init_map+0x5f/0x5d0
     [<ffffffffa0063365>] usb_submit_urb+0xe5/0x260 [usbcore]
     [<ffffffffa0064b7e>] usb_start_wait_urb+0x5e/0xf0 [usbcore]
     [<ffffffffa0063943>] ? usb_init_urb+0x23/0x40 [usbcore]
     [<ffffffffa0064cd4>] usb_bulk_msg+0xc4/0x150 [usbcore]
     [<ffffffffa0441a91>] T.719+0x31/0x40 [p54usb]
     [<ffffffffa0441acf>] p54u_upload_firmware_3887+0x2f/0x490 [p54usb]
     [<ffffffffa049c667>] ? p54_parse_firmware+0x427/0x450 [p54common]
     <Rest of traceback removed>
    ---[ end trace f77df0316ddad3de ]---
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  23. lwfinger Greg Kroah-Hartman

    b43legacy: avoid PPC fault during resume

    lwfinger authored gregkh committed
    commit 316a4d9 upstream.
    
    For PPC architecture with PHY Revision < 3, a read of the register
    B43_MMIO_HWENABLED_LO will cause a CPU fault unless b43legacy_status()
    returns a value of 2 (B43legacy_STAT_STARTED); however, one finds that
    the driver is unable to associate after resuming from hibernation unless
    this routine returns 1. To satisfy both conditions, the routine is rewritten
    to return TRUE whenever b43legacy_status() returns a value < 2.
    
    This patch fixes the second problem listed in the postings for Red Hat
    Bugzilla #538523.
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  24. Greg Kroah-Hartman

    x86/mce: Set up timer unconditionally

    Jan Beulich authored gregkh committed
    commit bc09eff upstream.
    
    mce_timer must be passed to setup_timer() in all cases, no
    matter whether it is going to be actually used. Otherwise, when
    the CPU gets brought down, its call to del_timer_sync() will
    never return, as the timer won't have a base associated, and
    hence lock_timer_base() will loop infinitely.
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
    LKML-Reference: <4B1DB831.2030801@jp.fujitsu.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  25. davem330 Greg Kroah-Hartman

    sparc: Set UTS_MACHINE correctly.

    davem330 authored gregkh committed
    [ Upstream commit 7f5620a ]
    
    "ARCH" can be just about anything, so we shouldn't end up
    with UTS_MACHINE of "sparc" in a 64-bit kernel build just
    because someone set the personality using 'sparc32' or
    similar.  CONFIG_SPARC64 drives the compilation and
    therefore provides the definitive value, not "ARCH".
    
    This mirrors commit 8c6531f
    (x86: correctly set UTS_MACHINE for "make ARCH=x86")
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  26. davem330 Greg Kroah-Hartman

    sparc64: Fix stack debugging IRQ stack regression.

    davem330 authored gregkh committed
    [ Upstream commit 166e553 ]
    
    Commit 4f70f7a
    (sparc64: Implement IRQ stacks.) has two bugs.
    
    First, the softirq range check forgets to subtract STACK_BIAS
    before comparing with %sp.  Next, on failure the wrong label
    is jumped to, resulting in a bogus stack being loaded.
    
    Reported-by: Igor Kovalenko <igor.v.kovalenko@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  27. davem330 Greg Kroah-Hartman

    sparc64: Fix overly strict range type matching for PCI devices.

    davem330 authored gregkh committed
    [ Upstream commit 4230fa3 ]
    
    When we are trying to see if a range property entry applies
    to a given address, we are overly strict about the type.
    
    We should only allow I/O ranges for I/O addresses, and only allow
    CONFIG space ranges for CONFIG space address.
    
    However for MEM ranges, they come in 32-bit and 64-bit flavors.
    And a lack of an exact match is OK if the range is 32-bit and
    the address is 64-bit.  We can assign a 64-bit address properly
    into a 32-bit parent range just fine.
    
    So allow it.
    
    Reported-by: Patrick Finnegan <pat@computer-refuge.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  28. davem330 Greg Kroah-Hartman

    sparc64: Don't specify IRQF_SHARED for LDC interrupts.

    davem330 authored gregkh committed
    [ Upstream commit 08a036d ]
    
    IRQF_SHARED and IRQF_DISABLED don't mix.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  29. davem330 Greg Kroah-Hartman

    sunsu: Use sunserial_console_termios() in sunsu_console_setup().

    davem330 authored gregkh committed
    [ Upstream commit be24656 ]
    
    Be like the other Sun serial drivers otherwise the special handling of
    OpenFirmware options and hard-coded overrides for LOM/RSC consoles
    will not be handled.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  30. davem330 Greg Kroah-Hartman

    sunsu: Pass true 'ignore_line' to console match when RSC or LOM console.

    davem330 authored gregkh committed
    [ Upstream commit 1917d17 ]
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  31. davem330 Greg Kroah-Hartman

    serial: suncore: Fix RSC/LOM handling in sunserial_console_termios().

    davem330 authored gregkh committed
    [ Upstream commit 457931d ]
    
    RSC and LOM devices have fixed speed settings.
    
    We already had some code to match and handle "rsc" named devices on
    E250 systems, but we also have to handle 'rsc-console', 'rsc-control',
    and 'lom-console'.
    
    Also, in order to get this right regardless of what 'output-device'
    happens to be, explicitly pass the UART device node pointer to this
    routine.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  32. davem330 Greg Kroah-Hartman

    serial: suncore: Add 'ignore_line' argument to sunserial_console_matc…

    davem330 authored gregkh committed
    …h().
    
    [ Upstream commit 4e3533d ]
    
    This tells the logic to ignore the line match when deciding whether the
    device is the OpenFirmware specified console device or not.
    
    This is going to be used in the SU driver for rsc-console detection.
    
    There is probably a better way to handle this, but this is the least
    intrusive solution for now which we can validate won't break any other
    cases.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  33. davem330 Greg Kroah-Hartman

    sunsu: Fix detection of SU ports which are RSC console or control.

    davem330 authored gregkh committed
    [ Upstream commit 8301d38 ]
    
    These device nodes are named "rsc-console" and "rsc-control" rather
    than 'serial', but the device_type property is 'serial' so we'll
    tip off of that for detection.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  34. davem330 Greg Kroah-Hartman

    sunsab: Do not set sunsab_reg.cons right before registering minors.

    davem330 authored gregkh committed
    [ Upstream commit 4e68e18 ]
    
    Other Sun serial drivers do not do this, and if we keep it this way
    it ends up registering all serial devices as consoles rather than
    just the one which we explicitly register via sunserial_console_match()
    which uses add_preferred_console().
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  35. davem330 Greg Kroah-Hartman

    sparc64: Fix definition of VMEMMAP_SIZE.

    davem330 authored gregkh committed
    [ Upstream commit bffbc94 ]
    
    This was the cause of various boot failures on V480, V880, etc.
    systems.
    
    Kernel image memory was being overwritten because the vmemmap[]
    array was being sized to small.  So if you had physical memory
    addresses past a certain point, the early bootup would spam
    all over variables in the kernel data section.
    
    The vmemmap mappings map page structs, not page struct pointers.
    And that was the key thinko in the macro definition.
    
    This was fixable thanks to the help, reports, and tireless patience
    of Hermann Lauer.
    
    Reported-by: Hermann Lauer <Hermann.Lauer@iwr.uni-heidelberg.de>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Something went wrong with that request. Please try again.