An error occurred fetching the project authors.
  1. 14 Mar, 2004 1 commit
  2. 12 Mar, 2004 1 commit
    • Andrew Morton's avatar
      [PATCH] i386 very early memory detection cleanup patch · 973adfc0
      Andrew Morton authored
      From: "H. Peter Anvin" <hpa@zytor.com>
      
      This patch cleans up the very early memory setup on the i386 platform.  In
      particular, it removes the hard-coded 8 MB limit completely by dynamically
      creating the early-boot pagetables rather than having them hard coded.
      
      While I was at it, I changed head.S so that it always sets up a local GDT;
      this means among other things that SMP and VISWS are no longer special
      cases, and is conceptually cleaner to boot.  The VISWS people have
      confirmed it works on VISWS.
      
      It also uses a separate entrypoint for non-boot processors since this is
      completely kernel-internal anyway.  This eliminates the need to set %bx on
      boot.  (If you think this is a bad idea I can eliminate this change; it
      just seemed cleaner to me to do it this way.)
      
      Additionally, zero bss with rep;stosl rather that rep;stosb.
      973adfc0
  3. 01 Mar, 2004 1 commit
  4. 05 Feb, 2004 1 commit
  5. 31 Jan, 2004 1 commit
  6. 23 Jan, 2004 1 commit
  7. 01 Sep, 2003 1 commit
  8. 20 Aug, 2003 1 commit
    • Jeff Garzik's avatar
      [PATCH] remove mount_root_failed_msg() · df1c4865
      Jeff Garzik authored
      This one snuck in...
      
       - debugging message for ACPI
      
       - Intel guys removed it from their 2.4 tree (at my request)
      
       - it's point-in-time specific (message becomes nearly useless after
         ACPI bug fixes)
      
       - b/c of the point-in-time issue, it's IMO much more appropriate for a
         vendor kernel (where the message, I agree, may be helpful)
      
       - can potentially mislead users to the correct cause of root mount failure
      
       - overall, I disagree with adding messages like this.  The number one
         bug report, by far, for networking drivers is ACPI-related (no
         interrupts delivered).  You don't see me adding "boot with acpi=off"
         messages to the net subsystem.
      df1c4865
  9. 18 Aug, 2003 1 commit
  10. 02 Aug, 2003 2 commits
  11. 31 Jul, 2003 1 commit
    • Alan Cox's avatar
      [PATCH] ikconfig · e78eae3d
      Alan Cox authored
      (Randy Dunlap)
      
      Build the kernel config data into the kernel - either unloaded or accessible
      via /proc
      e78eae3d
  12. 16 Jan, 2003 1 commit
  13. 30 Dec, 2002 1 commit
  14. 28 Dec, 2002 1 commit
  15. 15 Oct, 2002 1 commit
  16. 09 Oct, 2002 1 commit
    • Matt Domsch's avatar
      EDD: x86 BIOS Enhanced Disk Drive support · 7df2bda6
      Matt Domsch authored
      The major changes implemented in this patch:
      arch/i386/boot/setup.S - int13 real mode calls store results in empty_zero_page
      arch/i386/kernel/setup.c - copy results from empty_zero_page to local storage
      arch/i386/kernel/edd.c - module exports results via driverfs
      
      x86 systems suffer from a disconnect between what BIOS believes is the
      boot disk, and what Linux thinks BIOS thinks is the boot disk.  This
      manifests itself in multi-disk systems - it's quite possible to
      install a distribution, only to fail on reboot - the disk installed to
      is not the disk BIOS is booting from.  Dell restricts our possible
      standard factory installed Linux offerings to "disks on no more than
      one controller" to avoid this problem, but mechanisms now exist to
      solve it and allow such configurations.
      
      BIOS Enhanced Disk Device Services (EDD) 3.0 provides the ability for
      disk adapter BIOSs to tell the OS what it believes is the boot disk.
      While this isn't widely implemented in BIOSs yet, it's time that Linux
      received support to be ready as BIOSs with this feature do become
      available.  At a minimum, LSI MegaRAID cards support this today.
      
      EDD works by providing the bus (PCI, PCI-X, ISA, InfiniBand, PCI
      Express, or HyperTransport) location (e.g. PCI 02:01.0) and interface
      (ATAPI, ATA, SCSI, USB, 1394, FibreChannel, I2O, RAID, SATA) location
      (e.g. SCSI ID 5 LUN 0) information for each BIOS int13 device.
      
      The patch below creates CONFIG_EDD, that when defined, makes the
      BIOS int13 calls to retrieve and store this information.  The data is
      copied to a safe place in setup.c, and exported via driverfs.
      
      Here's a sample driverfs tree with two BIOS int13 devices - dev 80 has
      incorrect PCI bus information, thus no symlinks are made, but as much
      info as possible is presented.  Dev 81 has correct PCI and SCSI
      information, thus symlinks are made to the actual disc device.
      
      /driverfs
      |-- bios
      |   |-- int13_dev80
      |   |   |-- extensions
      |   |   |-- host_bus
      |   |   |-- info_flags
      |   |   |-- interface
      |   |   |-- raw_data
      |   |   |-- sectors
      |   |   `-- version
      |   `-- int13_dev81
      |       |-- extensions
      |       |-- host_bus
      |       |-- info_flags
      |       |-- interface
      |       |-- pci_dev -> ../../root/pci2/02:0c.0/03:00.0/04:00.0
      |       |-- raw_data
      |       |-- disc -> ../../root/pci2/02:0c.0/03:00.0/04:00.0/scsi4/4:0:0:0
      |       |-- sectors
      |       `-- version
      |-- bus
      |   |-- scsi
      |   |   |-- devices
      |   |   |   |-- 4:0:0:0 -> ../../../root/pci2/02:0c.0/03:00.0/04:00.0/scsi4/4:0:0:0
      |   |   `-- drivers
      |   |       `-- sd
      `-- root
          |-- pci2
          |   |-- 02:0c.0
          |   |   |-- 03:00.0
          |   |   |   |-- 04:00.0
          |   |   |   |   |-- irq
          |   |   |   |   |-- name
          |   |   |   |   |-- power
          |   |   |   |   |-- resource
          |   |   |   |   `-- scsi4
          |   |   |   |       |-- 4:0:0:0
          |   |   |   |       |   |-- 4:0:0:0::p1
          |   |   |   |       |   |   |-- kdev
          |   |   |   |       |   |   |-- name
          |   |   |   |       |   |   |-- power
          |   |   |   |       |   |   `-- type
          |   |   |   |       |   |-- 4:0:0:0:disc
          |   |   |   |       |   |   |-- kdev
          |   |   |   |       |   |   |-- name
          |   |   |   |       |   |   |-- power
          |   |   |   |       |   |   `-- type
          |   |   |   |       |   |-- name
          |   |   |   |       |   |-- power
          |   |   |   |       |   `-- type
      
      
      (Yes, the 'bios' top-level directory isn't the right place,
       and Patrick has promised to make something there in the future,
       at which point this can be moved.)
      
      The 'raw_data' file contains the full set of information returned by BIOS
      with extra error reporting.  This exists for vendor BIOS debugging purposes.
      
      The 'host-bus' file contains the PCI (or ISA, HyperTransport, ...)
      identifying information, as BIOS knows it.
      
      The 'interface' file contains the SCSI (or IDE, USB, ...) identifying
      information, as BIOS knows it.
      
      The 'extensions' file lists the BIOS EDD extensions per spec.
      The 'info_flags' file lists the BIOS EDD device information flags per spec.
      The 'sectors' file reports the number of sectors BIOS believes this
      device has.
      The 'version' file lists the EDD version.  To have device path
      information, this must be 0x30 or above.  Earlier EDD versions exist
      without the device path - as much information as is available is presented.
      
      At most 6 BIOS devices are reported, as that fills the space that's
      left in the empty_zero_page.  In general you only care about device
      80h, though for software RAID1 knowing what 81h is might be useful also.
      
      
      
      Known issues:
      - module unload leaves a directory around.  Seems related to
        creating symlinks in that directory.  Seen on kernel 2.5.41.
      - refcounting of struct device objects could be improved.
      
      TODO:
      - Add IDE and USB disk device support
      - when driverfs model of discs and partitions changes,
        update symlink accordingly.
      - Get symlink creator helper functions exported from
        drivers/base instead of duplicating them here.
      - move edd.[ch] to better locations if/when one is decided
      
      I'd also like to acknowledge the help and comments received from Greg
      KH and Patrick Mochel.  This isn't something driverfs was originally
      conceived to handle, their assistance has been invaluable.
      
      Please pull from:
      
      BK:
          http://mdomsch.bkbits.net/linux-2.5-edd-tolinus
      
      Patch (against 2.5.41+BK-current):
          http://domsch.com/linux/edd30/edd-driverfs-6.patch
          http://domsch.com/linux/edd30/edd-driverfs-6.patch.sign
      
      Thanks,
      Matt
      
      -- 
      Matt Domsch
      Sr. Software Engineer, Lead Engineer, Architect
      Dell Linux Solutions www.dell.com/linux
      Linux on Dell mailing lists @ http://lists.us.dell.com
      7df2bda6
  17. 08 Oct, 2002 1 commit
    • Dave Jones's avatar
      [PATCH] CONFIG_NR_CPUS · 9153f34e
      Dave Jones authored
      By Robert Love, this patch sets the maximum number
      of CPUs a kernel can support (From 2-32 on IA32)
      The reasoning behind this is a space saving of
      8KB per CPU.
      9153f34e
  18. 26 Sep, 2002 1 commit
  19. 28 Aug, 2002 1 commit
  20. 26 Aug, 2002 1 commit
  21. 13 Aug, 2002 1 commit
  22. 22 May, 2002 1 commit
    • Martin Dalecki's avatar
      [PATCH] 2.5.17 IDE 67 · 14cfb6a6
      Martin Dalecki authored
       - Nuke COMMERIAL and similar spurious configuration options...
         The fact that every single default configuration option contained
         those bits makes this trivial patch appear rather big.
      14cfb6a6
  23. 21 May, 2002 1 commit
    • Pavel Machek's avatar
      [PATCH] suspend-to-{RAM,disk} · 542f96a5
      Pavel Machek authored
      Here's suspend-to-{RAM,disk} combined patch for
      2.5.17. Suspend-to-disk is pretty stable and was tested in
      2.4-ac. Suspend-to-RAM is little more experimental, but works for me,
      and is certainly better than disk-eating version currently in kernel.
      
      Major parts are: process stopper, S3 specific code, S4 specific
      code.
      542f96a5
  24. 17 May, 2002 1 commit
    • Martin Dalecki's avatar
      [PATCH] 2.5.15 IDE 63 · d7e09f7e
      Martin Dalecki authored
      - Propagate the queue handling changes to pmac as well.
      
      - Move set_transfer to ide-taskfile.c this is the only place where it's used
         and it can be made static there. Same applies to ide_ata66_check().
      
      - Move ide_auto_reduce_xfer to ide.c.
      
      - Make ide_cmd() local to the only place where it's used. Rename it to
         drive_cmd(). Don't pass drive_cmd_intr() as parameter.
      
      - Remove ide_next command completion type. Nobody is using it.
      
      - Move ide_do_drive_cmd to ide-taskfile. It's used there and in sub-drivers.
         Not in ide.c. The usage inside the device type drivers is entirely bogus
         inconsistent and so on...
      
      - Kill bogus IRQ masking code. The kernel is supposed to handle this properly.
         We should not try to work against possible bugs in the overall irq handling
         code. Wow this is increasing the systems overall responsibility by a
         significant margin.
      
      - Remove disfunctional pdcadma code. It is only misleading to the user.
      d7e09f7e
  25. 06 May, 2002 1 commit
    • Martin Dalecki's avatar
      [PATCH] 2.5.14 IDE 55 · fb0bbfda
      Martin Dalecki authored
       - Update HPT374 driver carried over from 2.4.xx series by Andrew Morton.
         Resync it with the recent host chip driver changes, or better the
         introduction of an API at all.
      
       - Consolidate the handling of device ID byte order in one place.
         This was spotted and patched by Bartomiej onierkiewicz.
      
       - Eliminate CONFIG_BLK_DEV_IDEPCI - it's duplicating the functionality of the
         already present and fine CONFIG_PCI flag and if we are a PCI host, we are
         indeed very likely to need host chip support anyway.
      
       - Remove some redundant info about the model and channel number from
         /proc/ide. Remove the binary entries not helpful to the user, and not used
         by any program and redundant to corresponding ioctls.
      
       - Properly return udma_read and udma_write values in taskfile.
      
       - Only initialize XXX_udma to the default handlers if it has not been
         initialized by the host chip initialization.
      
      I have enabled spin lock debugging and can see that on device
      flush the spin locks get wrong counts... no problems elsewher ethus
      far. I will re check them next time around.
      fb0bbfda
  26. 30 Apr, 2002 2 commits
    • Linus Torvalds's avatar
      update x86 defconfig · 8c93aa4e
      Linus Torvalds authored
      8c93aa4e
    • Martin Dalecki's avatar
      [PATCH] 2.5.11 IDE 46 · 4a58bd1a
      Martin Dalecki authored
      - Remove the specific CONFIG_IDEDMA_PCI_WIP in favor of using the generic
         CONFIG_EXPERIMENTAL tag. (Pointed out by Vojtech Pavlik).
      
      - Change the signature of the IRQ handler to take the request directly as a
         parameter. This doesn't blow the code up but makes it much more obvious and
         finally it's reducing the number of side effects of the hwgroup->rq field.
      
      - A second sharp look after the above change allowed us to remove the wrq field
         from the hwgroup struct. It's just not used at all.
      
      - Change the signature of the end_request member of struct ata_operations to
         take the request as a second argument. Similar for __ide_end_request()
         and ide_end_request().
      
      - Remove BUG_ON() items just before ide_set_handler(). The check in
         ide_set_handler is clever enough now.
      
      - Remove the rq subfield from ide-scsi packet structure. We have now the
         request context always in place. Same for floppy.
      
      - Let the timer expiry function take the request as a direct argument.
      
      Yes I know those changes are extensive. But they are a necessary step
      in between for the following purposes:
      
      - Consolidate the whole ATA/ATAPI stuff on passing a single unified request
         handling object. Because after eliminating those side effects it's far easier
         to see what's passed where.
      
      - Minimizing the amount of side effects in the overall code. That's a good
         thing anyway and it *doesn't* cost us neither performance nor space, since
         the stack depths are small anyway here.
      
      - Minimizing the usage of hwgroup - which should go away if possible.
      4a58bd1a
  27. 28 Apr, 2002 1 commit
    • Dave Jones's avatar
      [PATCH] bluesmoke update. · 2617765b
      Dave Jones authored
      o   P4 thermal throttling is now compile time option
      o   ifdefs cleaned up due to above
      o   Only poke the LVT if thermal throttling is enabled.
      o   Remove bogus cache flushing as per previous discussion.
      o   Replace hard coded timer values with MCE_RATE
      o   Change default polling frequency from 5 to 15 seconds
      o   SMP fixes. (Don't readd timer)
      o   Compile time warning fixes.
      o   Add config helptext
      2617765b
  28. 22 Apr, 2002 1 commit
  29. 12 Apr, 2002 1 commit
  30. 09 Apr, 2002 1 commit
  31. 04 Apr, 2002 1 commit
  32. 03 Apr, 2002 1 commit
  33. 02 Apr, 2002 1 commit
  34. 20 Mar, 2002 1 commit
  35. 18 Mar, 2002 1 commit
    • Martin Dalecki's avatar
      [PATCH] 2.5.7-pre2 IDE 22a · 198231a8
      Martin Dalecki authored
      - Apply more patches from Vojtech Pavlik for the handling of host chip setup.
         Hopefully they are settled now.
      
      - Kill unused CONFIG_BLK_DEV_MODES
      
      - Push register addressing down in to task_vlb_sync.
      
      - Make the taskfile parsing stuff actually readable. This is compressing the
         code by an incredible amount. We use just one function doing the whole
         scanning right now. This should make sure that the IRQ handler used by a
         particular command is always right.  I didn't introduce typos hopefully
         here.
      
      - Don't call ide_handler_parser as argument for do_taskfile() any longer. We
         have killed this function by coalescing it's functionality with
         ide_cmd_type_parser() anyway.
      
      - Kill unused SLC90E66 code, which Vojtech apparently missed in his patch.
      
      - sync up with 2.5.7-pre2
      
      Once again the actual patch is rather big mostly due to the removal of
      some default configuration variables which are not used anylonger. So time for
      the next patch stage.
      198231a8
  36. 15 Mar, 2002 1 commit
  37. 13 Mar, 2002 1 commit
    • Martin Dalecki's avatar
      [PATCH] IDE 21 · 10cea35a
      Martin Dalecki authored
      If I was to give this patch a name it would be:
      
      "Vojtech Pavlik unleashed from the chains".
      
      So credit where credit is due :-).
      
      Anyway here follows the change log:
      
      Mon Mar 11 23:48:28 CET 2002 ide-clean-21
      
      - Swallow rewritten amd74xx host chip setup code from Vojtech Pavlik.  We can
         revert it easly if it turns out to be a bad thing. However the code looks
         quite sane to me. In esp. it doesn't containg that many magic numbers.
      
      - Clean stale white spaces in ide-timing.h tirvial fix.
      
      - Make ide_release_dma return void. It's value is never used anyway.
      
      - Swallow more timing setup code cleanup by Vojtech Pavlik. Apply some
         cosmetics to it. Port opti621 to the new setup code.
      
      - Kill abuse of ide_do_reset() on error return paths for atapi floppy tape and
         cd-rom devices. Just stop them. This gives better changes that defect
         removable media will not cause suddenly broken timings on hard discs
         containing system data! Even then comments in ide_do_reset() admit, that
         resetting the whole channel can have adverse effects on the second interface
         on this channel. And I have too frequently observed linux struggling on
         defect cd-rom for a far too long time to wish it to continue.
      
         Oh did I forget to say that the corresponding "how can I break my system fast
         and reliable" ioctl is gone as well?
      
         Removing it recovered the fact that the CONFIG_BLK_DEV_IDEDMA_TIMEOUT is
         completely bogous. I have removed this option therefore as well, because it's
         playing the same wrack havoc on the devices if enabled. This cat has been in
         an unfinished and *unfunctional* state anyway.
      
      - Actually add physical suspend code to the power handling code.  Still the
         resume code isn't finished just jet. This is all subject to change at the
         point in time when we get to proper command queueing.
         I think however that Pavel will be interrested in tidding this bit up...
      
      - Resync with 2.5.7-pre1.
      10cea35a
  38. 12 Mar, 2002 1 commit