1. 11 11月, 2008 2 次提交
  2. 04 11月, 2008 1 次提交
  3. 01 11月, 2008 2 次提交
  4. 28 10月, 2008 1 次提交
  5. 23 10月, 2008 1 次提交
  6. 25 9月, 2008 1 次提交
    • D
      wireless: Read scan flags correctly on x86-64 · 9930ccee
      David Kilroy 提交于
      The SIOCSIWSCAN handler is passed data in an iw_point structure. Some
      drivers erronously use an iw_param instead.
      
      On 32 bit architectures the difference isn't noticed as the flags
      parameter tends to be the only one used by scan handlers and is at the
      same offset.
      
      On 64 bit architectures the pointer in the iw_point structure means the
      flag parameter is at different offsets in these structures.
      
      Thanks to Jean Tourrilhes for tracking this down for orinoco, and Pavel
      Roskin for confirming the fix and identifying other suspect handlers.
      Signed-off-by: NDavid Kilroy <kilroyd@googlemail.com>
      Acked-by: NPavel Roskin <proski@gnu.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      9930ccee
  7. 16 9月, 2008 1 次提交
  8. 03 9月, 2008 1 次提交
    • D
      orinoco: Multicast to the specified addresses · 667d4100
      David Kilroy 提交于
      When multicasting the driver sets the number of group addresses using
      the count from the previous set multicast command. In general this means
      you have to set the multicast addresses twice to get the behaviour you
      want.
      
      If we were multicasting, and reduce the number of addresses we are
      multicasting to, then the driver would write uninitialised data from the
      stack into the group addresses to multicast to.
      
      Only write the multicast addresses we have specifically set.
      Signed-off-by: NDavid Kilroy <kilroyd@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      667d4100
  9. 23 8月, 2008 13 次提交
  10. 07 8月, 2008 1 次提交
    • W
      [netdrvr] Drivers should not set IFF_* flag themselves · c16d1185
      Wang Chen 提交于
      Some hardware set promisc when they are requested to set IFF_ALLMULTI flag.
      It's ok, but if drivers set IFF_PROMISC flag when they set promisc,
      it will broken upper layer handle for promisc and allmulti.
      In addition, drivers can use their own hardware programming to make it.
      So do not allow drivers to set IFF_* flags.
      
      This is a general driver fix, so I didn't split it to pieces and send
      to specific driver maintainers.
      Signed-off-by: NWang Chen <wangchen@cn.fujitsu.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      c16d1185
  11. 17 6月, 2008 1 次提交
    • D
      wext: Emit event stream entries correctly when compat. · ccc58057
      David S. Miller 提交于
      Three major portions to this change:
      
      1) Add IW_EV_COMPAT_LCP_LEN, IW_EV_COMPAT_POINT_OFF,
         and IW_EV_COMPAT_POINT_LEN helper defines.
      
      2) Delete iw_stream_check_add_*(), they are unused.
      
      3) Add iw_request_info argument to iwe_stream_add_*(), and use it to
         size the event and pointer lengths correctly depending upon whether
         IW_REQUEST_FLAG_COMPAT is set or not.
      
      4) The mechanical transformations to the drivers and wireless stack
         bits to get the iw_request_info passed down into the routines
         modified in #3.  Also, explicit references to IW_EV_LCP_LEN are
         replaced with iwe_stream_lcp_len(info).
      
      With a lot of help and bug fixes from Masakazu Mokuno.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ccc58057
  12. 29 1月, 2008 2 次提交
  13. 11 10月, 2007 1 次提交
  14. 26 4月, 2007 3 次提交
  15. 08 2月, 2007 2 次提交
  16. 22 11月, 2006 1 次提交
  17. 17 10月, 2006 1 次提交
  18. 07 10月, 2006 1 次提交
  19. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  20. 26 9月, 2006 1 次提交
  21. 14 9月, 2006 1 次提交
  22. 30 8月, 2006 1 次提交