1. 27 3月, 2009 1 次提交
  2. 26 3月, 2009 7 次提交
  3. 24 3月, 2009 1 次提交
  4. 17 2月, 2009 1 次提交
  5. 16 2月, 2009 1 次提交
    • P
      net: new user space API for time stamping of incoming and outgoing packets · cb9eff09
      Patrick Ohly 提交于
      User space can request hardware and/or software time stamping.
      Reporting of the result(s) via a new control message is enabled
      separately for each field in the message because some of the
      fields may require additional computation and thus cause overhead.
      User space can tell the different kinds of time stamps apart
      and choose what suits its needs.
      
      When a TX timestamp operation is requested, the TX skb will be cloned
      and the clone will be time stamped (in hardware or software) and added
      to the socket error queue of the skb, if the skb has a socket
      associated with it.
      
      The actual TX timestamp will reach userspace as a RX timestamp on the
      cloned packet. If timestamping is requested and no timestamping is
      done in the device driver (potentially this may use hardware
      timestamping), it will be done in software after the device's
      start_hard_xmit routine.
      Signed-off-by: NPatrick Ohly <patrick.ohly@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cb9eff09
  6. 01 2月, 2009 1 次提交
  7. 27 1月, 2009 1 次提交
  8. 16 1月, 2009 2 次提交
    • H
      avr32: fix out-of-range rjmp instruction on large kernels · 61f3632f
      Haavard Skinnemoen 提交于
      Use .subsection to place fixups closer to their jump targets. This
      increases the maximum size of the kernel before we get link errors
      significantly.
      
      The problem here is that we don't have a "call"-ish pseudo-instruction
      to use instead of rjmp...we could add one, but that means we'll have to
      wait for a new toolchain release, wait until we're fairly sure most
      people are using it, etc...
      
      As an added bonus, it should decrease the RAM footprint slightly,
      though it might pollute the icache a bit more.
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      61f3632f
    • B
      avr32: Fix out-of-range rcalls in large kernels · 8d29b7b9
      Ben Nizette 提交于
      Replace handcoded rcall instructions with the call pseudo-instruction.
      For kernels too far over 1MB the rcall instruction can't reach and
      linking will fail.  We already call the final linker with --relax which
      converts call pseudo-instructions to the right things anyway.
      
      This fixes
      
      arch/avr32/kernel/built-in.o: In function `syscall_exit_work':
      (.ex.text+0x198): relocation truncated to fit: R_AVR32_22H_PCREL against symbol `schedule' defined in .sched.text section in kernel/built-in.o
      arch/avr32/kernel/built-in.o: In function `fault_exit_work':
      (.ex.text+0x3b6): relocation truncated to fit: R_AVR32_22H_PCREL against symbol `schedule' defined in .sched.text section in kernel/built-in.o
      
      But I'm still left with
      
      arch/avr32/kernel/built-in.o:(.fixup+0x2): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+45a
      arch/avr32/kernel/built-in.o:(.fixup+0x8): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+8ea
      arch/avr32/kernel/built-in.o:(.fixup+0xe): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+abe
      arch/avr32/kernel/built-in.o:(.fixup+0x14): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+ac8
      arch/avr32/kernel/built-in.o:(.fixup+0x1a): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+ad2
      arch/avr32/kernel/built-in.o:(.fixup+0x20): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+adc
      arch/avr32/kernel/built-in.o:(.fixup+0x26): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+ae6
      arch/avr32/kernel/built-in.o:(.fixup+0x2c): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+af0
      arch/avr32/kernel/built-in.o:(.fixup+0x32): additional relocation overflows omitted from the output
      
      These are caused by a similar problem with 'rjmp' instructions.
      Unfortunately, there's no easy fix for these at the moment since we
      don't have a arbitrary-range 'jmp' instruction similar to 'call'.
      Signed-off-by: NBen Nizette <bn@niasdigital.com>
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      8d29b7b9
  9. 15 1月, 2009 1 次提交
  10. 13 1月, 2009 1 次提交
  11. 07 1月, 2009 7 次提交
  12. 06 1月, 2009 3 次提交
  13. 05 1月, 2009 6 次提交
  14. 01 1月, 2009 2 次提交
  15. 18 12月, 2008 2 次提交
  16. 17 12月, 2008 2 次提交
  17. 13 12月, 2008 1 次提交