08 Oct, 2007

1 commit


05 Oct, 2007

2 commits

  • The way the current CPM binding describes available multi-user (a.k.a.
    dual-ported) RAM doesn't work well when there are multiple free regions,
    and it doesn't work at all if the region doesn't begin at the start of
    the muram area (as the hardware needs to be programmed with offsets into
    this area). The latter situation can happen with SMC UARTs on CPM2, as its
    parameter RAM is relocatable, u-boot puts it at zero, and the kernel doesn't
    support moving it.

    It is now described with a muram node, similar to QE. The current CPM
    binding is sufficiently recent (i.e. never appeared in an official release)
    that compatibility with existing device trees is not an issue.

    The code supporting the new binding is shared between cpm1 and cpm2, rather
    than remain separated. QE should be able to use this code as well, once
    minor fixes are made to its device trees.

    Signed-off-by: Scott Wood
    Signed-off-by: Kumar Gala

    Scott Wood
     
  • The localbus node is used to describe devices that are connected via a chip
    select or similar mechanism. The advantages over placing the devices under
    the root node are that it can be probed without probing other random things
    under the root, and that the description of which chip select a given device
    uses can be used to set up mappings if the firmware failed to do so in a
    useful manner.

    cuboot-pq2 is updated to match the binding; previously, it called itself
    chipselect rather than localbus, and used phandle linkage between the
    actual bus node and the control node (the current agreement is to simply use
    the fully-qualified address of the control registers, and ignore the overlap
    with the IMMR node).

    Signed-off-by: Scott Wood
    Signed-off-by: Kumar Gala

    Scott Wood
     

04 Oct, 2007

1 commit

  • This introduces a new device binding for the CPM and other devices on
    these boards. Some of the changes include:

    1. Proper namespace scoping for Freescale compatibles and properties.

    2. Use compatible rather than things like device_type and model
    to determine which particular variant of a device is present.

    3. Give the drivers the relevant CPM command word directly, rather than
    requiring it to have a lookup table based on device-id, SCC v. SMC, and
    CPM version.

    4. Specify the CPCR and the usable DPRAM region in the CPM's reg property.

    Boards that do not require the legacy bindings should select
    CONFIG_PPC_CPM_NEW_BINDING to enable the of_platform CPM devices. Once
    all existing boards are converted and tested, the config option can
    become default y to prevent new boards from using the old model. Once
    arch/ppc is gone, the config option can be removed altogether.

    Signed-off-by: Scott Wood
    Acked-by: David Gibson
    Signed-off-by: Kumar Gala

    Scott Wood
     

03 Oct, 2007

1 commit


01 Oct, 2007

1 commit


27 Sep, 2007

1 commit


25 Sep, 2007

1 commit


21 Sep, 2007

1 commit

  • Emil Medve points out that this documentation file uses CRLF line
    endings, which means that if you use

    [core]
    autocrlf=input

    (which makes sense if you ever develop under Windows, for example, or if
    you use other broken tools) in your git config, git will always complain
    about the file being dirty.

    This removes the bogus DOS line endings, and removes whitespace at the
    end of line.

    Cc: Emil Medve
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

20 Sep, 2007

1 commit


18 Sep, 2007

2 commits


17 Sep, 2007

3 commits

  • Len Brown
     
  • Name it thinkpad-acpi version 0.16 to avoid any confusion with some 0.15
    thinkpad-acpi development snapshots and backports that had input layer
    support, but no hotkey_report_mode support.

    Signed-off-by: Henrique de Moraes Holschuh
    Signed-off-by: Len Brown

    Henrique de Moraes Holschuh
     
  • Revert new 2.6.23 CONFIG_THINKPAD_ACPI_INPUT_ENABLED Kconfig option because
    it would create a legacy we don't want to support.

    CONFIG_THINKPAD_ACPI_INPUT_ENABLED was added to try to fix an issue that is
    now moot with the addition of the netlink ACPI event report interface to
    the ACPI core.

    Now that ACPI core can send events over netlink, we can use a different
    strategy to keep backwards compatibility with older userspace, without the
    need for the CONFIG_THINKPAD_ACPI_INPUT_ENABLED games. And it arrived
    before CONFIG_THINKPAD_ACPI_INPUT_ENABLED made it to a stable mainline
    kernel, even, which is Good.

    This patch is in sync with some changes to thinkpad-acpi backports, that
    will keep things sane for userspace across different combinations of kernel
    versions, thinkpad-acpi backports (or the lack thereof), and userspace
    capabilities:

    Unless a module parameter is used, thinkpad-acpi will now behave in such a
    way that it will work well (by default) with userspace that still uses only
    the old ACPI procfs event interface and doesn't care for thinkpad-acpi
    input devices.

    It will also always work well with userspace that has been updated to use
    both the thinkpad-acpi input devices, and ACPI core netlink event
    interface, regardless of any module parameter.

    The module parameter was added to allow thinkpad-acpi to work with
    userspace that has been partially updated to use thinkpad-acpi input
    devices, but not the new ACPI core netlink event interface. To use this
    mode of hot key reporting, one has to specify the hotkey_report_mode=2
    module parameter.

    The thinkpad-acpi driver exports the value of hotkey_report_mode through
    sysfs, as well. thinkpad-acpi backports to older kernels, that do not
    support the new ACPI core netlink interface, have code to allow userspace
    to switch hotkey_report_mode at runtime through sysfs. This capability
    will not be provided in mainline thinkpad-acpi as it is not needed there.

    Signed-off-by: Henrique de Moraes Holschuh
    Cc: Michael S. Tsirkin
    Cc: Hugh Dickins
    Cc: Richard Hughes
    Signed-off-by: Len Brown

    Henrique de Moraes Holschuh
     

16 Sep, 2007

2 commits

  • * 'upstream-linus' of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6:
    drivers/net/pcmcia/3c589_cs: fix port configuration switcheroo
    sk98lin: resurrect driver
    ucc_geth: fix compilation
    mv643xx_eth: Fix tx_bytes stats calculation
    As struct iw_point is bi-directional payload, we should copy back the content
    [PATCH] bcm43xx: Fix cancellation of work queue crashes
    spidernet: fix interrupt reason recognition
    ehea: fix last_rx update
    ehea: propagate physical port state
    Fix a lock problem in generic phy code
    sky2: restore multicast list on resume and other ops
    atl1: disable broken 64-bit DMA

    Linus Torvalds
     
  • This reverts commit e1abecc48938fbe1966ea6e78267fc673fa59295.

    The driver works on some hardware that skge doesn't handle yet.

    Signed-off-by: Stephen Hemminger
    Signed-off-by: Jeff Garzik

    Stephen Hemminger
     

15 Sep, 2007

2 commits


13 Sep, 2007

2 commits


12 Sep, 2007

4 commits


11 Sep, 2007

1 commit


31 Aug, 2007

1 commit

  • We find that SB700 and SB800 use the same SMBus device ID as SB600, which is
    0x4385, instead of the already submitted 0x4395.

    Besides removing the wrong SB700 device ID, add SB800 support to kernel, by
    renaming the PCI_DEVICE_ID_ATI_IXP600_SMBUS into
    PCI_DEVICE_ID_ATI_SBX00_SMBUS.

    Signed-off-by: Shane Huang
    Signed-off-by: Jean Delvare
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Shane Huang
     

25 Aug, 2007

3 commits


24 Aug, 2007

4 commits


23 Aug, 2007

6 commits

  • Updates to the MAINTAINERS file and documentation for 9p to point to the
    swik wiki versus the outdated sf.net page. Also updated some email addresses
    and added pointers to papers which better describe the implementation and
    application of the Linux 9p client.

    Signed-off-by: Eric Van Hensbergen

    Eric Van Hensbergen
     
  • Commit b663a79c191508f27cd885224b592a878c0ba0f6 ("taskstats: add
    context-switch counters") incorrectly removed a comma from a printf
    statement. This causes corruption in the output printing or a seg
    fault.

    Signed-off-by: Michael Neuling
    Acked-by: Balbir Singh
    Signed-off-by: Linus Torvalds

    Michael Neuling
     
  • I couldn't find any memory policy documentation in the Documentation
    directory, so here is my attempt to document it.

    There's lots more that could be written about the internal design--including
    data structures, functions, etc. However, if you agree that this is better
    that the nothing that exists now, perhaps it could be merged. This will
    provide a baseline for updates to document the many policy patches that are
    currently being worked.

    Signed-off-by: Lee Schermerhorn
    Cc: Christoph Lameter
    Cc: Andi Kleen
    Cc: Michael Kerrisk
    Acked-by: Rob Landley
    Acked-by: Mel Gorman
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Lee Schermerhorn
     
  • This useful interface is hardly mentioned anywhere in the in-tree
    documentation.

    Signed-off-by: Rolf Eike Beer
    Cc: Tejun Heo
    Acked-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Rolf Eike Beer
     
  • Hello,

    I've noticed that in Document/HOWTO the url address:
    http://sosdg.org/~coywolf/lxr/
    has changed to
    http://users.sosdg.org/~qiyong/lxr/
    from the website.

    -- qiyong

    Signed-off-by: Qi Yong
    Signed-off-by: Greg Kroah-Hartman

    Qi Yong
     
  • This is a Documentation/HOWTO korean version of 2.6.23-rc1
    The header is refered to a japanese's one.

    From: Minchan Kim
    Signed-off-by: Greg Kroah-Hartman

    Minchan Kim