From: Christoph Hellwig <hch@infradead.org>
To: Mike Werner <werner@sgi.com>
Cc: davej@codemonkey.org.uk, linux-kernel@vger.kernel.org,
dri-devel@lists.sourceforge.net
Subject: Re: [patch 2.6.10-rc3 1/4] agpgart: allow multiple backends to be initialized
Date: Sun, 19 Dec 2004 13:37:58 +0000 [thread overview]
Message-ID: <20041219133758.GB599@infradead.org> (raw)
In-Reply-To: <200412180917.14255.werner@sgi.com>
On Sat, Dec 18, 2004 at 09:17:14AM -0800, Mike Werner wrote:
> > The agp_bridge_find function pointer is bogus, that way you can only support
> > one backend at a time.
> Obviously you mean one type of backend here.
> I have tried to simplify this patch as much as possible so that it only tries to do one thing
> and that is just the api change. I think the searching for valid bridges is a separate issue
> since none of the currently supported hardware needs it. The only possible platform
> that I assumed might is amd64 and Andi Kleen specifically told me it doesn't.
I agree that it's a separate issue. So keep the function poniter out for
the time beeing and we can discuss it last.
> I don't agree that you *must* pass the agp_bridge_data pointer for every method.
> You don't need it for bind/unbind/free if you associate each memory region
> allocated using agp_allocate_memory(bridge,...) with a particular bridge
> which is what the patch does. That is, agp_memory knows which bridge it belongs to.
Yes, agreed. But you need to pass the agp_bridge_data to each function in
some way.
next prev parent reply other threads:[~2004-12-19 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 20:55 Mike Werner
2004-12-18 14:48 ` Christoph Hellwig
2004-12-18 17:17 ` Mike Werner
2004-12-19 13:37 ` Christoph Hellwig [this message]
2004-12-20 23:59 ` Mike Werner
2004-12-22 0:08 ` Mike Werner
2004-12-22 19:08 ` Mike Werner
2004-12-23 1:42 ` [resend patch 2.6.10-rc3 1/3] " Mike Werner
2004-12-20 14:05 ` [patch 2.6.10-rc3 1/4] " Alan Cox
[not found] <200412171255.59390.werner@sgi.com.suse.lists.linux.kernel>
2004-12-18 8:23 ` Andi Kleen
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=20041219133758.GB599@infradead.org \
--to=hch@infradead.org \
--cc=davej@codemonkey.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@sgi.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
all inboxes | Powered by JetHome®