From: "Rafał Miłecki" <zajec5@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] drm/radeon/kms: implement reading PCIE lanes on R600+
Date: Thu, 18 Feb 2010 12:40:58 +0100 [thread overview]
Message-ID: <b170af451002180340r141bc28ag94597f2dfe6b52f6@mail.gmail.com> (raw)
In-Reply-To: <21d7e9971002172057j14448d0dyc93905c3a7199158@mail.gmail.com>
W dniu 18 lutego 2010 05:57 użytkownik Dave Airlie <airlied@gmail.com> napisał:
> 2010/2/18 Rafał Miłecki <zajec5@gmail.com>:
>> Ported from DDX
>>
>
> The PCIE regs on r600 are the same offsets at the ones on rv370 from
> what I can see
> probably don't need to add a new PCIE_P struct at all I think the
> rv370 functions should work.
Err, not really?
# egrep --color "define.*PCIE_(PORT_)?INDEX" ./*h
./r600_reg.h:#define R600_PCIE_PORT_INDEX 0x0038
./radeon_reg.h:#define RADEON_PCIE_INDEX 0x0030
# egrep --color "define.*PCIE_(PORT_)?DATA" ./*h
./r600_reg.h:#define R600_PCIE_PORT_DATA 0x003c
./radeon_reg.h:#define RADEON_PCIE_DATA 0x0034
--
Rafał
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-02-18 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 22:57 [PATCH] drm/radeon/kms: implement reading PCIE lanes on R600+ Rafał Miłecki
2010-02-18 4:57 ` Dave Airlie
2010-02-18 11:40 ` Rafał Miłecki [this message]
2010-02-18 15:19 ` Alex Deucher
2010-02-18 15:20 ` Alex Deucher
2010-02-18 19:10 ` 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=b170af451002180340r141bc28ag94597f2dfe6b52f6@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.