Mathias,
you may want to post this on bugzilla (http://bugs.xfree86.org/) so
that it doesn't get lost. stuff posted there also seems to be included
in CVS more readily.
Alex
--- Mathias Fröhlich <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I have implemented a new feature for the mouse driver
I would love to see this patch applied. I've been using tpscroll
(http://rsim.cs.uiuc.edu/~sachs/tp-scroll/) to get this functionality
for years. it'd be nice to have it as part of xfree86.
Alex
--- Mathias Fröhlich <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I have implemented a new feature f
info on futexes:
http://ds9a.nl/futex-manpages/
I'm not real familiar with them.
Alex
--- Mark Vojkovich <[EMAIL PROTECTED]> wrote:
> On Tue, 23 Sep 2003, [iso-8859-1] emmanuel ALLAUD wrote:
>
> > This is perhaps a dumb idea, but could the futexes
> > help here? I don't know if they have equiv
be re-coded.
>
> Also, both trident and Sis have the linux driver, which is release
> with
> Linux OS, for almost all their own chips.
>
> -Original Message-
> From: Alex Deucher [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 15, 2003 5:30 PM
> To: T
I wonder how the new company will be with respect to giving out
datasheets? like sis or like trident?
Alex
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
> Russ Dill wrote:
> > On Mon, 2003-09-15 at 11:03, Alex Deucher wrote:
> >
> >>Is anyone on either of thes
Is anyone on either of these lists familiar with XGI? It seems to be a
new GPU manufacturer consisting of a merger of Trident and the SiS
graphics division.
here's their website:
http://www.xgitech.com/index.htm
They have some interesting products products (dual GPU solution). Some
of their oth
Does using the TMU for blitting work in conjunction with OpenGL? in
the xfree86 mga driver, there is an option (textured video) to use the
TMU as a YUV Xvideo interface, however, enabling that disabled the DRI.
I had thought about adding a textured video option to the radeon
driver (using the TMU
t;[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, 29 Aug 2003 00:31 am, Alex Deucher wrote:
> > The following cards have hw dualhead support, but no driver support
> for
> > it:
> > i830/845
> I'm interested in working
tell them to whine to ati to implement a psuedo-xinerama extension in
their driver. nvidia did it.
Alex
--- Billy Biggs <[EMAIL PROTECTED]> wrote:
> Thomas Winischhofer ([EMAIL PROTECTED]):
>
> > No idea what the ATI folks have done there... seems to be some sort
> of
> > mergedfb mode, too.
>
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
>
> > It appears that the ati firegl driver does not support xinerama
> when
> > using its "dualhead/mergedfb" mode. I'd be happy to add xinerama
> > support for ati
it would appear so.
--- Billy Biggs <[EMAIL PROTECTED]> wrote:
> Alex Deucher ([EMAIL PROTECTED]):
>
> > The radeon and Sis mergedfb drivers support their own internal
> > xinerama extension to provide hints to xinerama aware apps. They
> do
> > not use the
It appears that the ati firegl driver does not support xinerama when
using its "dualhead/mergedfb" mode. I'd be happy to add xinerama
support for ati's driver. just tell them to release the source ;)
I suppose as a work-around you could divide the width by 2 for modes
like 2048x768 or 2560x1024,
The radeon and Sis mergedfb drivers support their own internal xinerama
extension to provide hints to xinerama aware apps. They do not use the
regular Xinerama extension. the closed source nvidia driver does a
similar thing.
Alex
--- Billy Biggs <[EMAIL PROTECTED]> wrote:
> As a more speci
This is probably better asked on dri-devel (cc:ed).
--- Cheshire Cat Fish <[EMAIL PROTECTED]> wrote:
> I am investigating supporting DRI and OpenGL for the Silicon Motion
> driver.
> I'm new to both of those, so some of these may be newbie sounding
> questions.
>
> 1) I have the OpenGL code from
I was leaning that way myself...
Alex
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> >
> > Next, mergedfb...
> >
> > I've been thinking about creating generic xfree support functions
> to
> > replace the chipset
Dualhead...
Right now there is dualhead support for the following cards in xfree86:
radeon
matrox
sis
via
chips
3dlabs (Sven mentioned that he had this quasi-working on the newer
cards, although I don't know the state of his driver)
The following cards have hw dualhead support, but no driver supp
there is support for 3D on mach64 in the DRI CVS tree.
see here for more details:
http://www.retinalburn.net/linux/dri_status.html
binary snapshots are available here:
http://dri.sourceforge.net/snapshots/bleeding-edge/
Alex
--- mark dohl <[EMAIL PROTECTED]> wrote:
> hi,
> at the same time I re
A while back someone posted a patch on devel or xpert that fixed chips
for PPC. he was trying to make it work on an old powerbook. I'm not
sure if the patch ever made it into CVS or not. you might try the
archives. I think his patch was for an older chipset, maybe 6 or
something like that,
Open a bug on http://bugs.xfree86.org/
you can post a description, patches, and comments. Other users can try
your code, and when it's ready, one of the xfree86 developers can
commit it to the cvs tree.
Alex
--- Mark McLoughlin <[EMAIL PROTECTED]> wrote:
> Hey,
> I've done some work on por
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > How is DPI supposed to work if you have a virtual desktop larger
> than
> > the current mode? the current code seems to produce the wrong DPI.
>
> > xf86SetDpi() has the following code:
this is a semi-fix, but it still does not deal with monitors that have
different DPI. Perhaps this is something that needs to be looked at
for xfree 5.
Alex
--- Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Aug 2003, Alex Deucher wrote:
>
> > How is DPI suppo
I have two questions for you about the radeon driver.
the first relates to the CP and accel. I'm attempting to convert the
Xv code to use the CP. how do you check to find out if the driver is
using CP or MMIO accel? I considered using
info->directRenderingEnabled, but as far as I can see the
How is DPI supposed to work if you have a virtual desktop larger than
the current mode? the current code seems to produce the wrong DPI.
xf86SetDpi() has the following code:
if (pScrn->widthmm > 0) {
pScrn->xDpi =
(int)((double)pScrn->virtualX * MMPERINCH / pScrn->widthmm)
If I have time I may take a look at it. One thing I've noticed is that
Xv doesn't seem to work too well when I have a 3D app running.
Converting Xv to use the CP may help that.
Alex
--- Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Thu, 2003-08-14 at 17:45, Alex Deucher w
you might try xfree86 cvs and then use the
option "MonitorLayout" "LVDS, CRT"
I think I also recall hearing that apple wired the DACS differently
than most boards. I believe this is fixed in cvs.
Alex
--- "Andreakis, Dean (MED)" <[EMAIL PROTECTED]> wrote:
> I am utilizing MergedFB mode from A
If the CP is enabled for acceleration on the radeon, could I also use
it to issue Xv commands rather than using mmio? It looks like it
should be possible. I'd be willing to give it a try. would any sort
of special locking be required or can I just issue the commands to the
ring like the accel co
about toying with
it on radeon, but I don't know how to tickle the hardware to make it do
that...
Alex
--- Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> On Sun, 10 Aug 2003 19:57:31 -0700 (PDT) Alex Deucher
> <[EMAIL PROTECTED]> babbled:
>
> > I realize this probab
some mach64 mobility chips had a second crtc that was never supported.
same thing with rage 128. I'm not sure about the accel engine on
mach32, but I think mach64 is fairly well accelerated. If you want the
databooks, register as a developer with ATI and request them (be
patient). Also the old
this should be extended to video drivers as well allowing you to
dynamically adjust that. I believe THomas Winischofer has done
something simialr with his sisctl utility and the sis driver, although
I haven't really looked to closely at how that works yet.
Alex
--- "Bryan W. Headley" <[EMAIL PRO
You might want to create a bug in bugzilla (bugs.xfree86.org) and
attach the patches there. that way people can comment on the patches
and the committers usually post a comment there if they decide to
include it.
Alex
--- Warren Turkal <[EMAIL PROTECTED]> wrote:
> BTW, if I submit a patch t
I realize this probably isn't the preferred way to do it in the long
run, but there is a basic XTransparency (might be called XOpacity)
extension in the Xdirectfb cvs tree for setting the opacity level for
windows. there was even a patch for metacity (or maybe sawfish) posted
on the directfb devel
While I was working on mergedfb support for the radeon video overlay, I
happened upon and fixed a bug in the setting of ECP. in
RADEONAllocAdaptor() and RADEONDisplayVideo(), the current code looks
something like this:
if(info->ModeReg.dot_clock_freq < 17500)
ecp_div = 0;
else
rgedfb
support is pretty easy once you get regular pScrn based multi-head
working.
Alex
--- Tim Roberts <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Aug 2003 06:36:04 -0700 (PDT), Alex Deucher wrote:
> >
> >some mach64 mobility chips had a second crtc that was never
> suppor
--- Jon Smirl <[EMAIL PROTECTED]> wrote:
> Hopefully these is the last versions. They implement:
> 1) add every know PCI ID
> 2) access ROM directly instead of relying on copy in
> low RAM. This allows multiple cards. Required
> MPP_TB_CONFIG fix in driver.
Is this patch necessary for xfree86? It
--- Dr Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
>
> There is a GATOS project to add 3D to those mach64 chips which
> support 3D; it has never been merged into the XFree86 driver.
>
> Xv may or may not have made it into the mach64 driver too.
>
GATOS develops the Xv and video in/out featur
the Xv code is already in xfree86 cvs. The 3D code still has some
security issues that need to be worked out before it can be merged into
the the DRI CVS trunk. If it gets merged into the trunk, it will be
merged into xfree86 CVS when the two trees get periodically merged.
Alex
--- James Maddis
.
Alex
--- Jon Smirl <[EMAIL PROTECTED]> wrote:
> --- Alex Deucher <[EMAIL PROTECTED]> wrote:
> > > 2) access ROM directly instead of relying on copy
> > > in low RAM. This allows multiple cards. Required
> > > MPP_TB_CONFIG fix in driver.
> >
&
you could also create a desktop using OpenGL textures and polygons.
something like an Xnest server that uses openGL for windowing.
Alex
--- Alexander Block <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I want to post-process the output of an x-server. In detail I want to
> take e.g. the desktop view o
For those that are interested, I just wanted to mention that I've
posted new versions of my radeon mergedfb patch and my radeon
powermanagement patch. Please see bugzilla for more details. Binaries
and diffs are available on my website (listed on bugzilla).
Mergedfb:
http://bugs.xfree86.org/show
or use an empty pixmap for the old sytle cursors.
Alex
--- Matthew Allum <[EMAIL PROTECTED]> wrote:
> If you use XFree 4.3 with libxcursor, you can create a completely
> transparent cursor theme.
>
> -- Matthew
>
> on Wed, Aug 06, 2003 at 02:21:35PM +0800, tom wrote:
> > I want to hide t
>
> Unfortunately, KDM does not support RandR as it seems, so I have not
> tested this in reality yet.
>
> Thomas
>
> Thomas Winischhofer wrote:
> > Alex Deucher wrote:
> >
> >> I'd be interested in seeing your code once you have decided on a
>
e new code. Thanks for writing the code and preparing this
description.
Alex
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > I'd be interested in seeing your code once you have decided on a
> route,
> > so that I can update the radeon merg
I'd be interested in seeing your code once you have decided on a route,
so that I can update the radeon mergedfb driver.
Alex
--- Thomas Winischhofer <[EMAIL PROTECTED]> wrote:
>
> However, I am still interested in how the binary NVidia driver solves
>
> this logical puzzle. (I have changed my
These questions are about the linux kernel framebuffer drivers and
would probably be better answered on either the linux-kernel or
linux-fbdev mailing lists. This ML is for Xfree86 development.
Alex
--- "Mr. Mailing List" <[EMAIL PROTECTED]> wrote:
> I have laptop with 320m radeon. radeonfb did
gt; > On Fri, 1 Aug 2003 12:58:06 -0700 (PDT), Alex Deucher wrote:
> > >
> > >Does savage HW even support acceleration with rotation?
> >
> > The Savage hardware wouldn't know about it. That's the point here:
> I would
> > have to modify the driv
Does savage HW even support acceleration with rotation?
--- Tim Roberts <[EMAIL PROTECTED]> wrote:
> I've had a client ask me about changing the Savage driver to support
> acceleration while the screen is rotated. (Today, I just let
> ShadowFB handle
> rotation.)
>
> I presume there are other
>
>
> Also whatever this means, I have the feeling it's a big deal
> regarding
> the cle266, is this something I need to fix in BIOS?
>
> (WW) via(0): Failed to set up write-combining range
> (0xd800,0x200)
>
> Thanks all, for your help!
>
Does your kernel have support for MTRRs compi
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw renderer. It's in
the pipeline for future development by the DRI folks, but if it were
sponsored, it might happen
What about tungsten graphics or Providenza & Boekelheide, Inc. (Tim
Robert's company? Plus I'm sure there are other small development
companies that would be interested.
Alex
--- Mark Vojkovich <[EMAIL PROTECTED]> wrote:
> On Tue, 15 Jul 2003, Alex Deucher wrote:
>
This proposal comes up periodically on this and other xfree lists, but
never really goes anywhere. Why not raise money from the open source
community to fund open source driver development? everything from
revamping X (ie, speeding up the development of 5.0 features) to adding
a new Xfree86 3D dr
VIA/S3 released fully featured driver that it developed in house. they
were based on 4.2.0. VIA had previously released a 2D only driver for
the CLE266, which was integrated into xfree86 CVS. The released
drivers are available on Alan Cox's website:
http://www.linux.org.uk/~alan/S3.zip
http://w
also, just as a note, the new savage driver VIA/S3 released has Xvmc
support as well.
Alex
--- "Sottek, Matthew J" <[EMAIL PROTECTED]> wrote:
> XvMC is only implemented for i810/i815 class chips at this time.
> 830/845/855 chips share the same binary XFree driver but are not
> very similar in de
Anyone familiar with xvmc have any thoughts on this?
Alex
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com--- Begin Message ---
Hi List.
XvMC seems to be not much used as the mailing-list archive shows.
But since someone made a pa
it's actually Alan Cox's website :)
Alex
--- Alan Hourihane <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 11, 2003 at 05:20:16PM -0700, Tim Roberts wrote:
> > I've recently been made aware of the XFree86 Savage driver that VIA
> released
> > and is now available on Alan Hourihane's web site. This dr
several drivers support TV out but not all. I believe via, trident,
and savage have open source support for most tv out options. Matrox
provides binary support for the g400 (although you can get tv out
working with the linux frambuffer driver for all recent matrox cards),
as does nvidia. for ATI
ATI beat ya to it ;) Support for the 9800 and a few others as well as a
few other fixes were added to CVS last week.
Alex
--- Markus Bäurle <[EMAIL PROTECTED]> wrote:
> Hello everybody,
>
> I hacked XFree86 4.3.0 to recognize my ATI Radeon 9800 Pro card. I
> added a new
> chip type ATI_CHIP_R35
I think there is already accel support for 69030 including dualhead
support in xfree86.
Alex
--- Rob Taylor <[EMAIL PROTECTED]> wrote:
> MessageIt appears i'm lying and the accellerated X driver is no
> longer on
> said page. The framebuffer driver thats required for the acceleretd
> friver
> to
send a patch to [EMAIL PROTECTED]
Alex
--- Rob Taylor <[EMAIL PROTECTED]> wrote:
> Messageumm, there already exits a working accelerated driver for the
> 69030,
> see http://www.humboldt.co.uk/. i also have a port of this to 4.2.0
> that i
> can email you if you want.
>
> relatedly, what would b
I just saw this on VIA's website. It looks like they just took Alan's
code and added some tv features (or perhaps just re-released his
code?). I don't know if there are already in CVS or not, but for what
it's worth here's the link:
http://www.viaarena.com/?PageID=296
http://downloads.viaarena.co
Plus most users will be on some un*x anyway. Also users generally
don't have a problem with .html vs .htm and .jpeg vs .jpg, at least in
my experience.
Alex
--- "Peter \"Firefly\" Lund" <[EMAIL PROTECTED]> wrote:
> On Thu, 10 Jul 2003, Alex Deucher wrote:
I prefer .sfnt as well. we shouldn't feel limited by DOS.
Just my 2 cents...
Alex
--- Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
> On 10 Jul 2003, Juliusz Chroboczek wrote:
>
> > I need to pick an extension for the bitmap-only SFNT fonts[1].
> While
> > these fonts use the same file format
I believe all it supports right now with the standard xfree86 drivers
is framebuffer resizing. the kdrive servers support more xrandr
options.
Alex
--- Andrew C Aitchison <[EMAIL PROTECTED]> wrote:
> On Tue, 8 Jul 2003, Jesper Tiberg wrote:
>
> > Hello!
> > I just bought a ViewSonic TFT-monitor
some drivers offer a rotate option, however there is no HW acceleration
when this is used.
Alex
--- Jesper Tiberg <[EMAIL PROTECTED]> wrote:
> Hello!
> I just bought a ViewSonic TFT-monitor (VP171b) with the pivot
> function
> the ability to flip the display 90 degrees) and I wonder if there is
what do you mean by structure? docs about the APIs, features, and
drivers are here:
http://www.xfree86.org/4.3.0/
in the source tree,
2D drivers live in xc/programs/Xserver/hw/xfree86/drivers/
3D and mesa live in xc/lib/GL/mesa/
Alex
--- "Si, Tom (˾½Æ½ IES)" <[EMAIL PROTECTED]> wrote:
> Hi,
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
>
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
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
) 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
> >
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
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
--- 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
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
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
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
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
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
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
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'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
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
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.
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
>
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
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
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
--- 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
--- 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
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
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
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
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
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
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
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
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
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
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?
>
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 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
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
201 - 300 of 317 matches
Mail list logo
