check the xfree86 or xorg devel mailing lists. Someone posted a patch
for i8xx rotation (no accel, using shadowfb).
Alex
On Wed, 14 Jul 2004 11:52:42 +0530, NaggarajaVignesh.R
<[EMAIL PROTECTED]> wrote:
> Hi
>
> Iam trying to Rotate the Screen 90 in Red Hat Linux 9.0 with System
> Configurati
At long last I've gotten duoview (dualhead) working with my savage IX!
It should also work on MX and Supersavage chips, but I don't have the
hardware to test. My current code is a bit of a hack, basically just 2
viewports into a big framebuffer. There are no safeguards in the code
at the moment.
Post you patches on either xfree86 or xorg bugzilla and we can take a
look at integrating them. FWIW, the new intel DDX code drop in cvs
includes full multi-head support. I'm not sure how that affects your
patches.
Alex
On Sun, 25 Jul 2004 15:09:18 +0200, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> w
On Thu, 23 Sep 2004 18:12:31 +0100 (BST), Andrew C Aitchison
<[EMAIL PROTECTED]> wrote:
> On Thu, 23 Sep 2004, Klaus Dittrich wrote:
>
> > I put all noDDC options in the server flags and in both
> > monitor options as well.
> > But nothing helped, the hangs still happen.
> >
> > According to the l
On Thu, 23 Sep 2004 12:45:17 -0500 (CDT), Huver <[EMAIL PROTECTED]> wrote:
> Alex Deucher <[EMAIL PROTECTED]> writes:
> >
> > On Thu, 23 Sep 2004 18:12:31 +0100 (BST), Andrew C Aitchison
> > <[EMAIL PROTECTED]> wrote:
> >>
> >> I stil
On Fri, 19 Nov 2004 19:05:13 +0100, Måns Rullgård <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes:
>
> >> [EMAIL PROTECTED] writes:
> >>
> >>> Hi,
> >>>
> >>> Where I can find the documentation about developing video driver
> >>> for XFree?? I'll need to develop one to a new card we working
On Wed, 19 Jan 2005 16:32:44 +0100, Grand Apeiron <[EMAIL PROTECTED]> wrote:
> Hi,
>
> i've just noted that the XFree86 radeon driver does not support DRI
> (at least not for 9500/9700 series and i have a 9550).
> I've also tried the ATI proprietary driver but giving up after it didn't
> work righ
On Wed, 19 Jan 2005 17:33:41 +0100, Grand Apeiron <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-01-19 at 10:58 -0500, Alex Deucher wrote:
> > there is experimental r300/r400 support going on here:
> > http://r300.sf.net
> > Note, at the moment there is no support wit
On Tue, 8 Feb 2005 18:40:07 -0500, David Dawes <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 08, 2005 at 11:24:43PM +, Alan Hourihane wrote:
> >On Tue, Feb 08, 2005 at 06:17:50PM -0500, David Dawes wrote:
> >> On Tue, Feb 08, 2005 at 05:12:29PM +, Alan Hourihane wrote:
> >> >On Tue, Feb 08, 2005
On Thu, 10 Feb 2005 10:08:20 -, Charles Dobson <[EMAIL PROTECTED]> wrote:
> I am not sure if I should post this here or on bugzilla.
post your patch in bugzilla.
Thanks,
Alex
>
> While trying to get a Silicon Motion SM722 video controller
> working with Solaris, I have discovered a problem
On Fri, 18 Feb 2005 09:12:01 -0800, Bukie Mabayoje <[EMAIL PROTECTED]> wrote:
>
> Read my comments in blue. And I am still looking into this.
>
> Nqnsome wrote:
> Hi,
>
> Can someone help me, please!?
>
> I have a Compal CY27 laptop. The graphics chipset is (as reported by lspci):
>
> 0
On Fri, 18 Feb 2005 17:03:33 -0300, SLCB <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks a lot for replying, really!
>
> > The 82852GM supports two independent display. You have one at 00:02:.0
> > and the other at 00:02.1. You are configured to use BusID
> > "PCI:0:2:0". I am not sure which video po
On Fri, 18 Feb 2005 17:13:17 -0300, SLCB <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Sorry, I forgot to comment one answer.
>
> Bukie Mabayoje wrote:
>
> > I suspect the reason it works is that your system have two graphics
> > controller. And one of it is the 350Mhz 24-bit RAMDAC that support a
> > re
On Fri, 18 Feb 2005 12:02:37 -0800, Bukie Mabayoje <[EMAIL PROTECTED]> wrote:
>
>
> Alex Deucher wrote:
>
> > On Fri, 18 Feb 2005 17:03:33 -0300, SLCB <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > Thanks a lot for replying, really!
&
On Fri, 18 Feb 2005 18:15:16 -0300, Nqnsome <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks again.
>
> Alex Deucher wrote:
>
> >>Alex is correct. Let focus on the primary display controller on PCI:0:2:0
> >>with Display Pipe A and Display Pipe B.
> &
On 5/4/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > On Tue, May 03, 2005 at 05:18:28PM -0700, Tim Roberts wrote:
> >> [EMAIL PROTECTED] wrote:
> >>
> >> >devel@XFree86.Org
> >> >Hi I am trying to get XFree running on this configuration butno success
> >> so
> >> >far. It looks likevsomethin
On 6/1/05, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> * Stuart Anderson <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> > I just wanted to make sure you were aware of the similar work
> > that has been underway for several months. Details can be found at
> >
> > http://xorg.freedesktop.org/wi
On 10/16/05, Michael <[EMAIL PROTECTED]> wrote:
> Hello,
>
> > > since the sunffb driver doesn't support the XRender extension but
> > > the graphics processor supports alpha blending and a few other nice
> > > tricks I've been poking around a bit to add this sort of
> > > functionality. The proble
On 10/19/05, Rick Knight <[EMAIL PROTECTED]> wrote:
> I've done some more testing and the problem seems to actually be with
> KDE. If I start Xorg in failsafe mode and scan in the Xterm window, I
> can see the Cuecat's output. Also, if I open an xterm in KDE, not a KDE
> term, I can still scan. It
On 11/16/05, Smoof . <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am writing an application that will display up to 9 independent video
> streams (each stream is 320 x 240). I'm new to Xv and may not be using the
> correct terminology so please bear with me. I have tried two approaches:
>
> The firs
On 11/16/05, Smoof . <[EMAIL PROTECTED]> wrote:
> >Smoof . wrote:
> >
> >>
> >>My plan was to do all the rendering with the same client and I know that
> >>my overlay adaptor only has a single port for the YUV420 format that I am
> >>using. Can someone say if the following would be possible:
> >>
If you have a monitor that is natively portrait or will support a
portrait mode, then you can just define a 768x1024 modeline and
assuming the driver doesn't rely on the bios (since I doubt any bios
will have a mode like that defined) it will set the mode. However, if
the monitor you are trying to
On 11/28/05, Barry Scott <[EMAIL PROTECTED]> wrote:
> I'm seeing this error when I attempt to play a HD 720p (1280x720) movie
> in Xine:
>
> X Error of failed request: BadAlloc (insufficient resources for operation)
> Major opcode of failed request: 143 (XVideo)
> Minor opcode of failed reque
On 2/6/06, Kaliraj Kalaichelvan - CTD, Chennai <[EMAIL PROTECTED]> wrote:
> I am using XFree86 Version 4.3.0. I understand from driver folder
> (\xc\programs\Xserver\hw\xfree86\drivers\siliconmotion)that silicon motion
> driver supports for SM720, SM910, SM810, SM820, SM710, SM712. Does this same
>
helvan
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Alex Deucher
> Sent: Wednesday, February 08, 2006 2:55 AM
> To: devel@xfree86.org
> Subject: Re: SM501 driver support in XFree86
>
>
> On 2/6/06, Kaliraj Kalai
On 6/12/06, Barry Scott <[EMAIL PROTECTED]> wrote:
Barry Scott wrote:
> Using the Xfree86 4.6.0 i810 driver I'm seeing a problem with sync
> polarity setting.
>
> This modeline is required for 1280x768 mode:
>
> Modeline "1280x768" 79.30 1280 1335 1473 1665 768 769 772 793
> -hsync +vsync
>
>
On 6/13/06, Barry Scott <[EMAIL PROTECTED]> wrote:
Tim Roberts wrote:
> Barry Scott wrote:
>
>
>> Using the Xfree86 4.6.0 i810 driver I'm seeing a problem with sync
>> polarity setting.
>>
>> This modeline is required for 1280x768 mode:
>>
>> Modeline "1280x768" 79.30 1280 1335 1473 1665 768
On 6/14/06, Barry Scott <[EMAIL PROTECTED]> wrote:
Alex Deucher wrote:
>
> The i810 driver is limited to the modes the bios knows how to set. If
> the bios doesn't have the specific mode you are lookign for, then you
> are out of luck. There is native modesetting supp
On 10/5/06, jf simon <[EMAIL PROTECTED]> wrote:
Hi,
I am trying to use the x86emu code to emulate a PCI ATI Radeon
VGA bios on a powerpc platform (IBM 970 Maple).
The emulation starts OK, but after some time I can see that it is
making a call to a location that is outside of the VGA bios.
Which c
On 3/8/07, bruno schwander <[EMAIL PROTECTED]> wrote:
ah never mind. since this is interlaced, the pixel clock needs to be half
that to get the right frame refresh rate (60Hz) with a pixel clock of
12.22MHz, it passes.
Now, I am not sure if the pixel clock is effectively set to that, and my
lcd
->Clock. I have a similar patch in my xorg
smi tree.
Alex
bruno
On Thu, 8 Mar 2007, bruno schwander wrote:
> On Thu, 8 Mar 2007, Alex Deucher wrote:
>
>> The siliconmotion driver doesn't explicitly set the vclk pll. It uses
>> the bios (if UseBIOS is set or does
On 3/9/07, bruno schwander <[EMAIL PROTECTED]> wrote:
On Fri, 9 Mar 2007, Alex Deucher wrote:
> On 3/9/07, bruno schwander <[EMAIL PROTECTED]> wrote:
>> so I gather now that actually I should leave the xf86SetCrtcForModes()
>> alone, and just add setting the c
On 3/9/07, bruno schwander <[EMAIL PROTECTED]> wrote:
On Fri, 9 Mar 2007, Alex Deucher wrote:
> The latest version of the siliconmotion driver in xorg git head should
> have the lockup fix you need. The problem is the engine doesn't need
> to be synced until it has been
On 3/10/07, bruno schwander <[EMAIL PROTECTED]> wrote:
I looked at that diff and it looks like what I added, except that I also
set bits 7:6 of CCR68 to 01 because the doc I have says that will select
VCLK from the programmable VCLK regs, CCR6C and CCR6D.
Right, I should probably do that explic
On 3/10/07, bruno schwander <[EMAIL PROTECTED]> wrote:
in SMI_Save(), SR6C and SR6D (and SR68) are saved only if pSmi->Dualhead,
why ? seems it should always be done ?
It should. Like I said this is still my untested local working tree.
I'm aiming to add xrandr 1.2 support as well.
in SMI_W
On 3/10/07, bruno schwander <[EMAIL PROTECTED]> wrote:
I looked at that diff and it looks like what I added, except that I also
set bits 7:6 of CCR68 to 01 because the doc I have says that will select
VCLK from the programmable VCLK regs, CCR6C and CCR6D.
I fixed the vclk problem. The postsca
K = 14.31818 Mhz * (VNR/VDR) * (1/(1 + PS))
VNR being SR6C and VDR and SR6D. PS is bit 7 of SR6D.
I hope this helps.
Alex
bruno
On Sun, 11 Mar 2007, Alex Deucher wrote:
> On 3/10/07, bruno schwander <[EMAIL PROTECTED]> wrote:
>> I looked at that diff and it looks like what I added,
On 3/13/07, bruno schwander <[EMAIL PROTECTED]> wrote:
On Mon, 12 Mar 2007, Alex Deucher wrote:
> On 3/12/07, bruno schwander <[EMAIL PROTECTED]> wrote:
>> I used your vclk setting code as in smi_driver.c, and changed the shift
>> in SMI_CommonCalcClock() but
On 4/6/07, SciFi <[EMAIL PROTECTED]> wrote:
Yves' changes did not help getting stuck several times during the
build here. I'll be documenting as best I can and send 'em thru
bugzilla. I bet we'll be too late for Apple to put this into
Leopard, I have no idea what they're doing since I can't af
On 4/11/07, SciFi <[EMAIL PROTECTED]> wrote:
On Fri 06 Apr 2007 14:01:59 -0400,
Alex Deucher wrote:
> On 4/6/07, SciFi <[EMAIL PROTECTED]> wrote:
>>
>> Yves' changes did not help getting stuck several times during
>> the build here. I'll be doc
On Nov 26, 2007 8:08 PM, Bankim Bhavsar <[EMAIL PROTECTED]> wrote:
> I'm implementing Xv extension of linux X driver.
>
> I need to use offscreen memory to allocate space for incoming video-frames.
> Currently, I am using xf86InitFBManager() part of xf86fbman.h to
> initialize offscreen memory by s
On Tue, Mar 4, 2008 at 5:34 PM, Michael Lorenz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
>
> On Mar 4, 2008, at 15:37, Marc Aurele La France wrote:
>
> > On Mon, 3 Mar 2008, Michael Lorenz wrote:
> >
> >> I noticed the following - XAACopyArea() o
On Thu, Mar 6, 2008 at 2:00 PM, Michael Lorenz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> On Mar 5, 2008, at 19:06, Alex Deucher wrote:
>
> > On Tue, Mar 4, 2008 at 5:34 PM, Michael Lorenz
> > <[EMA
On Thu, Mar 6, 2008 at 2:58 PM, Michael Lorenz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> On Mar 6, 2008, at 14:12, Alex Deucher wrote:
>
> > On Thu, Mar 6, 2008 at 2:00 PM, Michael Lorenz
> > <[EMA
On Thu, Mar 6, 2008 at 2:58 PM, Michael Lorenz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> On Mar 6, 2008, at 14:12, Alex Deucher wrote:
>
> > On Thu, Mar 6, 2008 at 2:00 PM, Michael Lorenz
> > <[EMA
On Thu, Mar 6, 2008 at 4:26 PM, Michael Lorenz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
>
>
> On Mar 6, 2008, at 15:58, Alex Deucher wrote:
>
> > On Thu, Mar 6, 2008 at 2:58 PM, Michael Lorenz
> > &l
On Thu, Mar 6, 2008 at 5:17 PM, Michael Lorenz <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> On Mar 6, 2008, at 16:40, Alex Deucher wrote:
>
> > On Thu, Mar 6, 2008 at 4:26 PM, Michael Lorenz
> > <[EMAIL P
I'm trying to add duoview support (dual head -- 2 crtcs, one chip) to
the savage driver, but I keep getting "entity already in use" errors.
I've studied the mga and radeon code thoroughly and I've read the
DESIGN guide, and I think I have a pretty good understanding of what
need to be done, but fo
I'm using 1.1.26, on my savage IX (IBM T20) and it works fine. I'm
using it as the basis for the duoview support I'm adding.
Alex
--- "Mike A. Harris" <[EMAIL PROTECTED]> wrote:
> On 21 Feb 2003, Juliusz Chroboczek wrote:
>
> >Oh, and what about the Savage changes? XFree86 no longer crashes
>
I believe Zephaniah E. Hull was doing some work for getting xfree86 to
work dynamically with the 2.5 input layer. I think it was called
evdev. I can't seem to find the link to his site at the moment though.
Alex
--- "Charl P. Botha" <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 28, 2003 at 10:54:17
Send your patches to [EMAIL PROTECTED] and/or [EMAIL PROTECTED] for
inclusion in a future release.
Alex
--- Sven Goethel <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> dear xfree developers,
>
> i have added xfree86 _server_ support for
> qnx neutrino 6.2 !
>
Jonathan,
could you also post your XF86Config file? I have some ideas on how
to extend this. It's still kind of a hack, but here goes:
add an option to the radeon driver, say "MergedFB" or something like
that. when that option is set to TRUE, it would skip the sections of
code that you have
send it to [EMAIL PROTECTED] and/or [EMAIL PROTECTED]
Alex
--- [EMAIL PROTECTED] wrote:
> ...
> > > Now it works for me.
> >
> > Thanks,
> >
> > I've committed your fix to the CVS.
>
>
> Quick question -- I posed a patch to
> xc/programs/Xserver/hw/xfree86/os-support/bsd/alpha_video.c on Monday
also check out GATOS -- http://gatos.sf.net
Alex
--- Olivier Chapuis <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 09, 2003 at 04:21:52PM +0100, Aleksandar Simonovski
> wrote:
> > is tv-out supported with ati radeon 9000 on xfree 4.3
> >
>
> I do not think so. However, there is a tool named "atitvou
the v4l driver interfaces with the kernel v4l drivers. I believe that
driver uses some linux includes. There my be an "X" way of doing
socket ops though...
Alex
--- Paul Evans <[EMAIL PROTECTED]> wrote:
> I'm (still) writing an output driver for a network attached device.
> My
> question of the
I'm not too familiar with the neomagic cards, but the hardware "mpeg"
acceleration may have just referred to the HW color space conversion of
the Xvideo interface. If the chip had motion compensation or iDCT
capabilities, I doubt those will ever be supported since no one has
docs to the chip and n
does Xvideo work if you remove the panning check? if so i don't see
why we couldn't remove it. I'll try and check on my savage IX tonight
or tomorrow.
Alex
--- Billy Biggs <[EMAIL PROTECTED]> wrote:
> On startup, the savage driver protects its call to initialize its
> XVideo code like this (s
It shouldn't be a problem although you may have to generate your own
modeline, since it's a non-standard one.
try one of these sites to generate a modeline:
http://xtiming.sourceforge.net/cgi-bin/xtiming.pl
http://koala.ilog.fr/cgi-bin/nph-colas-modelines
Alex
--- Mark Cuss <[EMAIL PROTECTED]>
You could do it that way. You might want to look at the dri project
(http://dri.sf.net) though. That way you can get an idea of how X
talks to the kernel driver and such as well as make your driver
consistant with the rest of the open source drivers out there. You can
also use the DRI code from
what's the status of S3/sonicblue/VIA? who owns what? I'd really like
to get savage mx/ix specs, but I fear that possiblity is slipping away
:(
Alex
--- Alexander Stohr <[EMAIL PROTECTED]> wrote:
> Hmm, SonicBlue (aka known as S3) has claimed
> bankrupcy (Chapter 11) recently, so its a changing
hecked. They had docs available as
> long
> as you were willing to sign an NDA. The NDA allows source code
> release,
> so is compatible with XFree86 development.
>
> --
> Kevin
>
>
> Alex Deucher wrote:
> >
> >
> > what's the status of S3/soni
Do you think I could still get savage mx/ix docs? perhaps if the old
stuff is orphaned, they will lift the NDAs on the docs? not likey I
suspect. I really want to finish duoview support. At this point I
think I might be better off just onloading my savage laptop and getting
a laptop with an ati
the standard r128 driver should work for this chipset. the M4 is r128
based.
Alex
--- [EMAIL PROTECTED] wrote:
> I have a Dell Inspiron 8000(laptop) 1Ghz
> 128MB
> ATI M4 graphics card
>
>
>
> I am having a strange problem.
>
> I believe that this problem is with XFree86 and it's consistenc
Sis wrote support for the 300 series and it works. However, when mesa
4.x came out no one ever updated the sis dri stuff to match the new
structure. so DRI works with the 300 if you use the mesa 3.x libs. It
shouldn't be too hard to port the sis stuff to mesa 4.x, but there
doesn't seem to be mu
actually I believe the t30 has a full fledged mobility radeon 7500 on
board. regardless, the issue seems to be that the max res supported by
the DVI port is 1280x1024. running the port at 1200x1600 is beyond the
specs (and not supported). I don't really see this as a problem. if
you run at 1200
I suspect it was not designed to handle the bandwidth needed for
1600x1200. DVI may be the future, but the ports are limited by the
transmitters driving them, just as CRT ports are limited by the RAMDAC.
As 1600x1200 LCDs become more popular, I'm sure you'll see the
capabilities of DVI ports incr
There are some hacks to accomplish this, but I don't think there's
really an elegant way to do this in the current architecture. Xfree86
5 should address this.
Alex
--- Robert Woerle <[EMAIL PROTECTED]> wrote:
> Hi
>
> I did make a touchscreen driver for a Tablet PC .
> I also have a calibratio
I believe the wacom driver is a good starting point.
Alex
--- Marco Lazzarotto <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have to write a driver for the ronics touchscreen.
> Since the sample driver is outdated (in the 4.3.0 source
> tree,almost),
> where do I find a good starting point to do it?
>
I'm working on integrating my radeon mergedfb code with xfree86 cvs.
so far it's working, but now I'm trying to integrate the current clone
code with the mergedfb clone mode. so far so good. I'm trying to use
the modes defined for the 1st head as clone modes for the second head
in the even that
Now that 4.3.0 is out, what is the status of xfixes? I'd like to see
it included again for 4.4.0 or 5 or whatever the next release will be.
it fixed some annying behavior in X. if not xfixes, what about another
extension offering similar functionality?
Thoughts?
Alex
If that's the case then's what's the best way to iterate through the
mode list without getting stuck in an endless loop? It's probably
somehting simple, but it's just not coming to me...
Alex
--- Dr Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
>
> I have only looked at this code briefly and lo
yeah, that's the way to do it... I feel like an idiot... it's been too
long since my old CS classes...
Thanks to all who replied,
Alex
--- Sven Luther <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2003 at 08:24:31AM -0700, Alex Deucher wrote:
> > If that's the case
BTW, bugzilla reference for this feature is here:
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=276
Please test and post any comments or issues.
Thanks,
Alex
---
The attached patch adds mergedfb support (a single framebuffer with two
viewports looking into
Just curious, as I'm not too familiar with XvMC yet, but would this
provide another Xv adapter that used the 3D texture engine to display
videos rather than othe video overlay? or something else. Sorry for
my ignorance.
Thanks,
Alex
--- Mark Vojkovich <[EMAIL PROTECTED]> wrote:
>I'd like t
thanks, I got it working. The working patch against CVS in up on
bugzilla:
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=276
Alex
--- Egbert Eich <[EMAIL PROTECTED]> wrote:
> Alex Deucher writes:
> > I'm working on integrating my radeon mergedfb code with xfr
ri.shtml
Alex
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > Sis wrote support for the 300 series and it works. However, when
> mesa
> > 4.x came out no one ever updated the sis dri stuff to match the new
> > structure. so DRI works with the 300
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
>
> I certainly wouldn't buy one to replace my Radeon 8500! :) It would
> be
> exclusively to update the drive. It's the same reason I would be a
> Gamma card w/an R2 rasterizer...too bad there are *none* on eBay.
> After
> I realized that, I prett
--- Wouter Bijlsma <[EMAIL PROTECTED]> wrote:
>
> It's a pity the DRI folks don't have access to the hardware. I do.
> But I'm not a driver developer (though I'm quite skilled in C,
> assembler and graphics code). Would it be a bad thing for me to try
> and find out if the existing 7000 driver can
there are alot of issues with dualhead and LCDs on PPC. I believe the
fix is to use fbdev, but I'm not sure anyone has gotten dualhead to
work yet. check the archives from last month.
Alex
--- "Andreakis, Dean (MED)" <[EMAIL PROTECTED]> wrote:
> I am trying to enable dual independent heads on m
I had this problem as well at one point when I was messing with the
savage driver. What was weird was I hadn't messed with any of the vbe
stuff. I think it ended up being a bad pointer reference or something
like that. also, if you are attempting to mess with programming
dualhead, you need to tu
this is from the DRI (front, back, and depth buffers) not the 2D driver
I think.
Alex
--- "Andreakis, Dean (MED)" <[EMAIL PROTECTED]> wrote:
>
> (WW) RADEON (0): Static buffer allocation failed -- need at least
> 9216
> kB video memory
> (II) RADEON (0): Memory manager initialzed to (0,0) (10124
ges in the XF86 log file. Maybe I need to do something else to
> stop
> DRI from trying to load...
>
> thx,
>
> -dean andreakis
>
> On Fri, 2003-06-13 at 14:47, Alex Deucher wrote:
> > this is from the DRI (front, back, and depth buffers) not the 2D
> driver
>
The attached patch adds mergedfb support (a single framebuffer with two
viewports looking into it) to the radeon driver. the options are
consistant with the sis and mga drivers. I've also replaced the old
clone mode with the clone mode supplied by the mergedfb code. It's
behavior follows that of
unfortunately, you have the two chips for which you are least likely to
find documentation. the neomagic driver was written for XF 3.3 under a
special agreement with neomagic. the driver was originally binary
only, but eventually the source was released. Neomagic no longer makes
graphics chips.
You can download the chips databooks right off their web site. although
it might be hard finding a card (must chips chips are in latops). I've
heard 3dlabs is also good about giving out docs. Matrox cards prior to
the parhelia are also well supported and you can download the databooks
from matrox
I'm not sure Xinput really supports this sort of functionality right
now. Support for this may be something for 5.0.
Alex
--- Divide by Zero <[EMAIL PROTECTED]> wrote:
> On Tuesday 24 of June 2003 23:16, Brad Hards wrote:
> > On Wed, 25 Jun 2003 00:34 am, Divide by Zero wrote:
> > > I'm trying t
perhaps you could write a kernel driver and wrap it with an X driver
(although you'd lose multiplatform capabilities). I'm not that
familiar with XInput.
Alex
--- Divide by Zero <[EMAIL PROTECTED]> wrote:
> On Wednesday 25 of June 2003 05:39, Alex Deucher wrote:
> > I
I just saw this on extremetech today:
http://www.extremetech.com/article2/0,3973,1101038,00.asp
Looks like SiS is spinning off it's graphics chip division. perhaps
this could mean better access to databooks!
time will tell I suppose.
Alex
__
Do you Yahoo!?
SBC
there is a work around for root window file managers like nautilus or
KDE in xsnow and xpenguins. you might also want to check the nautilus
source or gnome source for the root window code, or ask on one of the
gnome lists.
Alex
--- Daniel Godas Lopez <[EMAIL PROTECTED]> wrote:
> i have made a pr
try your query on Nautilus-devel (http://www.gnome.org). one of the
nautilus developers should be able to answer your question.
Alex
--- Daniel Godas Lopez <[EMAIL PROTECTED]> wrote:
> i have been trying to paint on the root window, i am using an include
> file (vroot.h) that defines a function
why aren't the windows drivers affected? they must be a way around it
without needing a new bios... The same thing was claimed the last time
around with the 830s and dell never fixed the bios, but someone came up
with a work around.
Alex
--- Hope Merritt <[EMAIL PROTECTED]> wrote:
> All,
>
> T
well, yeah.
My point was that intel should just release a patch to fix the driver
(or specs to let us fix it) rather than "fixing" the bios and making us
wait for dell to (possibly) update the bios.
Alex
--- "Mike A. Harris" <[EMAIL PROTECTED]> wrote:
>
> Simple. Because the Windows drivers
it's also needed for mergedfb support on mga, although it could
probably be rewritten to not use HAL.
Alex
--- Dr Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
> On Tue, 1 Jul 2003, Egbert Eich wrote:
>
> > Dr Andrew C Aitchison writes:
> > >
> > > 260. Disabled mode writeback to client prog
--- Egbert Eich <[EMAIL PROTECTED]> wrote:
>
> The truth is that we don't know what MGA HAL does exactly.
> It does a lot of initialization stuff when it is called in
> PreInit()(!)
> and it sets up video modes differently than the OpenSource code does.
> In some cases it does the wrong thing so I
the nv driver does not support dualhead. you need the nvidia binary.
Currently only mga, radeon, chips, and sis support dualhead on a single
card.
Alex
--- Kendall Bennett <[EMAIL PROTECTED]> wrote:
> Hi Guys!
>
> We are trying to figure out how to get Dual Head working on the
> NVIDIA NV
> dr
I don't suppose you can contribute your code back? I've sure someone
could get it working in due time.
Alex
--- Kendall Bennett <[EMAIL PROTECTED]> wrote:
> Mark Vojkovich <[EMAIL PROTECTED]> wrote:
>
> > > We are trying to figure out how to get Dual Head working on the
> NVIDIA NV
> > > drive
) ok.
Alex
--- Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
> On Wed, 2 Jul 2003, Alex Deucher wrote:
>
> > Actually you could probably replace the HAL functionality by using
> the
> > linux matrox framebuffer driver or directfb driver as a reference.
> it
> >
right now? not likely. Sis refuses to release the necessary databooks
needed to write a 3D driver. unless this changes, we'll probably be
out of luck.
Alex
--- Serdar Cevher <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I would like to know when SiS650 users could have the 3D support for
> the
> card o
open a bug at http://bugs.xfree86.org/ and include your patch so that
it doesn't get lost. hopefully it will get fixed up and integrated.
Alex
--- áÌÅËÓÅÊ_âÁÊ <[EMAIL PROTECTED]> wrote:
> With the attached trivial patch I forced these cards to work to some
> extent
> with XFree 4.3.0 ...
>
> On
I believe this patch was already applied to cvs (HEAD, don't know about
the branches) a while back.
Alex
--- Erik van het Hof <[EMAIL PROTECTED]> wrote:
> Please find below an email and patch by Rik Faith to make XTEST work
> with Xinerama. I have backported this to a 4.2.1 version on my debian
>
1 - 100 of 317 matches
Mail list logo
