From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eric Anholt <eric@anholt.net>
Cc: David Airlie <airlied@linux.ie>,
linuxppc-dev@ozlabs.org, dri-devel@lists.sf.net
Subject: Re: [PATCH 3/3] drm: Make drm_local_map use a resource_size_t offset
Date: Tue, 03 Feb 2009 08:21:28 +1100 [thread overview]
Message-ID: <1233609688.18767.118.camel@pasglop> (raw)
In-Reply-To: <1233608464.4932.15.camel@gaiman>
>
> Could this comment instead be maybe:
>
> Because the kernel-userspace ABI is fixed at a 32-bit offset, while PCI
> resources may live above that, we ignore the map offset for maps of type
> _DRM_FRAMEBUFFER or _DRM_REGISTERS. It is assumed that each driver will
> have only one resource of each type.
>
> (I want to remember later what exact ABI problem was in question)
Fair enough. I'll repost.
Cheers,
Ben.
next prev parent reply other threads:[~2009-02-02 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 5:55 [PATCH 3/3] drm: Make drm_local_map use a resource_size_t offset Benjamin Herrenschmidt
2009-02-02 21:01 ` Eric Anholt
2009-02-02 21:21 ` Benjamin Herrenschmidt [this message]
2009-02-03 8:39 ` Dave Airlie
2009-02-03 9:02 ` Benjamin Herrenschmidt
2009-02-03 9:06 ` Dave Airlie
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=1233609688.18767.118.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=eric@anholt.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).