24 Nov, 2011

1 commit


23 Nov, 2011

2 commits

  • CPSW module includes an interrupt pacing block that can
    be programmed to throttle the rate at which interrupts are
    generated. This patch implements interrupt pacing logic that can
    be controlled through the ethtool interface(only rx_coalesce_usecs
    param is honored)

    Signed-off-by: Chandan Nath

    Chandan Nath
     
  • This patch is added to route CPSW interrupts through ICSS module.
    CPSW CPSW_RX and CPSW_TX interrupts are not directly used from CPSW
    and instead they are routed through Timer module. This is done as an
    software workaround for enabling interrupt pacing feature. As interrupt
    Pacing works on C0_RX_PULSE interrupt connection to A8 INTC, which is
    not connected to Cortex A8 interrupt controller directly due to hw issue,
    it prevents interrupt pacing to work in AM33xx EVM. Therefore, Timer
    capture module is used to pickup these interrupts and routed to A8 INTC.

    Signed-off-by: Chandan Nath
    Signed-off-by: Afzal Mohammed

    Afzal Mohammed
     

21 Nov, 2011

1 commit


16 Nov, 2011

1 commit

  • Bosch D_CAN controller is a full-CAN implementation which is compliant
    to CAN protocol version 2.0 part A and B. Bosch D_CAN user manual can be
    obtained from:

    http://www.semiconductors.bosch.de/media/en/pdf/ipmodules_1/can/d_can_users_manual_111.pdf

    This patch adds the support for this controller.
    The following are the design choices made while writing the controller
    driver:
    1. Interface Register set IF1 has be used for transmit and IF2 is used for
    receive message objects.
    2. Out of the total Message objects available, half of it are kept aside for RX
    purposes and the rest for TX purposes.
    3. NAPI implementation is such that both the TX and RX paths functions
    in polling mode.

    This patch adds the dcan driver support to am335x chip.

    Signed-off-by: Anil Kumar Ch

    Anil Kumar Ch
     

14 Nov, 2011

2 commits


27 Oct, 2011

11 commits


20 Oct, 2011

2 commits

  • Correct the wrong parameter for setting EEE for RTL8111E-VL.

    Signed-off-by: Hayes Wang
    Signed-off-by: David S. Miller

    hayeswang
     
  • Due to commit 92fc43b4159b518f5baae57301f26d770b0834c9 ("r8169: modify the
    flow of the hw reset."), rtl8169_hw_reset stomps during driver shutdown on
    RxConfig bits which are needed for WOL on some versions of the hardware.

    As these bits were formerly set from the r81{0x, 68}_pll_power_down methods,
    factor them out for use in the driver shutdown (rtl_shutdown) handler.

    I favored __rtl8169_get_wol() -hardware state indication- over
    RTL_FEATURE_WOL as the latter has become a good candidate for removal.

    Signed-off-by: Francois Romieu
    Cc: Hayes
    Tested-by: Marc Ballarin
    Signed-off-by: David S. Miller

    françois romieu
     

19 Oct, 2011

6 commits

  • e1000e uses paged frags, so any layer incorrectly pulling bytes from skb
    can trigger a BUG in skb_pull()

    [951.142737] [] skb_pull+0x15/0x17
    [951.142737] [] pptp_rcv_core+0x126/0x19a [pptp]
    [951.152725] [] sk_receive_skb+0x69/0x105
    [951.163558] [] pptp_rcv+0xc8/0xdc [pptp]
    [951.165092] [] gre_rcv+0x62/0x75 [gre]
    [951.165092] [] ip_local_deliver_finish+0x150/0x1c1
    [951.177599] [] ? ip_local_deliver_finish+0x0/0x1c1
    [951.177599] [] NF_HOOK.clone.7+0x51/0x58
    [951.177599] [] ip_local_deliver+0x51/0x55
    [951.177599] [] ip_rcv_finish+0x31a/0x33e
    [951.177599] [] ? ip_rcv_finish+0x0/0x33e
    [951.204898] [] NF_HOOK.clone.7+0x51/0x58
    [951.214651] [] ip_rcv+0x21b/0x246

    pptp_rcv_core() is a nice example of a function assuming everything it
    needs is available in skb head.

    Reported-by: Bradley Peterson
    Signed-off-by: Eric Dumazet
    Signed-off-by: David S. Miller

    Eric Dumazet
     
  • In case we cant transmit skb, we must free it

    Signed-off-by: Eric Dumazet
    CC: Dmitry Kozlov
    Signed-off-by: David S. Miller

    Eric Dumazet
     
  • The bond->recv_probe is called in bond_handle_frame() when
    a packet is received, but bond_close() sets it to NULL. So,
    a panic occurs when both functions work in parallel.

    Why this happen:
    After null pointer check of bond->recv_probe, an sk_buff is
    duplicated and bond->recv_probe is called in bond_handle_frame.
    So, a panic occurs when bond_close() is called between the
    check and call of bond->recv_probe.

    Patch:
    This patch uses a local function pointer of bond->recv_probe
    in bond_handle_frame(). So, it can avoid the null pointer
    dereference.

    Signed-off-by: Mitsuo Hayasaka
    Cc: Jay Vosburgh
    Cc: Andy Gospodarek
    Cc: Eric Dumazet
    Cc: WANG Cong
    Acked-by: Eric Dumazet
    Signed-off-by: David S. Miller

    Mitsuo Hayasaka
     
  • LAN89218 is register compatible with LAN911x.

    Signed-off-by: Phil Edworthy
    Signed-off-by: David S. Miller

    Phil Edworthy
     
  • USE_PHYLIB flag in tg3_remove_one() is being checked incorrectly. This
    results tg3_phy_fini->phy_disconnect is never called and when tg3 module
    is removed.

    In my case this resulted in panics in phy_state_machine calling function
    phydev->adjust_link.

    So correct this check.

    Signed-off-by: Jiri Pirko
    Acked-by: Matt Carlson
    Signed-off-by: David S. Miller

    Jiri Pirko
     
  • There is no check if netconsole is enabled current.
    so when exec echo 1 > enabled;
    the reference of net_device will increment always.

    Signed-off-by: Gao feng
    Acked-by: Flavio Leitner
    Signed-off-by: David S. Miller

    Gao feng
     

11 Oct, 2011

3 commits

  • Due to the 16 bit access to mscan registers there's too much data copied to
    the zero initialized CAN frame when having an odd number of bytes to copy.
    This patch ensures that only the requested bytes are copied by using an
    8 bit access for the remaining byte.

    Reported-by: Andre Naujoks
    Signed-off-by: Oliver Hartkopp
    Signed-off-by: Wolfgang Grandegger
    Signed-off-by: David S. Miller

    Wolfgang Grandegger
     
  • There are some consolidations of NPAR configuration
    when FCoE and iSCSI L2 clients will get the same id,
    in this case FCoE ring will be non-functional.

    Signed-off-by: Dmitry Kravkov
    Signed-off-by: Eilon Greenstein
    Signed-off-by: David S. Miller

    Dmitry Kravkov
     
  • The doorbell register was being unconditionally swapped. In x86, that
    meant it was being swapped to BE and written to the descriptor and to
    memory, depending on the case of blue frame support or writing to
    doorbell register. On PPC, this meant it was being swapped to LE and
    then swapped back to BE while writing to the register. But in the blue
    frame case, it was being written as LE to the descriptor.

    The fix is not to swap doorbell unconditionally, write it to the
    register as BE and convert it to BE when writing it to the descriptor.

    Signed-off-by: Thadeu Lima de Souza Cascardo
    Reported-by: Richard Hendrickson
    Cc: Eli Cohen
    Cc: Yevgeny Petrilin
    Cc: Benjamin Herrenschmidt
    Signed-off-by: David S. Miller

    Thadeu Lima de Souza Cascardo
     

05 Oct, 2011

1 commit


04 Oct, 2011

4 commits

  • The pch_gbe driver has an issue which a network stops,
    when receiving traffic is high.
    In the case, The link down and up are necessary to return a network.

    This patch fixed this issue.

    Signed-off-by: Toshiharu Okada
    Signed-off-by: David S. Miller

    Toshiharu Okada
     
  • When a link was downed during network use,
    there is an issue on which PC freezes.

    This patch fixed this issue.

    Signed-off-by: Toshiharu Okada
    Signed-off-by: David S. Miller

    Toshiharu Okada
     
  • If a VM is saved and restored (or migrated) the netback driver will no
    longer process any Tx packets from the frontend. xenvif_up() does not
    schedule the processing of any pending Tx requests from the front end
    because the carrier is off. Without this initial kick the frontend
    just adds Tx requests to the ring without raising an event (until the
    ring is full).

    This was caused by 47103041e91794acdbc6165da0ae288d844c820b (net:
    xen-netback: convert to hw_features) which reordered the calls to
    xenvif_up() and netif_carrier_on() in xenvif_connect().

    Signed-off-by: David Vrabel
    Cc: Ian Campbell
    Acked-by: Ian Campbell
    Signed-off-by: David S. Miller

    David Vrabel
     
  • During a test where a pair of bonding interfaces using ARP monitoring
    were both brought up and torn down (with an rmmod) repeatedly, a panic
    in the timer code was noticed. I tracked this down and determined that
    any of the bonding functions that ran as workqueue handlers and requeued
    more work might not properly exit when the module was removed.

    There was a flag protected by the bond lock called kill_timers that is
    set when the interface goes down or the module is removed, but many of
    the functions that monitor link status now unlock the bond lock to take
    rtnl first. There is a chance that another CPU running the rmmod could
    get the lock and set kill_timers after the first check has passed.

    This patch does not allow any function to queue work that will make
    itself run unless kill_timers is not set. I also noticed while doing
    this work that bond_resend_igmp_join_requests did not have a check for
    kill_timers, so I added the needed call there as well.

    Signed-off-by: Andy Gospodarek
    Reported-by: Liang Zheng
    Signed-off-by: David S. Miller

    Andy Gospodarek
     

29 Sep, 2011

3 commits

  • If request_irq fails, the ibmveth driver will overwrite
    the rc and end up returning a successful rc on its open
    function, resulting in an oops later when a packet gets
    sent and buffers are not allocated due to the failed open.

    Signed-off-by: Brian King
    Signed-off-by: David S. Miller

    Brian King
     
  • Fix EEH recovery on new P Series platform by
    requesting fundamental reset.

    Signed-off-by: Divy Le Ray
    Signed-off-by: David S. Miller

    Divy Le Ray
     
  • The driver has two warning messages that might be triggered
    by normal use cases. When they appear, the messages give the
    impression of a never ending series of errors.

    This commit changes them to debug messages instead.

    Signed-off-by: Richard Cochran
    Signed-off-by: David S. Miller

    Richard Cochran
     

28 Sep, 2011

3 commits