1. 12 10月, 2005 3 次提交
    • A
      [PATCH] dell_rbu: changes in packet update mechanism · ad6ce87e
      Abhay Salunke 提交于
      In the current dell_rbu code ver 2.0 the packet update mechanism makes the
      user app dump every individual packet in to the driver.
      
      This adds in efficiency as every packet update makes the
      /sys/class/firmware/dell_rbu/loading and data files to disappear and reappear
      again.  Thus the user app needs to wait for the files to reappear to dump
      another packet.  This slows down the packet update tremendously in case of
      large number of packets.  I am submitting a new patch for dell_rbu which will
      change the way we do packet updates;
      
      In the new method the user app will create a new single file which has already
      packetized the rbu image and all the packets are now staged in this file.
      
      This driver also creates a new entry in
      /sys/devices/platform/dell_rbu/packet_size ; the user needs to echo the packet
      size here before downloading the packet file.
      
      The user should do the following:
      
       create one single file which has all the packets stacked together.
       echo the packet size in to /sys/devices/platform/dell_rbu/packet_size.
       echo 1 > /sys/class/firmware/dell_rbu/loading
       cat the packetfile > /sys/class/firmware/dell_rbu/data
       echo 0 > /sys/class/firmware/dell_rbu/loading
      
      The driver takes the file which came through /sys/class/firmware/dell_rbu/data
      and takes chunks of paket_size data from it and place in contiguous memory.
      
      This makes packet update process very efficient and fast.  As all the packet
      update happens in one single operation.  The user can still read back the
      downloaded file from /sys/devices/platform/dell_rbu/data.
      Signed-off-by: NAbhay Salunke <abhay_salunke@dell.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ad6ce87e
    • A
      [PATCH] ppc64: Fix PCI hotplug · e4314bf4
      Anton Blanchard 提交于
      pSeries_irq_bus_setup is marked __devinit but references s7a_workaround
      which is marked __initdata.
      
      Depending on who got the memory for s7a_workaround (and if the value was
      now positive), it was possible for PCI hotplugged devices to have 3
      subtracted from their interrupt number.  This would happen randomly and
      caused me much confusion :)
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e4314bf4
    • C
      [PATCH] s390: ccw device reconnect oops. · e5945b4f
      Cornelia Huck 提交于
      Search for a disconnect ccw_device on the ccw bus rather than on the css
      bus (was a typo in patch I did for the klist conversion).  A cast to an
      embedding ccw_device from an embedded device in a struct subchannel will
      lead us to oopses.
      Signed-off-by: NCornelia Huck <cohuck@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e5945b4f
  2. 11 10月, 2005 15 次提交
  3. 10 10月, 2005 22 次提交