From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Andy Lutomirski <luto@kernel.org>
Cc: "French, Nicholas A." <naf@ou.edu>,
"hans.verkuil@cisco.com" <hans.verkuil@cisco.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: ivtv: use arch_phys_wc_add() and require PAT disabled
Date: Thu, 8 Mar 2018 04:14:11 +0000 [thread overview]
Message-ID: <20180308041411.GR14069@wotan.suse.de> (raw)
In-Reply-To: <20180308040601.GQ14069@wotan.suse.de>
On Thu, Mar 08, 2018 at 04:06:01AM +0000, Luis R. Rodriguez wrote:
> On Thu, Mar 08, 2018 at 03:16:29AM +0000, French, Nicholas A. wrote:
> > On Wed, Mar 07, 2018 at 07:02:05PM +0000, Luis R. Rodriguez wrote:
> > > On Tue, Mar 06, 2018 at 09:01:10PM +0000, French, Nicholas A. wrote:
> > > > any reason why PAT can't be enabled for ivtvfb as simply as in the attached
> > > > patch?
> > >
> > > Prior to your change the OSD buffer was obtained using the itv->dec_mem + oi->video_rbase
> > > given itv->dec_mem was initialized via [...]
> > > itv->dec_mem = ioremap_nocache(itv->base_addr + IVTV_DECODER_OFFSET - oi->video_buffer_size,
> > > IVTV_DECODER_SIZE);
> >
> > Ah, I see. So my proposed ioremap_wc call was only "working" by aliasing the
> > ioremap_nocache()'d mem area and not actually using write combining at all.
>
> There are some debugging PAT toys out there I think but I haven't played with
> them yet or I forgot how to to confirm or deny this sort of effort, but
> likeley.
In fact come to think of it I believe some neurons are telling me that if
two type does not match we'd get an error?
Luis
next prev parent reply other threads:[~2018-03-08 4:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR03MB3035EE1AFCEE298AFB15AC46D3C60@DM5PR03MB3035.namprd03.prod.outlook.com>
[not found] ` <20180301171936.GU14069@wotan.suse.de>
[not found] ` <DM5PR03MB303587F12D7E56B951730A76D3D90@DM5PR03MB3035.namprd03.prod.outlook.com>
2018-03-07 19:02 ` Luis R. Rodriguez
2018-03-08 3:16 ` French, Nicholas A.
2018-03-08 4:06 ` Luis R. Rodriguez
2018-03-08 4:14 ` Luis R. Rodriguez [this message]
2018-03-08 5:23 ` French, Nicholas A.
2018-03-10 16:57 ` French, Nicholas A.
2018-03-10 18:20 ` Andy Lutomirski
2018-03-11 19:51 ` Nick French
2018-03-11 20:19 ` Andy Lutomirski
2018-03-11 22:08 ` Nick French
2018-03-10 19:03 ` Luis R. Rodriguez
2018-03-10 19:05 ` Luis R. Rodriguez
2018-03-11 23:24 ` Ian Armstrong
2018-03-12 4:04 ` Nick French
2018-03-12 19:05 ` Ian Armstrong
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=20180308041411.GR14069@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luto@kernel.org \
--cc=naf@ou.edu \
/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
all inboxes | Powered by JetHome®