From: Alan <alan@lxorguk.ukuu.org.uk>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: linux-ide@vger.kernel.org,
fedora-ia64-list <fedora-ia64-list@redhat.com>
Subject: Re: The 5th bar of ide controller at legacy mode
Date: Mon, 12 Feb 2007 12:56:46 +0000 [thread overview]
Message-ID: <20070212125646.61263751@localhost.localdomain> (raw)
In-Reply-To: <1171244453.15989.389.camel@ymzhang>
O> 0x0000000000000000 0x00000000000003ff 0x0000000000000200
> 0x0000000000000000 0x0000000000000000 0x0000000000000000
>
> The 5th bar is incorrect. BIOS initiates ide controllers.
You appear to have a 5th BAR allocated at address 0 with a length of
0x400.
> failure, but ide-cd/piix is smarter to recall pci_enable_device_bars
> directly with parameter bars=(1<<4), so only 0~4th bar resources are checked.
the old IDE code deals only with SFF interfaces in simple modes, and hand
does all the handling for BAR 0-3 because of old PCI layer flaws and
weaknesses.
> So my question is: should ata/ata_piix also need to recall pci_enable_device_bars
> with parameter bars=(1<<4) if pci_enable_device fails like what ide-cd/piix does?
Your platform code or BIOS is buggy. PPC people had a similar problem.
Zero is not currently taken as "unallocated" by the PCI layer and, while
Linus suggested it could be, Dave Woodhouse and others pointed out there
are systems which legitimately use address 0 on the PCI in this way.
Sounds like you need to fix up after your firmware in your boot code,
perhaps with an arch specific pci header quirk.
Alan
next prev parent reply other threads:[~2007-02-12 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 1:40 Zhang, Yanmin
2007-02-12 12:22 ` [Fedora-ia64-list] " Prarit Bhargava
2007-02-12 12:56 ` Alan [this message]
2007-02-12 18:18 ` [Fedora-ia64-list] " Luck, Tony
2007-02-12 18:24 ` Prarit Bhargava
2007-02-12 19:24 ` Alan
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=20070212125646.61263751@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=fedora-ia64-list@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=yanmin_zhang@linux.intel.com \
--subject='Re: The 5th bar of ide controller at legacy mode' \
/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
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.