public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: drivers/ide/pci/pdc202xx_old.c
Date: Tue, 27 May 2003 00:57:07 +0200	[thread overview]
Message-ID: <3ED29BC3.104@gmx.net> (raw)

Hello IDE gurus,

is the following #if 0 in drivers/ide/pci/pdc202xx_old.c intentional?
What makes me worried about the code is that it looks like somebody
wanted to clean up the code for splitoff of pdc202xx_new.c and confused
the two files.
Either the code is really not needed and can be ripped out or it is
needed and was overlooked.

drivers/ide/pci/pdc202xx_old.c:719
        /*
         * software reset -  this is required because the bios
         * will set UDMA timing on if the hdd supports it. The
         * user may want to turn udma off. A bug in the pdc20262
         * is that it cannot handle a downgrade in timing from
         * UDMA to DMA. Disk accesses after issuing a set
         * feature command will result in errors. A software
         * reset leaves the timing registers intact,
         * but resets the drives.
         */
#if 0
        if ((dev->device == PCI_DEVICE_ID_PROMISE_20267) ||
            (dev->device == PCI_DEVICE_ID_PROMISE_20265) ||
            (dev->device == PCI_DEVICE_ID_PROMISE_20263) ||
            (dev->device == PCI_DEVICE_ID_PROMISE_20262)) {
                unsigned long high_16   = pci_resource_start(dev, 4);
                byte udma_speed_flag    = inb(high_16 + 0x001f);
                outb(udma_speed_flag | 0x10, high_16 + 0x001f);
                mdelay(100);
                outb(udma_speed_flag & ~0x10, high_16 + 0x001f);
                mdelay(2000);   /* 2 seconds ?! */
        }

#endif


Thoughts? Comments?

Carl-Daniel


                 reply	other threads:[~2003-05-26 22:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ED29BC3.104@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox