From: yhlu <yhlu.kernel@gmail.com>
To: Grant Grundler <iod00d@hp.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Greg KH <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
openib-general@openib.org, linville@tuxdriver.com,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [openib-general] Re: mthca and LinuxBIOS
Date: Sat, 6 Aug 2005 16:52:21 -0700 [thread overview]
Message-ID: <86802c4405080616526642fe39@mail.gmail.com> (raw)
In-Reply-To: <20050806043354.GA27352@esmail.cup.hp.com>
In LinuxBIOS internal structure for resource, We have index member in resource.
So the resource will be count from 0, ....7 or etc, but index member
will point to real BAR position.
I would like to see Kernel has simmliar definintion.
in LinuxBIOS
typedef uint64_t resource_t;
struct resource {
resource_t base; /* Base address of the resource */
resource_t size; /* Size of the resource */
resource_t limit; /* Largest valid value base + size -1 */
unsigned long flags; /* Descriptions of the kind of resource */
unsigned long index; /* Bus specific per device resource id */
unsigned char align; /* Required alignment (log 2) of the resource */
unsigned char gran; /* Granularity (log 2) of the resource */
/* Alignment must be >= the granularity of the resource */
};
YH
On 8/5/05, Grant Grundler <iod00d@hp.com> wrote:
> On Fri, Aug 05, 2005 at 04:59:37PM -0700, Grant Grundler wrote:
> > ISTR making comments before about the offending patch on linux-pci mailing
> > list. Is this the same patch that assumes pci_dev->resource[i] == BAR[i] ?
>
> I meant the patch assume 1:1 for pci_dev->resource[i] and BAR[i].
> not that the two are equivalent.
>
> grant
>
next prev parent reply other threads:[~2005-08-06 23:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 20:31 [PATCH 0/2] REALLY final InfiniBand updates for 2.6.13 Roland Dreier
2005-07-28 20:31 ` [PATCH 1/2] [IB/cm]: Correct CM port redirect reject codes Roland Dreier
2005-07-28 20:31 ` [PATCH 2/2] [IPoIB] Handle sending of unicast RARP responses Roland Dreier
2005-08-04 0:58 ` [PATCH 1/2] [IB/cm]: Correct CM port redirect reject codes yhlu
2005-08-04 1:39 ` [openib-general] " Grant Grundler
2005-08-04 4:44 ` mthca and LinuxBIOS (was: [PATCH 1/2] [IB/cm]: Correct CM port redirect reject codes) Roland Dreier
2005-08-04 16:33 ` yhlu
2005-08-04 16:36 ` mthca and LinuxBIOS Roland Dreier
2005-08-04 17:23 ` yhlu
2005-08-04 18:01 ` yhlu
2005-08-04 18:35 ` Roland Dreier
2005-08-04 19:30 ` yhlu
2005-08-05 3:47 ` Roland Dreier
2005-08-05 18:03 ` yhlu
2005-08-05 18:07 ` yhlu
2005-08-05 18:13 ` Roland Dreier
2005-08-05 18:26 ` yhlu
2005-08-05 19:25 ` yhlu
2005-08-05 19:45 ` yhlu
2005-08-05 20:28 ` yhlu
2005-08-05 20:38 ` Linus Torvalds
2005-08-05 22:00 ` Greg KH
2005-08-05 22:25 ` yhlu
2005-08-05 23:03 ` Greg KH
2005-08-06 5:29 ` [openib-general] " Grant Grundler
2005-08-05 23:06 ` Linus Torvalds
2005-08-05 23:59 ` [openib-general] " Grant Grundler
2005-08-06 4:33 ` Grant Grundler
2005-08-06 23:52 ` yhlu [this message]
2005-08-07 9:49 ` Ivan Kokshaysky
2005-08-05 18:11 ` Roland Dreier
2005-08-06 0:57 ` yhlu
2005-08-06 1:30 ` Roland Dreier
2005-08-06 2:47 ` yhlu
2005-08-04 6:42 ` [PATCH 1/2] [IB/cm]: Correct CM port redirect reject codes Michael S. Tsirkin
2005-08-04 18:22 ` yhlu
2005-08-08 12:21 ` Michael S. Tsirkin
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=86802c4405080616526642fe39@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--cc=iod00d@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=openib-general@openib.org \
--cc=torvalds@osdl.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