On Sun, Aug 02, 2009 at 08:00:01AM -0700, wrote:
> From: Michel Dänzer
>
> ---
> composite/compinit.c |4 +++-
> exa/exa_render.c | 30 +-
> fb/fbpict.h |2 ++
> hw/xfree86/xaa/xaaPict.c | 20
> render/picture
On Thu, 2009-10-08 at 19:11 -0700, Aaron Plattner wrote:
> On Sun, Aug 02, 2009 at 08:00:01AM -0700, wrote:
> >
> > diff --git a/composite/compinit.c b/composite/compinit.c
> > index dfc3929..6159e4e 100644
> > --- a/composite/compinit.c
> > +++ b/composite/compinit.c
> > @@ -238,6 +238,7 @@ sta
> On Thu, 2009-10-08 at 19:11 -0700, Aaron Plattner wrote:
> > On Sun, Aug 02, 2009 at 08:00:01AM -0700, wrote:
> > >
> > > diff --git a/composite/compinit.c b/composite/compinit.c
> > > index dfc3929..6159e4e 100644
> > > --- a/composite/compinit.c
> > > +++ b/composite/compinit.c
> > > @@ -238,
On Fri, 2009-10-09 at 11:26 +0200, Mark Kettenis wrote:
> > Hmm, right. The two hunks above were aimed towards my first approach for
> > fixing radeon KMS on big endian machines, by making the root window
> > visual BGRA. I've since abandoned that approach for a different one, so
> > those hun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On Oct 13, 2009, at 2:51 PM, Adam Jackson wrote:
> On Fri, 2009-10-09 at 11:26 +0200, Mark Kettenis wrote:
>
>>> Hmm, right. The two hunks above were aimed towards my first
>>> approach for
>>> fixing radeon KMS on big endian machines, by ma
On Tue, 2009-10-13 at 15:22 -0400, Michael wrote:
> On Oct 13, 2009, at 2:51 PM, Adam Jackson wrote:
> > Not that you're wrong (about proper BGRA support), but I think you may
> > be wrong (about i128). I'd like to see an X log from that chip with
> > Option "Debug" "on" in xorg.conf, I suspect CM
> From: Michael
> Date: Tue, 13 Oct 2009 15:22:55 -0400
>
> Hello,
Hi Michael,
Sorry for the late reply; I just returned from a trip to India.
> ... which reminds me - I have an SBus card with ( among others ) an
> I128. I wrote an accelerated kernel driver for NetBSD using the X
> driver
> From: Adam Jackson
> Date: Tue, 13 Oct 2009 14:51:26 -0400
>
> On Fri, 2009-10-09 at 11:26 +0200, Mark Kettenis wrote:
>
> > > Hmm, right. The two hunks above were aimed towards my first approach f=
> or
> > > fixing radeon KMS on big endian machines, by making the root window
> > > visual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On Oct 27, 2009, at 5:54 PM, Mark Kettenis wrote:
> (--) PCI: (0:0:3:0) 105d:2339:105d:000b Number 9 Imagine-128 II rev
> 2, Mem @ 0x0200/8388608, 0x0280/8388608, 0x0300/8388608,
> 0x0380/8388608, 0x0016/65536, I/O @ 0x0
On Tue, 2009-10-27 at 22:54 +0100, Mark Kettenis wrote:
> Hi Adam,
>
> See the log below. This is the Xorg version that's currently in the
> OpenBSD tree, with some modifications to the xf86-video-i128 driver
> such that it doesn't blow up.
>
> (--) PCI: (0:0:3:0) 105d:2339:105d:000b Number 9
> From: Adam Jackson
> Date: Wed, 28 Oct 2009 10:39:29 -0400
>
> > (--) PCI: (0:0:3:0) 105d:2339:105d:000b Number 9 Imagine-128 II rev 2,
> > Mem @ 0x0200/8388608, 0x0280/8388608, 0x0300/8388608,
> > 0x0380/8388608, 0x0016/65536, I/O @ 0x0600/256, BIOS @
> > 0x/327
On Thu, 2009-10-29 at 22:26 +0100, Mark Kettenis wrote:
> Excellent! After initializing MW0_CTRL to 0x0006, it seems things
> just work. I'll prepare a proper diff to do that on big-endian machines.
Very cool.
> To make the card work properly I still have to solve two issues:
>
> 1. It se
> From: Adam Jackson
> Date: Thu, 29 Oct 2009 18:33:20 -0400
>
> > To make the card work properly I still have to solve two issues:
> >=20
> > 1. It seems the ACNTRL register doesn't exist on the i128v2 chip.
> >Writes to this register result in a PCI bus error. This was
> >probably neve
Hello,
On Oct 31, 2009, at 11:17 AM, Mark Kettenis wrote:
> Still struggling a bit with how to map BAR 5 though. I have a hack to
> make things work, but I'll need to discuss the implications for the
> OpenBSD kernel and libpciaccess.
Assuming that OpenBSD is still more or less NetBSD-ish here
On Sat, 2009-10-31 at 16:17 +0100, Mark Kettenis wrote:
> > It might. BAR 5 is the I/O map, and it's 256 bytes. They're all
> > defined right up to 0xBC, which smells a little suspicious since the VGA
> > ports it claims to decode are 3C[0-5ACEF] and 3[BD][45A]. So while it
> > doesn't _say_ th
15 matches
Mail list logo
