Eric Lee / smarc-fsl-linux-kernel

21 Sep, 2007

1 commit

  • be7963b7e   ieee1394: ohci1394: fix initialization if built non-modular ... Browse Code »

    Initialization of ohci1394 was broken according to one reporter if the
    driver was statically linked, i.e. not built as loadable module. Dmesg:

    PCI: Device 0000:02:07.0 not available because of resource collisions
    ohci1394: Failed to enable OHCI hardware.

    This was reported for a Toshiba Satellite 5100-503. The cause is commit
    8df4083c5291b3647e0381d3c69ab2196f5dd3b7 in Linux 2.6.19-rc1 which only
    served purposes of early remote debugging via FireWire. This
    functionality is better provided by the currently out-of-tree driver
    ohci1394_earlyinit. Reversal of the commit was OK'd by Andi Kleen.

    Signed-off-by: Stefan Richter

    Stefan Richter
     

18 Jul, 2007

1 commit

  • 831441862   Freezer: make kernel threads nonfreezable by default ... Browse Code »

    Currently, the freezer treats all tasks as freezable, except for the kernel
    threads that explicitly set the PF_NOFREEZE flag for themselves. This
    approach is problematic, since it requires every kernel thread to either
    set PF_NOFREEZE explicitly, or call try_to_freeze(), even if it doesn't
    care for the freezing of tasks at all.

    It seems better to only require the kernel threads that want to or need to
    be frozen to use some freezer-related code and to remove any
    freezer-related code from the other (nonfreezable) kernel threads, which is
    done in this patch.

    The patch causes all kernel threads to be nonfreezable by default (ie. to
    have PF_NOFREEZE set by default) and introduces the set_freezable()
    function that should be called by the freezable kernel threads in order to
    unset PF_NOFREEZE. It also makes all of the currently freezable kernel
    threads call set_freezable(), so it shouldn't cause any (intentional)
    change of behaviour to appear. Additionally, it updates documentation to
    describe the freezing of tasks more accurately.

    [akpm@linux-foundation.org: build fixes]
    Signed-off-by: Rafael J. Wysocki
    Acked-by: Nigel Cunningham
    Cc: Pavel Machek
    Cc: Oleg Nesterov
    Cc: Gautham R Shenoy
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Rafael J. Wysocki
     

10 Jul, 2007

1 commit

  • 53c96b417   ieee1394: remove old isochronous ABI ... Browse Code »

    Based on patch "the scheduled removal of RAW1394_REQ_ISO_{SEND,LISTEN}"
    from Adrian Bunk, November 20 2006.

    This patch also removes the underlying facilities in ohci1394 and
    disables them in pcilynx. That is, hpsb_host_driver.devctl() and
    hpsb_host_driver.transmit_packet() are no longer used for iso reception
    and transmission.

    Since video1394 and dv1394 only work with ohci1394 and raw1394's rawiso
    interface has never been implemented in pcilynx, pcilynx is now no
    longer useful for isochronous applications.

    raw1394 will still handle the request types but will complete the
    requests with errors that indicate API version conflicts.

    Signed-off-by: Stefan Richter

    Stefan Richter
     

30 Apr, 2007

6 commits

17 Feb, 2007

1 commit

  • 3dc5ea9b3   ieee1394: cycle timer read extension for raw1394 ... Browse Code »

    This implements the simultaneous read of the isochronous cycle timer and
    the system clock (in usecs). This allows to express the exact receive
    time of an ISO packet as a system time with microsecond accuracy.
    http://bugzilla.kernel.org/show_bug.cgi?id=7773

    The counterpart patch for libraw1394 can be found at
    http://thread.gmane.org/gmane.linux.kernel.firewire.devel/8934

    Patch update (Stefan R.): Disable preemption and local interrupts.
    Prevent integer overflow. Add paranoid error checks and kerneldoc to
    hpsb_read_cycle_timer. Move it to other ieee1394_core high-level API
    functions. Change comments. Adjust whitespace. Rename struct
    _raw1394_cycle_timer.

    Signed-off-by: Stefan Richter
    Acked-by: Pieter Palmers
    Acked-by: Dan Dennedy

    Pieter Palmers
     

09 Feb, 2007

2 commits

08 Dec, 2006

2 commits

  • 3015c7397   ieee1394: conditionally export ieee1394_bus_type ... Browse Code »

    Follow-up to patch "Consolidate driver registering":
    Since I plan the lifetime of Linux 2.6.20 to be the deprecation phase
    of CONFIG_IEEE1394_EXPORT_FULL_API, it seems fair to keep all previously
    exported symbols available with this option until this phase is over.

    Signed-off-by: Stefan Richter

    Stefan Richter
     
  • ed30c26ee   ieee1394: Consolidate driver registering ... Browse Code »

    This patch consolidates some bookkeeping for driver registering. It
    closely models what pci_register_driver() does. The main addition is
    that the owner of the driver is set, so we get a proper symlink
    for /sys/bus/ieee1394/driver/*/module.

    Also moves setting of name and bus type into nodemgr. Because of this,
    we can remove the EXPORT_SYMBOL for ieee1394_bus_type, since it's now
    only used in ieee1394.ko.

    Signed-off-by: Stefan Richter

    Ben Collins
     

18 Sep, 2006

3 commits

04 Jul, 2006

1 commit

01 Jul, 2006

1 commit

13 Jun, 2006

2 commits

  • f654240f3   ieee1394_core: switch to kthread API ... Browse Code »

    This gets also rid of the MODPOST warning "drivers/ieee1394/ieee1394.o -
    Section mismatch: reference to .exit.text: from .smp_locks after '' (at
    offset 0x18)".

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Jody McIntyre
    Signed-off-by: Stefan Richter
    Signed-off-by: Andrew Morton
    Signed-off-by: Ben Collins

    Ben Collins
     
  • 647dcb5fa   ieee1394: support for slow links or slow 1394b phy ports ... Browse Code »

    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
     

29 Mar, 2006

2 commits

07 Jan, 2006

1 commit

  • 8c1d286e6   [PATCH] don't freeze firewire on suspend. ... Browse Code »

    We had a report from one loony user who tried out suspend to disk using a
    swap partition on a firewire drive. As the firewire thread was put to
    sleep it didn't work out too well.

    Signed-off-by: Dave Jones
    Cc: Pavel Machek
    Cc: Ben Collins
    Cc: Jody McIntyre
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Dave Jones
     

02 Dec, 2005

3 commits

01 Oct, 2005

1 commit

  • db2fd664f   [PATCH] ieee1394: fix for debug output ... Browse Code »

    Fix debug code so it prints the correct speed (was defaulting to 100, so
    anything > 400 showed only 100).

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

    Jody McIntyre
     

30 Aug, 2005

1 commit

  • 8728b834b   [NET]: Kill skb->list ... Browse Code »

    Remove the "list" member of struct sk_buff, as it is entirely
    redundant. All SKB list removal callers know which list the
    SKB is on, so storing this in sk_buff does nothing other than
    taking up some space.

    Two tricky bits were SCTP, which I took care of, and two ATM
    drivers which Francois Romieu fixed
    up.

    Signed-off-by: David S. Miller
    Signed-off-by: Francois Romieu

    David S. Miller
     

11 Jul, 2005

1 commit

  • 1934b8b65   [PATCH] Sync up ieee-1394 ... Browse Code »

    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

  • 3e1d1d28d   [PATCH] Cleanup patch for process freezing ... Browse Code »

    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

1 commit

17 May, 2005

2 commits

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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