Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-ide@vger.kernel.org
Subject: Problem with some aec62xx
Date: Sun, 07 Dec 2003 13:11:02 +1100	[thread overview]
Message-ID: <1070763062.12497.30.camel@gaston> (raw)

Hi !

One of you (Bart, Andre ?) has specs to these controllers ? Some
users are reporting me various failures with these on ppc until
they got a bit of code back from earlier 2.4 drivers into the
new (2.4.21+ or 2.6.0) one:

			/* Clear reset and test bits.  */
			pci_read_config_byte(hwif->pci_dev, 0x49, &reg49h);
			pci_write_config_byte(hwif->pci_dev, 0x49, reg49h & ~0x30);
			/* Enable chip interrupt output.  */
			pci_read_config_byte(hwif->pci_dev, 0x4a, &reg4ah);
			pci_write_config_byte(hwif->pci_dev, 0x4a, reg4ah & ~0x01);

Theres also this additional bit, that doesn't seem to be required,
but was there in 2.4.20 (at least in my tree, it's possible that the
version of the driver I had was slightly different as I remember
taking patches on this driver from some users a long time ago).

#define CONFIG_AEC6280_BURST
#ifdef CONFIG_AEC6280_BURST
			/* Must be greater than 0x80 for burst mode.  */
			pci_write_config_byte(hwif->pci_dev, PCI_LATENCY_TIMER, 0x90);
			/* Enable burst mode.  */
			pci_read_config_byte(hwif->pci_dev, 0x4a, &reg4ah);
			pci_write_config_byte(hwif->pci_dev, 0x4a, reg4ah | 0x80);
#endif



             reply	other threads:[~2003-12-07  2:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07  2:11 Benjamin Herrenschmidt [this message]
2003-12-07  2:19 ` Problem with some aec62xx Benjamin Herrenschmidt

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=1070763062.12497.30.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-ide@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