[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1302729850.8479.7.camel@dev.znau.edu.ua>
Date: Thu, 14 Apr 2011 00:24:10 +0300
From: George Kashperko <george@...u.edu.ua>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Greg KH <greg@...ah.com>, linux-wireless@...r.kernel.org,
"John W. Linville" <linville@...driver.com>,
b43-dev@...ts.infradead.org,
Michael Büsch <mb@...sch.de>,
Larry Finger <Larry.Finger@...inger.net>,
Arend van Spriel <arend@...adcom.com>,
linux-arm-kernel@...ts.infradead.org,
Russell King <rmk@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Andy Botting <andy@...ybotting.com>,
linuxdriverproject <devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH V4] axi: add AXI bus driver
> 2011/4/13 George Kashperko <george@...u.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists