From: Paul Bolle <pebolle@tiscali.nl>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Steven Newbury <steve@snewbury.org.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset flushing
Date: Sat, 08 Mar 2014 15:44:37 +0100 [thread overview]
Message-ID: <1394289877.31006.2.camel@x41> (raw)
In-Reply-To: <CAErSpo7Np8oju1ENQA5EgEpN4=Vv7f3s4E823ecbyp6FCWPL_Q@mail.gmail.com>
Bjorn Helgaas schreef op za 08-03-2014 om 07:12 [-0700]:
> I assume you have CONFIG_PHYS_ADDR_T_64BIT=n (which is perfectly
> legal); let me know if otherwise.
$ grep CONFIG_PHYS_ADDR_T_64BIT /boot/config-3.14.0-0.rc5.1.local2.fc20.i686
# CONFIG_PHYS_ADDR_T_64BIT is not set
So, yes, CONFIG_PHYS_ADDR_T_64BIT=n here.
Paul Bolle
next prev parent reply other threads:[~2014-03-08 14:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 19:06 agp/intel: can't ioremap flush page - no chipset flushing Paul Bolle
2014-02-08 19:59 ` Daniel Vetter
2014-02-08 20:22 ` Paul Bolle
2014-02-09 0:02 ` Daniel Vetter
2014-02-09 13:15 ` [Intel-gfx] " Steven Newbury
2014-02-09 13:25 ` Paul Bolle
2014-02-09 13:32 ` Steven Newbury
2014-02-10 21:33 ` Bjorn Helgaas
2014-03-06 20:25 ` Paul Bolle
2014-03-06 21:38 ` Bjorn Helgaas
2014-03-07 20:33 ` Bjorn Helgaas
2014-03-07 9:48 ` Paul Bolle
2014-03-07 16:55 ` Bjorn Helgaas
2014-03-07 17:16 ` Paul Bolle
2014-03-07 20:40 ` Bjorn Helgaas
2014-03-07 21:03 ` Paul Bolle
2014-03-07 22:07 ` Bjorn Helgaas
2014-03-08 14:12 ` Bjorn Helgaas
2014-03-08 14:44 ` Paul Bolle [this message]
2014-03-10 18:24 ` Bjorn Helgaas
2014-03-10 23:45 ` Paul Bolle
2014-03-11 0:07 ` Bjorn Helgaas
2014-03-11 0:15 ` Paul Bolle
2014-03-11 2:07 ` Bjorn Helgaas
2014-03-11 9:20 ` Paul Bolle
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=1394289877.31006.2.camel@x41 \
--to=pebolle@tiscali.nl \
--cc=airlied@linux.ie \
--cc=bhelgaas@google.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@snewbury.org.uk \
--cc=yinghai@kernel.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