On Wed, 13 Oct 2004 14:37:12 -0700, Ian Romanick <[EMAIL PROTECTED]> wrote:
> Michel Dänzer wrote:
>
> > Anyway, I think we're on a tangent here, as the problem doesn't seem to
> > be PPC specific at all.
>
> I dug out the Rage 128 that I have for the PC, and it works just fine.
> glxgears, readp
On Fri, 15 Oct 2004, Felix [ISO-8859-1] Kühling wrote:
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:58:
On Fri, 15 Oct 2004 03:55:37 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote:
I'm trying to get Shadow status working in the savage driver. I'd like
to put the status page into locked shared memo
> BTW, I don't see any use of it in the via driver. But it is used by
> mach64. I also see that i810-i915 use pci_alloc_consistent directly. Is
> that portable to BSD?
nope.. i810/830 aren't ported to BSD, and i915 has a #ifdef __freebsd__ or
something like that I think.. granted i915 doesn't wor
To get debug output now you need to use:
insmod ./drm.ko drm_debug=1
The code is switched to use 2.6 parameters instead of the old 2.4 ones.
--
Jon Smirl
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJ
I just switched linux-core over to 2.6 parameters to get debug output use
insmod ./drm.ko drm_debug=1
If the module is compiled in use
drm.drm_debug=1
on the kernel line.
The personalities share the drm_debug flag, that's why it is named
drm_debug instead of debug to stop symbol conflicts. When
On Fri, Oct 15, 2004 at 03:55:37AM +0200, Felix K?hling wrote:
> I'm trying to get Shadow status working in the savage driver. I'd like
> to put the status page into locked shared memory and tell the Savage
> chips about its physical address. I used a drmAddMap call copied from
> the MGA driver tha
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:58:
> On Fri, 15 Oct 2004 03:55:37 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote:
> > I'm trying to get Shadow status working in the savage driver. I'd like
> > to put the status page into locked shared memory and tell the Savage
> > chips about its phy
On Fri, 15 Oct 2004, Felix [ISO-8859-1] Kühling wrote:
Either I'm to stupid for it or the debug parameter of the drm module is
not working correctly. "modinfo drm" shows that there should be a debug
parameter. But when I pass it to modprobe I get an error message:
drm: Unknown parameter `de
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1519
--- Additional Comments From [EMAIL PROTECTED] 2004-10-14 19:13 ---
dbg = 0x6 f
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:56:
> On Fri, 15 Oct 2004 03:52:39 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote:
> > Snapshots are still built with linux-2.6. When we really make the change
> > to the linux-core stuff we'll also have to update the path drm/shared to
> > drm/shared-co
On Fri, 15 Oct 2004 03:59:57 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote:
> Either I'm to stupid for it or the debug parameter of the drm module is
> not working correctly. "modinfo drm" shows that there should be a debug
> parameter. But when I pass it to modprobe I get an error message:
>
>
On Fri, 15 Oct 2004 03:55:37 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote:
> I'm trying to get Shadow status working in the savage driver. I'd like
> to put the status page into locked shared memory and tell the Savage
> chips about its physical address. I used a drmAddMap call copied from
> the
Either I'm to stupid for it or the debug parameter of the drm module is
not working correctly. "modinfo drm" shows that there should be a debug
parameter. But when I pass it to modprobe I get an error message:
drm: Unknown parameter `debug'
and the module refuses to load.
With the linux-
On Fri, 15 Oct 2004 03:52:39 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote:
> Snapshots are still built with linux-2.6. When we really make the change
> to the linux-core stuff we'll also have to update the path drm/shared to
> drm/shared-core in the Mesa makefiles so they always build against the
I'm trying to get Shadow status working in the savage driver. I'd like
to put the status page into locked shared memory and tell the Savage
chips about its physical address. I used a drmAddMap call copied from
the MGA driver that looked like it did what I wanted. But I had to find
out that the hand
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:39:
> Is drm-core being included in the current snapshots? Is it time yet to
> remove the linux-2.6 drm directory and push more people towards
> testing drm-core? Reported problems against drm-core are getting more
> obscure now.
Snapshots are still bui
Is drm-core being included in the current snapshots? Is it time yet to
remove the linux-2.6 drm directory and push more people towards
testing drm-core? Reported problems against drm-core are getting more
obscure now.
--
Jon Smirl
[EMAIL PROTECTED]
--
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1623
--- Additional Comments From [EMAIL PROTECTED] 2004-10-14 16:00 ---
(In reply t
Am 2004.10.13 03:51:44 +0200 schrieb(en) Eric Anholt:
[...]
> New patch at:
> http://pdx.freedesktop.org/~anholt/dri/r200-projtex-8.diff
[...]
It seems Radeon R100 and R200 can't do projective texturing when
using tiny vertices (without w).
While fiddling around with R100 and tvertex-patch i not
On Thu, Oct 14, 2004 at 12:16:14 -0400, Vladimir Dergachev wrote:
>
>
> On Thu, 14 Oct 2004, Tino Keitel wrote:
[...]
> >There is no "linux-core" or "shared-core" directory, just "linux"
> >and "shared" btw., if this matters.
>
> Try using DRI CVS, module drm. Do a fresh checkout, just in cas
On Thu, 14 Oct 2004, Adam K Kirchhoff wrote:
I just heard that ATI has released r300 specs to Xi Graphics. While I'm sure
it's under an NDA, at least is shows a little more flexibility from ATI in
terms of releasing those specs. Might it be worth approaching them now in
releasing those specs
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1635
[EMAIL PROTECTED] changed:
What|Removed |Added
> What about the getmap ioctl? You may be right though, that one might get
> unexpected results. AFAICT maps are added at the head of the list. So
> the order is reversed and maps added by the Xserver mess up the indices.
GetMap ioctl returns them all and you have to search through them.
--
Jon
Am Do, den 14.10.2004 schrieb Jon Smirl um 18:38:
> I did it like this at startup time:
>
> /* registers */
> if ((ret = drm_initmap(dev, pci_resource_start(dev->pdev, 2),
> pci_resource_len(dev->pdev, 2), _DRM_REGISTERS,
> 0)))
> return ret;
>
> if (!(dev_priv->mmio = drm_core_fi
I did it like this at startup time:
/* registers */
if ((ret = drm_initmap(dev, pci_resource_start(dev->pdev, 2),
pci_resource_len(dev->pdev, 2), _DRM_REGISTERS,
0)))
return ret;
if (!(dev_priv->mmio = drm_core_findmap(dev, pci_resource_start(dev->pdev, 2
return DRM_
I just heard that ATI has released r300 specs to Xi Graphics. While I'm
sure it's under an NDA, at least is shows a little more flexibility from
ATI in terms of releasing those specs. Might it be worth approaching
them now in releasing those specs to the DRI developers under the same
rules an
{0x1002, 0x4150, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
In dmesg, I still have the same output.
There is no "linux-core" or "shared-core" directory, just "linux" and
"shared" btw., if this matters.
you probably need to run cvs co rather than cvs update from time to
time. update doesn'
On Thu, 14 Oct 2004 17:53:07 +0200, Tino Keitel <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 14, 2004 at 11:29:05 -0400, Vladimir Dergachev wrote:
> >
> >
> > On Thu, 14 Oct 2004, Tino Keitel wrote:
> >
> > >Hi folks,
> > >
> > >I grabbed the current CVS for the r300 driver, added the PCI ID of by
> >
On Thu, 14 Oct 2004, Tino Keitel wrote:
Hi folks,
I grabbed the current CVS for the r300 driver, added the PCI ID of by
Radeon 9600 (0x4150) to drm_pciids.h and built the module, but the
kernel only shows this after loading the module:
You need to add your pci id to drm_pciids.txt file in drm/shar
On Thu, 14 Oct 2004, Tino Keitel wrote:
On Thu, Oct 14, 2004 at 11:29:05 -0400, Vladimir Dergachev wrote:
On Thu, 14 Oct 2004, Tino Keitel wrote:
Hi folks,
I grabbed the current CVS for the r300 driver, added the PCI ID of by
Radeon 9600 (0x4150) to drm_pciids.h and built the module, but the
kern
On Thu, Oct 14, 2004 at 11:29:05 -0400, Vladimir Dergachev wrote:
>
>
> On Thu, 14 Oct 2004, Tino Keitel wrote:
>
> >Hi folks,
> >
> >I grabbed the current CVS for the r300 driver, added the PCI ID of by
> >Radeon 9600 (0x4150) to drm_pciids.h and built the module, but the
> >kernel only shows t
thx for answering,
i checked it but it still seems to be a too much complex driver for
what i need to develop, that is why i chose fb as a squeleton. What i
need is a simple driver in which i would code my own pipeline stages
(projection and rendering stages).
Regards
Pierre TEMPLIER
In the savage driver I'm going to use permanent maps from the start. So
there is no need for the Xserver to pass the permanent maps back to the
kernel driver in the init ioctl. Instead I want to find the maps by
index in the init ioctl. Therefore I added a drm_core_getmap inline
function similar to
On Thu, 14 Oct 2004 16:11:14 +0300, Pierre TEMPLIER <[EMAIL PROTECTED]> wrote:
> I'm trying to create a new DRI driver (software rendering). To do that
> i took fb (src/mesa/drivers/dri/fb) as a template for a minimal dri
> driver to create the driver.
>
> Q: when i try to compile fb driver (fb_dr
I'm trying to create a new DRI driver (software rendering). To do that
i took fb (src/mesa/drivers/dri/fb) as a template for a minimal dri
driver to create the driver.
Q: when i try to compile fb driver (fb_dri.c), i get the following
errors :
current/front/backBuffer are not present in structure
On Thu, 2004-10-14 at 04:38, Alex Deucher wrote:
On Thu, 14 Oct 2004 00:55:51 +0200, David <[EMAIL PROTECTED]> wrote:
> Hi. Sorry to be too picky, but I've found that after the Xv fix 4 pixels are
> missing on the right side of the screen.
> You can check a sample image to test this here (plea
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1635
Summary: tdfx_tex.c:convertPalette() may return without return
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1635
--- Additional Comments From [EMAIL PROTECTED] 2004-10-14 06:49 ---
Created an
Am 2004.10.13 23:37:12 +0200 schrieb(en) Ian Romanick:
> Michel Dänzer wrote:
>
> > Anyway, I think we're on a tangent here, as the problem doesn't seem to
> > be PPC specific at all.
>
> I dug out the Rage 128 that I have for the PC, and it works just fine.
> glxgears, readpix, all of it. :(
>
Hi folks,
I grabbed the current CVS for the r300 driver, added the PCI ID of by
Radeon 9600 (0x4150) to drm_pciids.h and built the module, but the
kernel only shows this after loading the module:
radeon: Ignoring new-style parameters in presence of obsolete ones
[drm] Initialized radeon 1.11.1 20
Am 2004.10.13 23:37:12 +0200 schrieb(en) Ian Romanick:
> Michel Dänzer wrote:
>
> > Anyway, I think we're on a tangent here, as the problem doesn't seem to
> > be PPC specific at all.
>
> I dug out the Rage 128 that I have for the PC, and it works just fine.
> glxgears, readpix, all of it. :(
>
Hi!
is DRM_WRITEMEMORYBARRIER() the right way to make sure data has been
flushed to AGP memory before firing it off to the DMA engine? If so, are
there performance implications?
/Thomas
---
This SF.net email is sponsored by: IT Product Guide
El Jueves, 14 de Octubre del 2004 5:38 AM, Alex Deucher escribió:
> On Thu, 14 Oct 2004 00:55:51 +0200, David <[EMAIL PROTECTED]> wrote:
> > Hi. Sorry to be too picky, but I've found that after the Xv fix 4 pixels
> > are missing on the right side of the screen.
> > You can check a sample image to
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1633
Summary: via_alloc_texture fail
Product: Mesa
Version: CVS
Am Do, den 14.10.2004 schrieb Patrick McFarland um 6:51:
> http://dri.sourceforge.net/cgi-bin/moin.cgi/Building mentions a
> buildtools.patch, is this still required for xorg cvs?
It's only needed if you want to compile the latest versions of glxgears,
glxinfo and xdriinfo while not building any
On Wed, 13 Oct 2004 01:47:27 +0200
Felix Kühling <[EMAIL PROTECTED]> wrote:
[snip]
>
> I need to make sure that libexpat is compiled in statically. This was
> the case with the old XFree86-based snapshots. Somehow I must have
> screwed up with the new ones. Hang on, this should be fixed tomorrow
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1623
--- Additional Comments From [EMAIL PROTECTED] 2004-10-14 00:48 ---
I think the
47 matches
Mail list logo
