[PATCH] ide-taskfile.c fixups/cleanups part #2 [6/9]

From: Bartlomiej Zolnierkiewicz (B.Zolnierkiewicz_at_elka.pw.edu.pl)
Date: 06/30/04

  • Next message: Bartlomiej Zolnierkiewicz: "[PATCH] ide-taskfile.c fixups/cleanups part #2 [0/9]"
    To: linux-ide@vger.kernel.org
    Date:	Wed, 30 Jun 2004 17:25:44 +0200
    
    

    [PATCH] ide: pre_task_mulout_intr() cleanup (CONFIG_IDE_TASKFILE_IO=n)

    drive_is_ready() reads STATUS register if CONFIG_IDEPCI_SHARE_IRQ is not
    defined and ALTSTATUS register if it is defined. Therefore drive_is_ready()
    in pre_task_mulout_intr() only makes sense if we can't trust STATUS register
    (because we call ide_wait_stat() which reads STATUS register earlier).

    Remove this "workaround" for now as it is not present in ide-disk.c
    and whole multi PIO-out code (CONFIG_IDE_TASKFILE_IO=n) was buggy before.

    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>

     linux-2.6.7-bk11-bzolnier/drivers/ide/ide-taskfile.c | 7 -------
     1 files changed, 7 deletions(-)

    diff -puN drivers/ide/ide-taskfile.c~ide_pre_task_mulout_intr drivers/ide/ide-taskfile.c
    --- linux-2.6.7-bk11/drivers/ide/ide-taskfile.c~ide_pre_task_mulout_intr 2004-06-28 21:27:32.442035640 +0200
    +++ linux-2.6.7-bk11-bzolnier/drivers/ide/ide-taskfile.c 2004-06-28 21:27:32.448034728 +0200
    @@ -433,13 +433,6 @@ ide_startstop_t pre_task_mulout_intr (id
                             drive->addressing ? "MULTWRITE_EXT" : "MULTWRITE");
                     return startstop;
             }
    - if (!(drive_is_ready(drive))) {
    - int i;
    - for (i=0; i<100; i++) {
    - if (drive_is_ready(drive))
    - break;
    - }
    - }
     
             ide_set_handler(drive, &task_mulout_intr, WAIT_WORSTCASE, NULL);
             task_buffer_multi_sectors(drive, rq, IDE_PIO_OUT);

    _

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Bartlomiej Zolnierkiewicz: "[PATCH] ide-taskfile.c fixups/cleanups part #2 [0/9]"

    Relevant Pages

    • Re: ptrace problem on ia64 with kernel 2.4.26
      ... > ddd, and other debugging tools, which depend on ptrace system call, don't ... > modification to peek info about register r4. ... > We use the following configuration: ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 2.6] Altix - ioc3 serial support
      ... ports, and for console ports, it is assumed that the console code has ... >> tty_buffer_request_room is a hint to help the kernel manage buffers>> better. ... register for this. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: FEATURE REQUEST: Specific Processor Optimizations on x86 Architecture
      ... The current code also does not touch any register. ... The wmb() change is not needed, unless you have an oostore CPU ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] S3 suspend/resume with noexec
      ... >>Please analyse surrounding code a bit more. ... > and restore every register that is being touched here. ... I'd like minimal push/pops. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: modprobe + request_module() deadlock
      ... or mxb) so that these are loaded via hotplug. ... They then register to the ... saa7146 core as an "extension" module, and the core then does the probing. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)