15 Nov, 2007

16 commits

  • The following is an extra entry to enable the touch screen on the new LG
    C1 EXPRESS DUAL machine.

    Cc: Russell King
    Cc: Bjorn Helgaas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Damian Jurd
     
  • This patch fixes the possible usage of a negative value as an array
    index spotted by the Coverity checker.

    sisfb_validate_mode() could return a negative error code and we must check for
    that prior to using its return value as an array index.

    Signed-off-by: Adrian Bunk
    Cc: Thomas Winischhofer
    Cc: "Antonino A. Daplas"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adrian Bunk
     
  • This patch fixes a memory leak spotted by the Coverity checker.

    Signed-off-by: Adrian Bunk
    Cc: Rusty Russell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adrian Bunk
     
  • A relatively recent version of the Geode LX datasheet listed the wrong
    address for one of the MSRs that controls TFT panels, resulting in
    breakage. This patch corrects the MSR address.

    Signed-off-by: Jordan Crouse
    Cc: "Antonino A. Daplas"
    Cc: "H. Peter Anvin"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jordan Crouse
     
  • Attached patch fixes two compilation problems of s1d13xxxfb.c:

    - Fixes outdated dbg() message to fix compilation error with debugging enabled.

    - Do not read kernel command line options when compiled as module.

    Signed-off-by: Stanislav Brabec
    Cc: "Antonino A. Daplas"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Stanislav Brabec
     
  • Instruction pointer returned by profile_pc() can be a random value. This
    break the assumption than we can safely set struct op_sample.eip field to a
    magic value to signal to the per-cpu buffer reader side special event like
    task switch ending up in a segfault in get_task_mm() when profile_pc()
    return ~0UL. Fixed by sanitizing the sampled eip and reject/log invalid
    eip.

    Problem reported by Sami Farin, patch tested by him.

    Signed-off-by: Philippe Elie
    Tested-by: Sami Farin
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Philippe Elie
     
  • Variables that are only used in #ifdef CONFIG_X86 should also only be
    declared there.

    Signed-off-by: Frank Lichtenheld
    Cc: Michal Januszewski
    Cc: "Antonino A. Daplas"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Frank Lichtenheld
     
  • chipsfb uses PCI interfaces and should depend on PCI.

    CC drivers/video/chipsfb.o
    drivers/video/chipsfb.c: In function 'chipsfb_pci_init':
    drivers/video/chipsfb.c:378: error: implicit declaration of function 'pci_request_region'
    drivers/video/chipsfb.c:435: error: implicit declaration of function 'pci_release_region'
    make[2]: *** [drivers/video/chipsfb.o] Error 1
    make[1]: *** [drivers/video] Error 2
    make: *** [drivers] Error 2

    !CONFIG_PCI causes the build to fail.

    Signed-off-by: Randy Dunlap
    Cc: Kamalesh Babulal
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • When PCMCIA_DEBUG is set, cm40x0_cs.c and cm4000_cs.c don't build because the
    definition of reader_to_dev uses a non-existent handle field of the struct
    pcmcia_device in the call to handle_to_dev. As handle_to_dev works on struct
    pcmcia_device, the fix is quite trivial.

    Signed-off-by: Pascal Terjan
    Cc: Harald Welte
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pascal Terjan
     
  • This should resolve these bug reports of the modem not working:
    http://bugzilla.kernel.org/show_bug.cgi?id=4355
    http://www.linuxquestions.org/questions/linux-newbie-8/connect-script-failed-on-ppp-go-123975/

    I don't have hardware to test this, but the initial report in the kernel
    bugzilla indicates that this change fixed the problem.

    Signed-off-by: Bjorn Helgaas
    Cc: Dmitry Vavilov
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bjorn Helgaas
     
  • The size argument passed to memset is wrong.

    Signed-off-by Li Zefan
    Acked-by: Evgeniy Polyakov
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Li Zefan
     
  • The size passed to memset is wrong.

    Signed-off-by Li Zefan
    Acked-by: Geert Uytterhoeven
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Li Zefan
     
  • Export the NVRAM on DS1307 and DS1338 chips, like several of the
    other drivers do for such combination RTC-and-NVRAM chips.

    Signed-off-by: David Brownell
    Acked-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     
  • Several of the RTC drivers are exporting binary "nvram" files in sysfs. Such
    NVRAM (or on many systems, EEPROM) data is often initialized during system
    manufacture to hold data about identity (serial numbers, Ethernet addresses,
    etc), configuration, calibration, and so forth.

    This patch improves integrity and security of those files:

    - Correctly initializes the size in one of the two cases where
    that was not yet being done.

    - Improves system security/integrity by making this state not
    be world-writable by default.

    Letting arbitrary userspace code mangle such state by default is at least Not
    A Good Thing; and it could sometimes be worse, depending on the particular
    data that might be corrupted. (I disregard the paranoiac "don't let anyone
    read it either" approach. Anyone storing passwords in such memory doesn't
    really care about security.)

    Signed-off-by: David Brownell
    Acked-by: Atsushi Nemoto
    Cc: Torsten Ertbjerg Rasmussen
    Cc: Mark Zhan
    Cc: Thomas Hommel
    Acked-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     
  • The RTC "hctosys" mechanism expects that RTC clock will use UTC, not local
    time (e.g. PST). Say so in Kconfig and in the kernel message.

    (Strictly speaking, the RTC clock should be tracking the POSIX epoch. That's
    not worth going into here. Goofing timezones means clocks are wrong by many
    hours; the POSIX-v-UTC differences just cost seconds.)

    Signed-off-by: David Brownell
    Acked-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     
  • When backlight_device_register() fails, return after undo initialization, do
    not try to use pointer that just was reset to NULL

    This fixes this oops:

    [ 1595.177672] [] show_trace_log_lvl+0x1a/0x30
    [ 1595.177706] [] show_trace+0x12/0x20
    [ 1595.177718] [] dump_stack+0x15/0x20
    [ 1595.177728] [] kobject_shadow_add+0x125/0x1c0
    [ 1595.177754] [] kobject_add+0xa/0x10
    [ 1595.177764] [] device_add+0x97/0x5d0
    [ 1595.177776] [] device_register+0x12/0x20
    [ 1595.177786] [] backlight_device_register+0x9f/0x110 [backlight]
    [ 1595.177814] [] toshiba_acpi_init+0x117/0x15e [toshiba_acpi]
    [ 1595.177834] [] sys_init_module+0xfd/0x14e0
    [ 1595.177871] [] sysenter_past_esp+0x5f/0x99
    [ 1595.177883] =======================
    [ 1595.177890] Could not register toshiba backlight device
    [ 1595.177985] BUG: unable to handle kernel NULL pointer dereference at virtual address 00000004
    ...
    [ 1595.394097] EIP: 0060:[] Not tainted VLI
    [ 1595.394101] EFLAGS: 00010282 (2.6.23-rc9-1avb #24)
    [ 1595.480081] EIP is at toshiba_acpi_init+0x143/0x15e [toshiba_acpi]

    Signed-off-by: Andrey Borzenkov
    Cc: John Belmonte
    Acked-by: Richard Purdie
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrey Borzenkov
     

14 Nov, 2007

11 commits


13 Nov, 2007

13 commits

  • This patch reverts Eric's commit 2b008b0a8e96b726c603c5e1a5a7a509b5f61e35

    It diets .text & .data section of the kernel if CONFIG_NET_NS is not set.
    This is safe after list operations cleanup.

    Signed-of-by: Denis V. Lunev
    Signed-off-by: David S. Miller

    Denis V. Lunev
     
  • Fix incorrect length for strncat by replacing it with strlcat

    Signed-off-by: Roel Kluin
    Signed-off-by: David S. Miller

    Roel Kluin
     
  • With ' 25)'
    will still cause the function to return -1,

    Signed-off-by: Roel Kluin
    Signed-off-by: David S. Miller

    Roel Kluin
     
  • This patch updates the version number to 3.86

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • This patch changes the PHY type reported through ethtool for copper
    devices from MII to TP. The latter is more accurate.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • This patch adds the A1 revision of 5784, 5764, and 5761, and applies all
    previous bugfixes. In places where the list of devices gets too long,
    the patch uses a new TG3_FLG3_5761_5784_AX_FIXES flag instead.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • Previous devices hardcoded the PCI Maximum Read Request Size to 4K. To
    better comply with the PCI spec, the hardware now defaults the MRRS to
    512 bytes. This will yield poor driver performance if left untouched.
    This patch increases the MRRS to 4K on driver initialization.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • Internal hardware timers become inaccurate after link events. Clock
    frequency switches performed by the CPMU fail to adjust timer
    prescalers. The fix is to detect core clock frequency changes during
    link events and adjust the timer prescalers accordingly.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • Most 5784 / 5764 LED modes do not work as expected because of a hardware
    bug. This patch forces the LED mode to be in MAC LED mode.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • New CPMU devices contend with the GPHY for power management. The GPHY
    autopowerdown feature is enabled by default in the PHY and thus needs to
    be disabled after every PHY reset.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • This patch adds the LINK_SPEED mode to the list of CPMU modes that can
    cause the loopback tests to fail. These bugs are planned to be fixed in
    future revisions of the chip, so the patch qualifies the fixes as such.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • Newer devices contain bootcode in the chip's private ROM area. This
    bootcode is called selfboot. Selfboot can be patched in the device's
    NVRAM and the patches can have several formats. In one particular
    format, the checksum calculation needs to be slightly modified. This
    patch adjusts the NVRAM test code for that case, and add support for the
    missing formats.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • 5784 and 5764 devices lock up when the link speed is 10Mbps, the CPMU
    link speed mode is enabled, and the MAC clock is running at 1.5Mhz. The
    fix is to run the MAC clock at faster speeds.

    Signed-off-by: Matt Carlson
    Signed-off-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson