From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Patrick Mahan <mahan-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Need to support mapping in bar1
Date: Thu, 8 Aug 2013 16:53:44 -0700 [thread overview]
Message-ID: <20130808165344.18a543b9@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <F59A35D6-FCF9-47F7-AE9F-F3A731C68C10-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
On Thu, 8 Aug 2013 16:45:42 -0700
Patrick Mahan <mahan-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org> wrote:
> Before I do this, I wanted to check with the list.
>
> The UIO support code in DPDK only maps in bar 0 for PCI devices, and it does provide support for mapping any other bar that the device provides.
>
> Has anyone fixed this yet? Or maybe has a patch?
>
> DPDK version: 1.3.1r2
>
> Thanks,
>
> Patrick
Yes, I sent patches to fix this, look on list. If not will resend.
next prev parent reply other threads:[~2013-08-08 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 23:45 Need to support mapping in bar1 Patrick Mahan
[not found] ` <F59A35D6-FCF9-47F7-AE9F-F3A731C68C10-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-08-08 23:53 ` Stephen Hemminger [this message]
[not found] ` <20130808165344.18a543b9-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-08-09 0:04 ` Patrick Mahan
[not found] ` <7866DDBC-AD11-4BF6-83E7-5FB61DD8281D-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-08-09 0:50 ` Stephen Hemminger
[not found] ` <20130808175032.7b343765-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-08-09 19:46 ` Patrick Mahan
[not found] ` <52054701.2050602-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-08-09 21:06 ` Stephen Hemminger
2013-08-09 22:17 ` Stephen Hemminger
[not found] ` <20130809151716.0516cf0a-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-08-13 21:50 ` Thomas Monjalon
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=20130808165344.18a543b9@nehalam.linuxnetplumber.net \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=mahan-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.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;
as well as URLs for NNTP newsgroup(s).