1. 31 Aug, 2004 10 commits
  2. 30 Aug, 2004 3 commits
  3. 31 Aug, 2004 3 commits
  4. 30 Aug, 2004 9 commits
  5. 29 Aug, 2004 6 commits
  6. 28 Aug, 2004 9 commits
    • Andrew Chew's avatar
      [PATCH] sata_nv: fix CK804 support · 78864390
      Andrew Chew authored
      This patch fixes a problem introduced when CK804 support was added.  mmio_base can only be set in the CK804 case,
      else libata will attempt to iounmap mmio_base, which isn't iomapped for the non-CK804 case.  Still need the bar 5
      address, so steal from host_set->ports[0]->ioaddr.scr_addr.  Jeff, let me know if this is a bad thing to do.
      78864390
    • Armin Schindler's avatar
      [PATCH] ISDN Eicon driver: maint/trace fix and update · 9a276d67
      Armin Schindler authored
      Fix of the debug/trace driver and removal of irq locks.
      
       - Only spinlocks[bh] are used now.
       - Removed obsolete direct debug /proc interface.
       - Update of internal trace features and its API.
       - Use common definition of MAX_DESCRIPTORS.
      9a276d67
    • Linus Torvalds's avatar
      Merge bk://gkernel.bkbits.net/net-drivers-2.6 · 4a435afe
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      4a435afe
    • Matt Porter's avatar
      [PATCH] ibm_emac driver updates · 9a23b6f0
      Matt Porter authored
      Optimizes transmit windows for improved performance and to prevent
      TX underruns. Fixes driver registration error handling. Fixes ZMII
      and RGMII thinkos. Fixes for MDIO handling issues from Ralph
      Siemsen. Please apply.
      Signed-off-by: default avatarMatt Porter <mporter@kernel.crashing.org>
      9a23b6f0
    • Jeremy Higdon's avatar
      [PATCH] Fix DMA boundary overflow bug · 5b5e59f8
      Jeremy Higdon authored
      We seem to have found an overflow problem in libata-core.c.
      We were trying to DMA to the address range 0xffff8000-0xffffbfff.
      
      In the original version of the code, given that address and
      count (0xffff8000 and 0x4000), the variable "boundary" would be
      set to 0, causing len to be set to 0x8000 (which is greater than
      sg_len).  Then at the bottom of the loop, sg_len would be set
      to 0xffffc000 (0x4000 - 0x8000), which would then cause the
      loop never to terminate (until much of memory was scribbled
      over or the kernel died).
      
      The code below should be functionally identical, but not be
      subject to the same overflow problem (boundary needs to be a
      u33).
      
      Signed-off-by: jeremy@sgi.com
      
      ===== drivers/scsi/libata-core.c 1.94 vs edited =====
      5b5e59f8
    • Linus Torvalds's avatar
      Merge http://jfs.bkbits.net/linux-2.5 · 0196b17d
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      0196b17d
    • Linus Torvalds's avatar
      Merge bk://linux-voyager.bkbits.net/dma-declare-coherent-memory-2.6 · c8339002
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.6/linux
      c8339002
    • Thayne Harbaugh's avatar
    • Andrew Morton's avatar
      [PATCH] Problem with SiS900 - Unknown PHY · 49fa5c32
      Andrew Morton authored
      From: Laurent <laurent@gobio2.net>
      
      Some time ago, I sent on this list a mail about my strange problem with my
      SiS900 network card (Subject was Sluggish performances with FreeBSD)
      
      To sum up, when my card is in 100Mb mode, I have poor throughput but in
      10Mb, all seems normal.
      
      After some tests, it seems these results was due to a misdetection of the
      PHY device.  mii-tool reports :
      
       product info: vendor 08:00:17, model 3 rev 0
      
      and after some search on the web, I found it's a NS DP83847 which is very
      similar.
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      49fa5c32