1. 03 Jul, 2006 6 commits
  2. 02 Jul, 2006 1 commit
    • Stefan Richter's avatar
      [PATCH] ieee1394: fix cosmetic problem in speed probe · d7530a1e
      Stefan Richter authored
      If ieee1394.h::IEEE1394_SPEED_MAX is bigger than the actual speed of an
      1394b host adapter and the speed to another 1394b node was probed, a
      bigger speed than actually used was kept in host->speed[n].  The only
      resulting problem so far was sbp2 displaying bogus values in the syslog,
      e.g. S3200 for actual S800 connections if IEEE1394_SPEED_MAX was S3200.
      But other high-level drivers which access this field could get into more
      trouble.  (Eth1394 is the only other in-tree driver which does so.  It
      seems it is not affected.)
      Nodemgr now clips this value according to the host adapter's link speed.
      A pointer expression in nodemgr_check_speed is also changed for clarity.
      Signed-off-by: default avatarStefan Richter <stefanr@s5r6.in-berlin.de>
      Signed-off-by: default avatarBen Collins <bcollins@ubuntu.com>
  3. 30 Jun, 2006 1 commit
  4. 25 Jun, 2006 1 commit
  5. 12 Jun, 2006 1 commit
    • Ben Collins's avatar
      ieee1394: support for slow links or slow 1394b phy ports · 647dcb5f
      Ben Collins authored
      Add support for the following types of hardware:
       + nodes that have a link speed < PHY speed
       + 1394b PHYs that are less than S800 capable
       + 1394b/1394a adapter cable between two 1394b PHYs
      Also, S1600 and S3200 are now supported if IEEE1394_SPEED_MAX is raised.
      A probing function is added to nodemgr's config ROM fetching routine
      which adjusts the allowable speed if an access problem was encountered.
      Pros and Cons of the approach:
       + minimum code footprint to support this less widely used hardware
       + nearly no overhead for unaffected hardware
       - ineffective before nodemgr began to read the ROM of affected nodes
       - ineffective if ieee1394 is loaded with disable_nodemgr=1
      The speed map CSRs which are published to the bus are not touched by the
      Signed-off-by: default avatarStefan Richter <stefanr@s5r6.in-berlin.de>
      Cc: Hakan Ardo <hakan@debian.org>
      Cc: Calculex <linux@calculex.com>
      Cc: Robert J. Kosinski <robk@cmcherald.com>
      Signed-off-by: default avatarBen Collins <bcollins@ubuntu.com>
  6. 04 Jan, 2006 1 commit
  7. 12 Dec, 2005 3 commits
  8. 05 Dec, 2005 1 commit
  9. 01 Dec, 2005 2 commits
  10. 07 Nov, 2005 1 commit
  11. 28 Oct, 2005 1 commit
  12. 30 Sep, 2005 2 commits
  13. 07 Sep, 2005 1 commit
    • Olaf Hering's avatar
      [PATCH] provide MODALIAS= enviroment variable to autoload ieee1394 modules via udev · 9b19d85a
      Olaf Hering authored
      Old 2.6.13 hotplug enviroment for 'plug in firewire disk' event:
      ==> debug.01139.ieee1394.add.8211 <==
      set -- ieee1394
      Module spb2 is not loaded.
      grep sbp2 /lib/modules/2.6.13-20050901172817-default/modules.alias
      alias ieee1394:ven*mo*sp0000609Ever00010483* sbp2
      printf 'ieee1394:ven%08Xmo%08Xsp%08Xver%08X\n' '0x000000' '0x001010' '0x00609e' '0x010483'
      modprobe -v ieee1394:ven00000000mo00001010sp0000609Ever00010483
      insmod /lib/modules/2.6.13-20050901172817-default/kernel/drivers/ieee1394/sbp2.ko
      Providing a MODALIAS= enviroment variable with the content above will fix it.
      Signed-off-by: default avatarOlaf Hering <olh@suse.de>
      Cc: Ben Collins <bcollins@debian.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  14. 10 Jul, 2005 1 commit
    • Ben Collins's avatar
      [PATCH] Sync up ieee-1394 · 1934b8b6
      Ben Collins authored
      Lots of this patch is trivial code cleanups (static vars were being
      intialized to 0, etc).
      There's also some fixes for ISO transmits (max buffer handling).
      Aswell, we have a few fixes to disable IRM capabilites correctly.  We've
      also disabled, by default some generally unused EXPORT symbols for the
      sake of cleanliness in the kernel.  However, instead of removing them
      completely, we felt it necessary to have a config option that allowed
      them to be enabled for the many projects outside of the main kernel tree
      that use our API for driver development.
      The primary reason for this patch is to revert a MODE6->MODE10 RBC
      conversion patch from the SCSI maintainers.  The new conversions handled
      directly in the scsi layer do not seem to work for SBP2.  This patch
      reverts to our old working code so that users can enjoy using Firewire
      disks and dvd drives again.
      We are working with the SCSI maintainers to resolve this issue outside
      of the main kernel tree.  We'll merge the patch once the SCSI layer's
      handling of the MODE10 conversion is working for us.
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  15. 25 Jun, 2005 1 commit
    • Christoph Lameter's avatar
      [PATCH] Cleanup patch for process freezing · 3e1d1d28
      Christoph Lameter authored
      1. Establish a simple API for process freezing defined in linux/include/sched.h:
         frozen(process)		Check for frozen process
         freezing(process)		Check if a process is being frozen
         freeze(process)		Tell a process to freeze (go to refrigerator)
         thaw_process(process)	Restart process
         frozen_process(process)	Process is frozen now
      2. Remove all references to PF_FREEZE and PF_FROZEN from all
         kernel sources except sched.h
      3. Fix numerous locations where try_to_freeze is manually done by a driver
      4. Remove the argument that is no longer necessary from two function calls.
      5. Some whitespace cleanup
      6. Clear potential race in refrigerator (provides an open window of PF_FREEZE
         cleared before setting PF_FROZEN, recalc_sigpending does not check
      This patch does not address the problem of freeze_processes() violating the rule
      that a task may only modify its own flags by setting PF_FREEZE. This is not clean
      in an SMP environment. freeze(process) is therefore not SMP safe!
      Signed-off-by: default avatarChristoph Lameter <christoph@lameter.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  16. 20 Jun, 2005 2 commits
  17. 17 May, 2005 1 commit
  18. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      Let it rip!