From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: dmaengine@vger.kernel.org
Cc: Vinod Koul <vinod.koul@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: IOAT 4.0 driver not supported on Intel 5000 chipset
Date: Wed, 25 Jan 2017 11:16:26 +0530 [thread overview]
Message-ID: <5e7585e2-bba9-95f1-612a-873fd4a7cfb0@linux.vnet.ibm.com> (raw)
Hello Vinod/Dave,
I have an old X86 system with 'Intel(R) Xeon(R) CPU X5450' which has
'5000 Series Chipset'. The latest mainline IOAT driver does not work
on it. Dont see /sys/class/dma getting filled up with channel details
even if I manually load both dca.ko followed by ioatdma.ko drivers
after the system boots. As it was working on a old distro kernel like
3.10, did a git bisect to figure out that the support was removed for
older IOAT HW around August 2015 with the following commits.
commit 85596a19478da5125f3471a0c474b3f05a78e390
Author: Dave Jiang <dave.jiang@intel.com>
Date: Tue Aug 11 08:48:10 2015 -0700
dmaengine: ioatdma: remove ioat1 specific code
Cleaning up of ioat1 specific code as it is no longer supported
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Acked-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
d73f277b329f46c13527c1090808421828671596 is the first bad commit
commit d73f277b329f46c13527c1090808421828671596
Author: Dave Jiang <dave.jiang@intel.com>
Date: Tue Aug 11 08:48:04 2015 -0700
dmaengine: ioatdma: deprecating and removal of old ioatdma devices
Removal of any devices that are ioatdma pre-3.0. This is the first step
in attempting to clean up the ioatdma driver and remove hw no longer
supported.
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Acked-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
I intend to use the HW with mainline kernel. Is there any work around
which can make it happen ?
Regards
Anshuman
next reply other threads:[~2017-01-25 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 5:46 Anshuman Khandual [this message]
2017-01-25 16:41 ` Dave Jiang
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=5e7585e2-bba9-95f1-612a-873fd4a7cfb0@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®