1. 11 Aug, 2005 4 commits
    • Amit Kucheria's avatar
      [PATCH] ARM: OMAP: Enable AUTOIDLE bit for OMAP16xx · 90ab2b4c
      Amit Kucheria authored
      Enable AUTOIDLE bit for OMAP16xx
      90ab2b4c
    • Imre Deak's avatar
      [PATCH] ARM: OMAP: DMA fixes · 81db4803
      Imre Deak authored
      Set the LCD DMA active flag _before_ starting the transfer and
      Mask CSR to avoid unnecessary callbacks.
      81db4803
    • Tony Lindgren's avatar
      Merge with ../linux-2.6 · 77f0154f
      Tony Lindgren authored
      77f0154f
    • Herbert Xu's avatar
      [TCP]: Adjust {p,f}ackets_out correctly in tcp_retransmit_skb() · b5da623a
      Herbert Xu authored
      Well I've only found one potential cause for the assertion
      failure in tcp_mark_head_lost.  First of all, this can only
      occur if cnt > 1 since tp->packets_out is never zero here.
      If it did hit zero we'd have much bigger problems.
      
      So cnt is equal to fackets_out - reordering.  Normally
      fackets_out is less than packets_out.  The only reason
      I've found that might cause fackets_out to exceed packets_out
      is if tcp_fragment is called from tcp_retransmit_skb with a
      TSO skb and the current MSS is greater than the MSS stored
      in the TSO skb.  This might occur as the result of an expiring
      dst entry.
      
      In that case, packets_out may decrease (line 1380-1381 in
      tcp_output.c).  However, fackets_out is unchanged which means
      that it may in fact exceed packets_out.
      
      Previously tcp_retrans_try_collapse was the only place where
      packets_out can go down and it takes care of this by decrementing
      fackets_out.
      
      So we should make sure that fackets_out is reduced by an appropriate
      amount here as well.
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b5da623a
  2. 10 Aug, 2005 24 commits
  3. 09 Aug, 2005 12 commits