On Tue, 2005-05-03 at 15:24 +1000, Benjamin Herrenschmidt wrote:
> Hi !
>
> The radeon DRM has some interesting bug that paul and I discovered to
> cause all sort of problems like crashing the machine on suspend/resume
> (go figure ...) etc...
>
> dev_priv->gart_vm_start = dev_priv->fb_loc
On Tue, 2005-05-03 at 10:09 +0200, Jerome Glisse wrote:
> Has i still doesn't understand the big pictures of video drivers, i
> was wondering
> if this could have an impact on bytes swapping on r300. Thus the problem
> of bit blit we have on r300 & X driver. I don't think so but as i don't well
>
Aapo Tahkola wrote:
On Thu, 21 Apr 2005 09:57:48 -0400 (EDT)
Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
On Thu, 21 Apr 2005, Aapo Tahkola wrote:
On Wed, 23 Feb 2005 15:03:38 -0500 (EST)
Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
With regard to state switching, it might be worth it to sim
On Tue, 2005-05-03 at 15:24 +1000, Benjamin Herrenschmidt wrote:
>
> The radeon DRM has some interesting bug that paul and I discovered to
> cause all sort of problems like crashing the machine on suspend/resume
> (go figure ...) etc...
>
> dev_priv->gart_vm_start = dev_priv->fb_location
>
On Tue, 2005-05-03 at 10:09 +0200, Jerome Glisse wrote:
> On 5/3/05, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> > Ok, I'm cross posting here because X.org is doing it wrong too. On R300,
> > for some reason I don't fully understand, it just goes back to the "old"
> > way of putting the FB
On Tue, 2005-05-03 at 10:41 +0200, Jerome Glisse wrote:
> > Now, the setting above has to be done the most intelligently you can
> > based on 1) do you need 2 apertures with different swapper settings
> > (typical of BE machines) or not, 2) what is your CONFIG_APER_SIZE
> > strapping vs. how much V
> > Note that with huge VRAM sizes appearing, we also want to make sure that
> > wheverver we put it won't overlap the 32 bits space since CONFIG_MEM_SIZE
> > can be huge nowadays... and if it does, put the GART just _before_ the
> > framebuffer instead. Again, this is all cards space, not bus vie
> In the meantime, here's a patch against current Linus "git" that I'm
> tempted to push asap so that at least 2.6.12 avoids the problem of
> overlapping which causes random stuffs to happen with lockups. The
> "issue" here is even if you don't have an r300-friendly DRM, it will
> still try to init
On Wed, 2005-05-04 at 00:39 +1000, Benjamin Herrenschmidt wrote:
> > > Note that with huge VRAM sizes appearing, we also want to make sure that
> > > wheverver we put it won't overlap the 32 bits space since CONFIG_MEM_SIZE
> > > can be huge nowadays... and if it does, put the GART just _before_ th
On Wed, 4 May 2005, Benjamin Herrenschmidt wrote:
Note that with huge VRAM sizes appearing, we also want to make sure that
wheverver we put it won't overlap the 32 bits space since CONFIG_MEM_SIZE
can be huge nowadays... and if it does, put the GART just _before_ the
framebuffer instead. Again, t
On Tue, 03 May 2005 14:59:53 +0100
Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Aapo Tahkola wrote:
> > On Thu, 21 Apr 2005 09:57:48 -0400 (EDT)
> > Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> >
> >
> >>
> >>On Thu, 21 Apr 2005, Aapo Tahkola wrote:
> >>
> >>
> >>>On Wed, 23 Feb 2005 15:03:38
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://bugs.freedesktop.org/show_bug.cgi?id=3195
Summary: Setting GL_TEXTURE_LOD_BIAS_EXT can cause a segfault.
P
>From Jon Smirl on Tuesday, 03 May, 2005:
>http://www.extremetech.com/article2/0,1558,1791681,00.asp
Ars Technica's Tiger article (specifically on the evolution of the OSX
graphics system) was very informative as well.
http://arstechnica.com/reviews/os/macosx-10.4.ars
-Joseph
--
[EMAIL PROTEC
El Tue, 3 May 2005 18:09:41 -0400,
Jon Smirl <[EMAIL PROTECTED]> escribió:
> "What does this actually mean? 3D surfaces can be paged out to virtual
> memory as needed. This is critical in the Longhorn user interface,
> where every window will be a 3D surface. Applications can now be
> bigger than
> If a conflict can't be avoided, we could fail gracefully upfront
> (suggesting to make the GART aperture smaller, ...) instead of risking
> subtle breakage?
Well, I don't know of any clean platform independant way to know if
there is a conflict or not, that is to know where RAM is in bus space.
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://bugs.freedesktop.org/show_bug.cgi?id=3198
Summary: Savage crashes with bus type PCI
Product: DRI
On Wed, 2005-05-04 at 09:48 +1000, Benjamin Herrenschmidt wrote:
> > If a conflict can't be avoided, we could fail gracefully upfront
> > (suggesting to make the GART aperture smaller, ...) instead of risking
> > subtle breakage?
>
> Well, I don't know of any clean platform independant way to know
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://bugs.freedesktop.org/show_bug.cgi?id=2596
--- Additional Comments From [EMAIL PROTECTED] 2005-05-03 19:58 ---
The D
On Wed, 2005-05-04 at 11:41 +1000, Benjamin Herrenschmidt wrote:
>
> Ok, here's a new patch that I'll send to Linus if you (Michel) acks it.
>
> I use CONFIG_MEMSIZE, I don't try to max out with CONFIG_APER_SIZE since
> I beleive we just don't care, and that avoids putting pressure on the
> GART
19 matches
Mail list logo
