public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] agp/intel: Fix dma mask for Sandybridge
Date: Mon, 23 Aug 2010 08:31:42 +0200	[thread overview]
Message-ID: <s5hiq31delt.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100823061922.GD29442@zhen-devel.sh.intel.com>

At Mon, 23 Aug 2010 14:19:22 +0800,
Zhenyu Wang wrote:
> 
> On 2010.08.23 08:02:42 +0200, Takashi Iwai wrote:
> > 
> > Also, I don't understand the logic of 40bit addr calculation:
> > 
> > > static unsigned long intel_gen6_mask_memory(struct agp_bridge_data *bridge,
> > >                                             dma_addr_t addr, int type)
> > > {
> > >         /* Shift high bits down */
> > >        addr |= (addr >> 28) & 0xff;
> > 
> > Isn't it 0xff0?
> > 
> 
> No. This depends on hw 32bit PTE format for sandybridge.
> 
> bit 31			 bit 11			 bit 4			bit 0
>    |<-physical addr 31:12->|<-physical addr 39:32->|<-cache ctl 3:1->|valid|

Then I really don't understand why it works.
You shift 28bit and mask with 0xff.  Obviously it overwrite bits 0:3
with original 28:31 bits.  Masking 0xff0 fixes the issue.

And, the information like above would be greatly helpful if put into
either changelog or comment...


thanks,

Takashi

  reply	other threads:[~2010-08-23  6:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 15:36 [PATCH] agp/intel: Fix dma mask for Sandybridge Takashi Iwai
2010-08-23  1:35 ` Zhenyu Wang
2010-08-23  5:29   ` Takashi Iwai
2010-08-23  5:43     ` Zhenyu Wang
2010-08-23  6:02       ` Takashi Iwai
2010-08-23  6:13         ` Takashi Iwai
2010-08-23  6:19         ` Zhenyu Wang
2010-08-23  6:31           ` Takashi Iwai [this message]
2010-08-23  6:48             ` Zhenyu Wang
2010-08-23 14:02               ` Eric Anholt

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=s5hiq31delt.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhenyuw@linux.intel.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