Skip to content
Snippets Groups Projects
  1. Apr 18, 2008
    • Stefan Richter's avatar
      firewire: reread config ROM when device reset the bus · c9755e14
      Stefan Richter authored
      
      When a device changes its configuration ROM, it announces this with a
      bus reset.  firewire-core has to check which node initiated a bus reset
      and whether any unit directories went away or were added on this node.
      
      Tested with an IOI FWB-IDE01AB which has its link-on bit set if bus
      power is available but does not respond to ROM read requests if self
      power is off.  This implements
        - recognition of the units if self power is switched on after fw-core
          gave up the initial attempt to read the config ROM,
        - shutdown of the units when self power is switched off.
      
      Also tested with a second PC running Linux/ieee1394.  When the eth1394
      driver is inserted and removed on that node, fw-core now notices the
      addition and removal of the IPv4 unit on the ieee1394 node.
      
      Signed-off-by: default avatarStefan Richter <stefanr@s5r6.in-berlin.de>
      c9755e14
  2. Feb 21, 2008
  3. Feb 16, 2008
    • Stefan Richter's avatar
      firewire: fix "kobject_add failed for fw* with -EEXIST" · 96b19062
      Stefan Richter authored
      There is a race between shutdown and creation of devices:  fw-core may
      attempt to add a device with the same name of an already existing
      device.  http://bugzilla.kernel.org/show_bug.cgi?id=9828
      
      
      
      Impact of the bug:  Happens rarely (when shutdown of a device coincides
      with creation of another), forces the user to unplug and replug the new
      device to get it working.
      
      The fix is obvious:  Free the minor number *after* instead of *before*
      device_unregister().  This requires to take an additional reference of
      the fw_device as long as the IDR tree points to it.
      
      And while we are at it, we fix an additional race condition:
      fw_device_op_open() took its reference of the fw_device a little bit too
      late, hence was in danger to access an already invalid fw_device.
      
      Signed-off-by: default avatarStefan Richter <stefanr@s5r6.in-berlin.de>
      96b19062
  4. Jan 30, 2008
  5. Oct 16, 2007
  6. Oct 14, 2007
  7. Jul 09, 2007
  8. Jun 20, 2007
  9. May 31, 2007
  10. May 27, 2007
  11. May 10, 2007
  12. Apr 30, 2007
  13. Mar 28, 2007
  14. Mar 20, 2007
  15. Mar 15, 2007
  16. Mar 09, 2007
Loading