From: George Kashperko <george@znau.edu.ua>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Greg KH" <greg@kroah.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org, "Michael Büsch" <mb@bu3sch.de>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Arend van Spriel" <arend@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
"Russell King" <rmk@arm.linux.org.uk>,
"Arnd Bergmann" <arnd@arndb.de>,
"Andy Botting" <andy@andybotting.com>,
linuxdriverproject <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH V4] axi: add AXI bus driver
Date: Thu, 14 Apr 2011 00:24:10 +0300 [thread overview]
Message-ID: <1302729850.8479.7.camel@dev.znau.edu.ua> (raw)
In-Reply-To: <BANLkTinLn4Ug=gX4coHJbSzrkxdSMjgGeg@mail.gmail.com>
> 2011/4/13 George Kashperko <george@znau.edu.ua>:
> >> I had no idea what you were referring to. We do not dig into PCIe
> >> functions yet, so I believe for now we need this "if".
> > You are already deep inside. Your host code drives pci function.
>
> But I don't use multiple PCIe functions, do not focus on that at all.
>
Don't see anything in the host driver code preventing it to be bound to
functions other than 0. But anyways if you sure your host will be used
by several cores then why don't you spinlock window accesses ?
Have nice day,
George
next prev parent reply other threads:[~2011-04-13 21:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 18:52 [RFC][PATCH V4] axi: add AXI bus driver Rafał Miłecki
2011-04-13 16:31 ` Greg KH
2011-04-13 19:39 ` Rafał Miłecki
2011-04-13 20:31 ` George Kashperko
2011-04-13 20:40 ` Rafał Miłecki
2011-04-13 20:45 ` George Kashperko
2011-04-13 20:55 ` Rafał Miłecki
2011-04-13 21:14 ` George Kashperko
2011-04-13 21:19 ` Rafał Miłecki
2011-04-13 21:24 ` George Kashperko [this message]
2011-04-13 21:33 ` Rafał Miłecki
2011-04-13 23:36 ` Jonas Gorski
2011-04-14 9:51 ` Rafał Miłecki
2011-04-13 20:37 ` Gábor Stefanik
2011-04-13 21:00 ` Greg KH
2011-04-13 21:02 ` Greg KH
2011-04-13 18:24 ` Larry Finger
2011-04-13 19:40 ` Rafał Miłecki
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=1302729850.8479.7.camel@dev.znau.edu.ua \
--to=george@znau.edu.ua \
--cc=Larry.Finger@lwfinger.net \
--cc=andy@andybotting.com \
--cc=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=b43-dev@lists.infradead.org \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=rmk@arm.linux.org.uk \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).