1. 05 1月, 2009 1 次提交
  2. 30 11月, 2008 1 次提交
  3. 10 7月, 2007 2 次提交
    • S
      ieee1394: remove old isochronous ABI · 53c96b41
      Stefan Richter 提交于
      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: NStefan Richter <stefanr@s5r6.in-berlin.de>
      53c96b41
    • K
      ieee1394: convert ieee1394 from "struct class_device" to "struct device" · dd7f2928
      Kay Sievers 提交于
      Here is a straightforward conversion to "struct device". The "struct
      class_device" will be removed from the kernel.
      
      It seems to work fine for me with and without CONFIG_SYSFS_DEPRECATED
      set.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      dd7f2928
  4. 30 4月, 2007 2 次提交
  5. 09 2月, 2007 2 次提交
  6. 22 11月, 2006 1 次提交
  7. 18 9月, 2006 1 次提交
    • S
      ieee1394: shrink tlabel pools, remove tpool semaphores · 9951903e
      Stefan Richter 提交于
      This patch reduces the size of struct hpsb_host and also removes
      semaphores from ieee1394_transactions.c.  On i386, struct hpsb_host
      shrinks from 10656 bytes to 6688 bytes.  This is accomplished by
       - using a single wait_queue for hpsb_get_tlabel instead of many
         instances of semaphores,
       - using a single lock to serialize access to all tlabel pools (the
         protected code regions are small, i.e. lock contention very low),
       - omitting the sysfs attribute tlabels_allocations.
      
      Drawback:  In the rare case that a process needs to sleep because all
      transaction labels for the node are temporarily exhausted, it is also
      woken up if a tlabel for a different node became free, checks for an
      available tlabel, and is put to sleep again.  The check is not costly
      and the situation occurs extremely rarely.  (Tlabels are typically
      only exhausted if there was no context switch to the khpsbpkt thread
      which recycles tlables.)  Therefore the benefit of reduced tpool size
      outweighs this drawback.
      
      The sysfs attributes tlabels_free and tlabels_mask are not compiled
      anymore unless CONFIG_IEEE1394_VERBOSEDEBUG is set.
      
      The by far biggest member of struct hpsb_host, the struct csr_control
      csr (5272 bytes on i386), is now placed at the end of struct hpsb_host.
      
      Note, hpsb_get_tlabel calls the macro wait_event_interruptible with a
      condition argument which has a side effect (allocation of a tlabel and
      manipulation of the packet).  This side effect happens only if the
      condition is true.  The patch relies on wait_event_interruptible not
      evaluating the condition again after it became true.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      9951903e
  8. 04 7月, 2006 3 次提交
  9. 13 6月, 2006 3 次提交
    • B
      ieee1394: extend lowlevel API for address range properties · 8aef63ff
      Ben Collins 提交于
      Host adapter hardware imposes certain restrictions and features on
      address ranges.  Instead of hard-wire such ranges into the ieee1394
      core or even into protocol drivers, let lowlevel drivers specify
      these ranges via struct hpsb_host.
      
      Patch "ohci1394: set address range properties" must be applied too,
      else hpsb_allocate_and_register_addrspace() won't work properly.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      Signed-off-by: NBen Collins <bcollins@ubuntu.com>
      8aef63ff
    • B
      ieee1394: save RAM by using a single tlabel for broadcast transactions · eaf88450
      Ben Collins 提交于
      Since broadcast transactions are already complete when the request has
      been sent, the same transaction label can be reused all over again, see
      IEEE 1394 7.3.2.5 and 6.2.4.3.  Therefore we can reduce the footprint
      of struct hpsb_host by the size of one struct hpsb_tlabel_pool.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      Signed-off-by: NBen Collins <bcollins@ubuntu.com>
      eaf88450
    • B
      ieee1394: support for slow links or slow 1394b phy ports · 647dcb5f
      Ben Collins 提交于
      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: NStefan 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: NBen Collins <bcollins@ubuntu.com>
      647dcb5f
  10. 13 12月, 2005 1 次提交
  11. 02 12月, 2005 2 次提交
  12. 01 10月, 2005 1 次提交
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4