From: Joerg Roedel <joro@8bytes.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Robert Hancock" <hancockrwd@gmail.com>,
"Justin Piszcz" <jpiszcz@lucidpixels.com>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
support@supermicro.com, linux-kernel@vger.kernel.org,
"Dan Williams" <djbw@fb.com>, "Jeff Garzik" <jgarzik@pobox.com>,
linux-ide@vger.kernel.org,
"David Woodhouse" <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org
Subject: Re: Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question
Date: Sun, 2 Dec 2012 14:26:49 +0100 [thread overview]
Message-ID: <20121202132649.GM30633@8bytes.org> (raw)
In-Reply-To: <CAErSpo6zvcN3aS_5ZNFD04yGNm_ehrNY_VUjO=172PSMKZYe+A@mail.gmail.com>
On Thu, Nov 29, 2012 at 08:38:53PM -0700, Bjorn Helgaas wrote:
> That's essentially the patch at
> https://bugzilla.redhat.com/show_bug.cgi?id=757166#c16, which in my
> opinion is too ugly to consider. But fortunately, I'm not the
> maintainer for any IOMMU drivers.
There is a quirk infrastructure for those kinds of broken devices in
drivers/pci/quirks.c. Have a look into the function
pci_get_dma_source(). This function is used by the IOMMU drivers to
create the correct mappings.
Joerg
next prev parent reply other threads:[~2012-12-02 13:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 19:40 Supermicro X9SRL-F - channel enumeration error & ACPI/firmware bug question Justin Piszcz
2012-11-26 21:42 ` Bruno Prémont
2012-11-27 0:50 ` Justin Piszcz
2012-11-27 0:56 ` Bjorn Helgaas
2012-11-27 1:00 ` Bjorn Helgaas
2012-11-27 1:00 ` Justin Piszcz
2012-11-27 1:11 ` Bjorn Helgaas
2012-11-27 13:33 ` Justin Piszcz
2012-11-27 13:49 ` Justin Piszcz
2012-11-27 13:56 ` Justin Piszcz
2012-11-27 14:35 ` Justin Piszcz
2012-11-29 0:08 ` Bjorn Helgaas
2012-11-29 0:49 ` Justin Piszcz
2012-11-28 23:54 ` Bjorn Helgaas
2012-11-29 0:48 ` Justin Piszcz
2012-11-29 0:34 ` Robert Hancock
2012-11-29 0:49 ` Justin Piszcz
2012-11-29 0:55 ` Robert Hancock
2012-11-29 8:55 ` Justin Piszcz
2012-11-29 18:16 ` Bjorn Helgaas
2012-11-30 2:39 ` Robert Hancock
2012-11-30 3:38 ` Bjorn Helgaas
2012-12-02 13:26 ` Joerg Roedel [this message]
2012-11-27 1:11 ` Dan Williams
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=20121202132649.GM30633@8bytes.org \
--to=joro@8bytes.org \
--cc=bhelgaas@google.com \
--cc=bonbons@linux-vserver.org \
--cc=djbw@fb.com \
--cc=dwmw2@infradead.org \
--cc=hancockrwd@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support@supermicro.com \
/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