01 Jul, 2006

1 commit


26 Jun, 2006

1 commit


13 Jun, 2006

1 commit

  • 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
    patch.

    Signed-off-by: Stefan Richter
    Cc: Hakan Ardo
    Cc: Calculex
    Cc: Robert J. Kosinski
    Signed-off-by: Ben Collins

    Ben Collins
     

05 Jan, 2006

2 commits


13 Dec, 2005

3 commits

  • Some old 1394-1995 SBP-2 bridges would hang if they received a broadcast write
    request to BROADCAST_CHANNEL before the config ROM was read. Affected devices
    include Datafab MD2-FW2 2.5" HDD and SmartDisk VST FWCDRW-V8 portable CD writer.
    The write request is now directed to specific nodes instead of being broadcast
    to all nodes at once, and it is only performed if a previous read request at
    this register succeeded.

    Fixes an old interoperability problem which was perceived as a 2.6.14-specific
    regression: http://marc.theaimsgroup.com/?t=113190586800003

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre
    (cherry picked from 61c7f775ca25ccfc0e51486103a724fb1a3a08f2 commit)

    Stefan Richter
     
  • After initializing an IEEE 1394 host, broadcast a resume packet. This makes
    remote nodes visible which suspended their ports while the host was down.
    Such nodes had to be unplugged and replugged in order to be recognized.

    Motorola DCT6200 cable reciever was affected, probably other devices too.
    http://marc.theaimsgroup.com/?t=113202715800001

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre
    (cherry picked from 14c0fa243b358c24040ff5f44b60c47aaf6430c3 commit)

    Stefan Richter
     
  • After a bus reset, let nodemgr call high-level update hooks first for nodes
    which do not need to be probed. The main benefit is for a bus with more
    than one SBP-2 device: SBP-2 reconnects will be performed before SBP-2
    logins, thus have a much higher chance to succeed, and their SCSI devices
    will not be blocked much longer than necessary. This was demonstrated for
    Linux 2.4 by Dave Cinege a while ago.

    A better approach would be to perform time-consuming probes in parallel by a
    subthread. I actually plan to implement this for sbp2 but it may take a
    while to get that done and tested. Until then, this tweak is a huge
    improvement for users with multiple SBP-2 devices.

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre

    Stefan Richter
     

06 Dec, 2005

1 commit

  • Some old 1394-1995 SBP-2 bridges would hang if they received a broadcast write
    request to BROADCAST_CHANNEL before the config ROM was read. Affected devices
    include Datafab MD2-FW2 2.5" HDD and SmartDisk VST FWCDRW-V8 portable CD writer.
    The write request is now directed to specific nodes instead of being broadcast
    to all nodes at once, and it is only performed if a previous read request at
    this register succeeded.

    Fixes an old interoperability problem which was perceived as a 2.6.14-specific
    regression: http://marc.theaimsgroup.com/?t=113190586800003

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre

    Stefan Richter
     

02 Dec, 2005

2 commits


07 Nov, 2005

1 commit

  • dv1394, eth1394, ieee1394, ohci1394, pcilynx, raw1394, sbp2c, video1394:
    - use kzalloc
    - provide safer size arguments to kmalloc and kzalloc
    - omit some casts

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre

    Stefan Richter
     

29 Oct, 2005

1 commit

  • In PM v1, all devices were called at SUSPEND_DISABLE level. Then
    all devices were called at SUSPEND_SAVE_STATE level, and finally
    SUSPEND_POWER_DOWN level. However, with PM v2, to maintain
    compatibility for platform devices, I arranged for the PM v2
    suspend/resume callbacks to call the old PM v1 suspend/resume
    callbacks three times with each level in order so that existing
    drivers continued to work.

    Since this is obsolete infrastructure which is no longer necessary,
    we can remove it. Here's an (untested) patch to do exactly that.

    Signed-off-by: Russell King
    Signed-off-by: Greg Kroah-Hartman

    Russell King
     

01 Oct, 2005

2 commits

  • Skip a superfluous pause that occured when the config ROM of a node was
    scanned unsuccessfully. This also occurs if a node without link wrongly
    enables its "link active" self ID flag. A GWCTech 6-port hub does this.

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre
    Cc: Ben Collins
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jody McIntyre
     
  • Units were not detected if the local IRM performed a bus reset. ("The root
    node is not cycle master capable; selecting a new root node and resetting...",
    often seen with iPods and other SBP-2 devices). Rearrange the order of IRM
    duties and node scanning. TODO: Audit the ROM caching and parsing code for
    underlying issues.

    Signed-off-by: Stefan Richter
    Signed-off-by: Jody McIntyre
    Cc: Ben Collins
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jody McIntyre
     

08 Sep, 2005

1 commit


11 Jul, 2005

1 commit

  • 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: Linus Torvalds

    Ben Collins
     

26 Jun, 2005

1 commit

  • 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
    PF_FROZEN).

    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: Christoph Lameter
    Signed-off-by: Linus Torvalds

    Christoph Lameter
     

21 Jun, 2005

2 commits


17 May, 2005

1 commit


17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds