From: Richard Baverstock <beaver@gto.net>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AGPGART for VIA vt8235, kernel 2.4.21-pre2
Date: Fri, 3 Jan 2003 13:13:38 -0500 [thread overview]
Message-ID: <20030103131338.4c9102e3.beaver@gto.net> (raw)
In-Reply-To: <20030103174323.GA10327@codemonkey.org.uk>
On Fri, 3 Jan 2003 17:43:23 +0000
Dave Jones <davej@codemonkey.org.uk> wrote:
> What exactly do you mean by 'it' ? The PCI device id ?
>
Since he was referring to the host bridge names, i thought he meant the naming conventions.
> If they share the same device ID, then Bernhards patch is
> really no better...
>
> #define PCI_DEVICE_ID_VIA_P4X333 0x3168
>
> In fact, P4X333 defines a chipset rather than a chip.
> According to ..
> http://www.viatech.com/en/apollo/p4x333.jsp and
> http://www.viatech.com/en/apollo/p4x400.jsp ,
> the northbridge is a VT8754 in both models, so the
> correct define would seem to be PCI_DEVICE_ID_VIA_8754
Then we were both wrong, and it should be vt8754.
> Just to confirm, device 3168 is the host bridge in lspci output right?
> And this does all work when you run a DRI application ?
>
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3168 (rev 03)
And yes, DRI works :)
Rich
prev parent reply other threads:[~2003-01-03 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 19:53 Richard Baverstock
2003-01-03 16:16 ` Vojtech Pavlik
2003-01-03 17:22 ` Richard Baverstock
2003-01-03 17:43 ` Dave Jones
2003-01-03 18:00 ` Dave Jones
2003-01-03 18:24 ` Richard Baverstock
2003-01-03 18:13 ` Richard Baverstock [this message]
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=20030103131338.4c9102e3.beaver@gto.net \
--to=beaver@gto.net \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®