From: David Howells <dhowells@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata-sff: Allow for wacky systems
Date: Tue, 24 Oct 2006 10:44:36 +0100 [thread overview]
Message-ID: <22963.1161683076@redhat.com> (raw)
In-Reply-To: <1161012290.24237.68.camel@localhost.localdomain>
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> There are some Linux supported platforms that simply cannot hit the low
> I/O addresses used by ATA legacy mode PCI mappings. These platforms have
> a window for PCI space that is fixed by the board logic and doesn't
> include the neccessary locations.
>
> Provide a config option so that such platforms faced with a controller
> that they cannot support simply error it and punt
Yep, that works:
warthog>grep ATA_LEGACY .config
CONFIG_NO_ATA_LEGACY=y
...
pata_hpt37x: BIOS has not set timing clocks.
hpt37x: HPT371: Bus clock 33MHz.
ata1: PATA max UDMA/133 cmd 0xE4000820 ctl 0xE400082A bmdma 0xE4000C00 irq 20
ata2: PATA max UDMA/133 cmd 0xE4000830 ctl 0xE400082E bmdma 0xE4000C08 irq 20
scsi0 : pata_hpt37x
ATA: abnormal status 0x7D on port 0xE4000827
scsi1 : pata_hpt37x
ATA: abnormal status 0x8 on port 0xE4000837
pata_it821x: controller in smart mode.
ata3: PATA max MWDMA2 cmd 0xE4000838 ctl 0xE4000842 bmdma 0xE4000850 irq 22
ata4: PATA max MWDMA2 cmd 0xE4000848 ctl 0xE4000846 bmdma 0xE4000858 irq 22
scsi2 : pata_it821x
scsi3 : pata_it821x
...
David
prev parent reply other threads:[~2006-10-24 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 15:24 [PATCH] libata-sff: Allow for wacky systems Alan Cox
2006-10-16 15:17 ` Valdis.Kletnieks
2006-10-16 16:24 ` Alan Cox
2006-10-21 19:19 ` Jeff Garzik
2006-10-24 9:44 ` David Howells [this message]
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=22963.1161683076@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.