On Sat, 2005-06-18 at 21:15 -0700, Jon Smirl wrote:
> CVSROOT: /cvs/dri
> Module name: drm
> Repository: drm/shared-core/
> Changes by: [EMAIL PROTECTED] 05/06/18 21:15:58
>
> Log message:
> Remove I2C support from radeon driver.
> Same support is available from radeonfb.
>
>
Hmmm
[...huge problems with an i915GM in an Samsung X20 under Xorg 6.8.2
from Mandriva/Mandrake ...]
On 6/16/05, Alan Hourihane <[EMAIL PROTECTED]> wrote:
> You've picked the wrong snapshot for the i915GM chip.
>
> You need i915-20050610 instead of i810-20050610.
after spending way too muc
On Saturday 18 June 2005 15:22, Jon Smirl wrote:
> On 6/18/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > The point to notice here is that these registers generally segmented
> > apart in the card's memory map. If all those trigger regs are within a
> > single 4k range, then that's the only range
DRM has the concepts of master and authenticated. In the current code
master is also equated with needing root priv. The patch splits these
two concepts into three (auth, master, root) and makes them separately
controllable.
For example:
[DRM_IOCTL_NR(DRM_IOCTL_ADD_BUFS)] = {drm_addbufs, 1
On 6/18/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> On Saturday 18 June 2005 13:38, Jerome Glisse wrote:
> > On 6/18/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> > > On Sat, 18 Jun 2005, Jerome Glisse wrote:
> > > > DST_LINE_START 0x1600
> > > > DST_LINE_END 0x1604
> > > > (from radeon fb
On Sat, 18 Jun 2005, Jerome Glisse wrote:
On 6/18/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
On Sat, 18 Jun 2005, Jerome Glisse wrote:
Hi,
Can anyone provide me some informations
on :
DST_LINE_START 0x1600
DST_LINE_END 0x1604
(from radeon fb)
What they are said to do ? End how t
On Saturday 18 June 2005 21:03, Adam Jackson wrote:
> On Saturday 18 June 2005 11:20, Jon Smirl wrote:
> > Access to the registers is something that should require root priv
> > right? Once I can get to the registers I can program them to contol
> > the DMA hardware and then muck with the kernel's
On 6/18/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> On Saturday 18 June 2005 11:20, Jon Smirl wrote:
> > Access to the registers is something that should require root priv
> > right? Once I can get to the registers I can program them to contol
> > the DMA hardware and then muck with the kernel's
On Saturday 18 June 2005 13:38, Jerome Glisse wrote:
> On 6/18/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
> > On Sat, 18 Jun 2005, Jerome Glisse wrote:
> > > DST_LINE_START 0x1600
> > > DST_LINE_END 0x1604
> > > (from radeon fb)
> >
> > From the name, I guess that they initiate line drawing
On Saturday 18 June 2005 11:20, Jon Smirl wrote:
> Access to the registers is something that should require root priv
> right? Once I can get to the registers I can program them to contol
> the DMA hardware and then muck with the kernel's memory and escalate
> my priveldge level. EGL avoids this po
Hi,
I just tried the latest r300 cvs code (with current mesa cvs, latest
Xorg snapshot) but all I get is a lockup as soon as the X server starts.
If I have debugging enabled, I get a loop of radeon_do_cp_idle calls.
Hardware is:
:00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [
On 6/18/05, Vladimir Dergachev <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, 18 Jun 2005, Jerome Glisse wrote:
>
> > Hi,
> >
> > Can anyone provide me some informations
> > on :
> > DST_LINE_START 0x1600
> > DST_LINE_END 0x1604
> > (from radeon fb)
> >
> > What they are said to do ? End how to setup
On Sat, 18 Jun 2005, Jerome Glisse wrote:
Hi,
Can anyone provide me some informations
on :
DST_LINE_START 0x1600
DST_LINE_END 0x1604
(from radeon fb)
What they are said to do ? End how to setup
them.
From the name, I guess that they initiate line drawing in 2d engine.
Hi,
Can anyone provide me some informations
on :
DST_LINE_START 0x1600
DST_LINE_END 0x1604
(from radeon fb)
What they are said to do ? End how to setup
them.
Thx a lot.
Jerome Glisse
---
SF.Net email is sponsored by: Discover Easy Linux Mi
On 6/17/05, Jon Smirl <[EMAIL PROTECTED]> wrote:
> These are the ones marked root.
>
> [DRM_IOCTL_NR(DRM_IOCTL_IRQ_BUSID)] = {drm_irq_by_busid, 0, 1},
> [DRM_IOCTL_NR(DRM_IOCTL_SET_VERSION)] = {drm_setversion, 0, 1},
> [DRM_IOCTL_NR(DRM_IOCTL_SET_UNIQUE)] = {drm_setunique,
I moved this to a new thread. I'd also like to ask everyone to help
with this. I don't want to accidentally introduce a security hole; the
more eyes looking at the code the less likely that will be.
On 6/17/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> drmAddMap has to be root-only because it's ma
On 6/18/05, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> > Everyone except for you that I have heard so far has been assuming the
> > kernel has some very limited capability to change modes in case things
> > go horribly wrong, which OOM killing this hypothetical small daemon
> > certainl
On 6/18/05, Lorenzo Colitti <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> >>When I first boot it's fine, but when the laptop comes back from S3,
> >>even if everything else works, the serial console just prints a couple
> >>of characters of garbage and then dies. :(
> >
> > The serial line is pro
Hi folks,
I installed the r300 driver with X.org and Mesa CVS and it works
without problems until now.
However, one app called mythtv tries use OpenGL and brought this error:
libGL: XF86DRIGetClientDriverName: 4.0.1 r300 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r300_dri.so
On 6/18/05, Nicolai Haehnle <[EMAIL PROTECTED]> wrote:
> On Saturday 18 June 2005 08:20, Benjamin Herrenschmidt wrote:
> > On Fri, 2005-06-17 at 18:37 +0200, Jerome Glisse wrote:
> > > Correct value (previous were ones of a dumb test :)):
> > >
> > > 0x01480xf7fff000 RADEON_MC_FB_LOCAT
Jon Smirl wrote:
When I first boot it's fine, but when the laptop comes back from S3,
even if everything else works, the serial console just prints a couple
of characters of garbage and then dies. :(
The serial line is probably coming back at the default baud rate and
you were setting it higher
Hello,
I extracted this patch by Egbert Eich from SuSe's kernel
source package:
http://www.develer.com/drm-ioctl32.patch
It allows running 32bit DRI clients on 64bit systems,
which is a very common situation due to proprietary
games.
Is there a reason why this code is not appropriate for
mergi
On Saturday 18 June 2005 08:20, Benjamin Herrenschmidt wrote:
> On Fri, 2005-06-17 at 18:37 +0200, Jerome Glisse wrote:
> > Correct value (previous were ones of a dumb test :)):
> >
> > 0x01480xf7fff000 RADEON_MC_FB_LOCATION
> > 0x014c0xfdfffc00 RADEON_MC_AGP_LOCATION
>
23 matches
Mail list logo
