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:17AM
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 !
this
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
which makes X
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 atitvout
(do a
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
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
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/sonicblue/VIA? who owns what? I'd really
like
to get savage mx/ix specs, but I fear
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 consistency
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
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 to
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 if you use the mesa 3.x libs.
It
shouldn't be too hard to port the sis stuff
--- 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 pretty much
--- 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 be
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 my
,
-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
I think.
Alex
--- Andreakis, Dean (MED) [EMAIL PROTECTED] wrote:
(WW) RADEON (0): Static buffer allocation failed -- need at least
9216
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 to
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
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 to
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,
The
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 have
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 program from
--- 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 had to
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
driver that is
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
exposes just about all the functionality of the Gxxx driver (tv
out
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 ...
Only
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
box
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, All
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
or
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
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 as
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
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
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 work
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_R350, but
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---BeginMessage---
Hi List.
XvMC seems to be not much used as the mailing-list archive shows.
But since someone made a
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
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
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
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
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 drivers
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 compiled in?
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 didn't
. 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 mergedfb driver.
Alex, the code is now available on my
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 the cursor
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:
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 of any
--- 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 features of
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 to
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
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
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 Alex D.
--- 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:
if (pScrn-widthmm 0
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
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 read
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 specific ones for mergedfb. This would make it
easier to add
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
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
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.
Is this patch necessary for xfree86? It may address
some of the issues
in the email threads I
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
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,
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 regular Xinerama extension. the closed source
--- 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's driver. just tell them to release the source ;)
Hm, I don't
] 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 on this, even if it is just to control the
second
output (ie to make
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
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: Thomas Winischhofer; [EMAIL PROTECTED]
Cc: Alex Deucher; [EMAIL PROTECTED]; [EMAIL PROTECTED
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 equivalent
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 for
This is somewhat off topic, but as I recall someone posted a patch to
use the linux event input interface to support hotplugging in xfree86.
it may be of use with what you are looking at now...or not.
Alex
--- Juliusz Chroboczek [EMAIL PROTECTED] wrote:
JG So I'd just open the device and see
you might check to make sure your message made it to the list. I've
posted some questions on linux-kernel and they never got through.
Alex
--- Emmanuel Allaud [EMAIL PROTECTED] wrote:
/I did not have news from my request on linux-kernel, but I came
across
this interview of Rusty Russel
what do you mean by on demand? in non-xinerama multihead you can
run apps on either head by specifying a display like you did below.
the cursor and keyboard inupt can move between heads based on their
relationship, but that apps stay on the head they were started on. if
you want to drag apps
for the confusion.
-Original Message-
From: Alex Deucher [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 4:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Multihead support
what do you mean by on demand? in non-xinerama multihead you can
run apps on either head by specifying
you can configure that heads however you want. if you don't want to
use two of the heads, don't include them in your config. then set up
the arrangemet of the other heads as you like.
Alex
--- [EMAIL PROTECTED] wrote:
I have five monitors on a system and one keyboard/mouse.
Can I configure
-- Oorspronkelijk bericht --
From: Alex Deucher [EMAIL PROTECTED]
Subject: Re: Multiple monitors
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Date: Tue, 7 Oct 2003 06:46:34 -0700 (PDT)
you can configure that heads however you want. if you don't want to
use two of the heads, don't include them
I believe Gerd Knorr wrote the v4l module. you might want to ask him.
Also, if you wrote a patch, I'm sure there would be interest.
Alex
--- Mark Cuss [EMAIL PROTECTED] wrote:
Hello
I'm wondering if there are currently any plans to implement
XvGetStill for
the video4linux driver in
the problem is X is fundamentally based on the concept of a single
cursor. Most if not all GUIs are.
Alex
--- Grant Wallace [EMAIL PROTECTED] wrote:
I earlier had a question regarding how to support
multiple pointers. One reply to that was to write a
Window Manager to handle this. I can see
I've never used ati's fireglx drivers so I can't comment on how they
work. Plus since they are closed source binary only drivers, opensource
developers cannot add any new features. if you want a xinerama like
feature, ask ati directly.
I maintain the mergedfb functionality in the xfree86
I doubt it unless intel releases the necessary programming information.
Alex
--- hb [EMAIL PROTECTED] wrote:
Hi;
Some weeks back there was a discussion about a problem with some
laptops
(acer 661LCi, dell 500m,..) were the Vid-BIOS does not return the
panel
size and XFree can't use the
[EMAIL PROTECTED] wrote:
On Mer, 2003-10-15 at 21:07, Alex Deucher wrote:
the 3D drvier needs to be updated to mesa 5.x. Not much work has
been
done on it and I think there are some issues with the 2D driver.
There's no way it will make it into 4.4.0. the current code is on
a
branch
post the patch on bugzilla - http://bugs.xfree86.org
Alex
--- Carlo Gebhardt [EMAIL PROTECTED] wrote:
Dear list,
I have writen an xkb layout for the Logitech Elite Keyboard.
Maybe someone can use it or it will be included into XFree.
-- changes to symbols.dir:
there is a patch for support of the 731 in bugzilla:
http://bugs.xfree86.org/show_bug.cgi?id=754
No other drivers support roation in hardware at the moment, so it's up
to you to implement it from scratch I suspect. Keith Packard did much
of the work for xrandr for PDAs. You might want to look at
I've talked to quite a few people that have had problems getting
dualhead to work on radeon IGP chips. Specifically, the crt port seems
to go into powersave mode when dualhead is enabled. I talked to Hui Yu
at ATI about the problem and he hasn't seen it on his IGP boards using
the lastest code
--- Robert Woerle [EMAIL PROTECTED] wrote:
Hi
I am now in contact with Keith packard and checked out his latest
stuff ..
it looks promising since there is already a SMI Server there ..
unfortunately it crashes when i use the hw acceleration ...without it
works ..
Alex Deucher
As I recall we had problems with allocating additional memory for Xv on
neomagic chips (hence the overly_mem option). As I recall there was an
issue with allocating memory beyond the limits of the blitter, similar
to the problems with Xv on via (bug 525). Could this issue be resolved
with Alan
unfortunately neither do I, or I'd give it a shot.
Alex
--- Alan Hourihane [EMAIL PROTECTED] wrote:
On Wed, Oct 29, 2003 at 12:26:45PM -0800, Alex Deucher wrote:
As I recall we had problems with allocating additional memory for
Xv on
neomagic chips (hence the overly_mem option). As I
make sure you also get the XFree86 package from the extras directory
or you will get an error because your server is too old.
Alex
--- manu [EMAIL PROTECTED] wrote:
Le 29.10.2003 18:36:27, Michel Dänzer a écrit :
On Wed, 2003-10-29 at 01:23, Emmanuel Allaud wrote:
Hi all,
I just
I'll take a look at fixing this in the radeon driver. What needs to be
done to play nice with the DRI?
Alex
--- Alan Hourihane [EMAIL PROTECTED] wrote:
On Thu, Oct 30, 2003 at 07:47:06AM -0600, Billy Biggs wrote:
Alan Hourihane ([EMAIL PROTECTED]):
Well, if someone else has a chip, or
try removing the videoram line from your config. the driver will
detect videoram fine.
Alex
--- Salvio Sergi [EMAIL PROTECTED] wrote:
Hi,
I posted this on dri-users and have been suggested to post here...
Everything starts fine with no errors (as you can see from the logs).
The
I agree that with hex values the driver is much harder to read and
debug (as a casual developer). that's part of the reason the radeon
driver is so well developed and feature-rich. however, I'd say that
most drivers in xfree86 use hex values rather than symbolic names so
symbolic names are
, 2003 at 11:23:38AM -0800, Alex Deucher wrote:
I agree that with hex values the driver is much harder to read and
debug (as a casual developer). that's part of the reason the
radeon
driver is so well developed and feature-rich. however, I'd say
that
most drivers in xfree86 use hex values
I agree with you that symbolic names are better in just about all
respects. I'm just saying that the nv driver is not the only one that
doesn't do it. That's it for me.
Alex
--- Mike A. Harris [EMAIL PROTECTED] wrote:
On Mon, 10 Nov 2003, Alex Deucher wrote:
Date: Mon, 10 Nov 2003 06:38:24
a bit.
Alex
--- Francesco [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
The video overlay on radeons can be blended with the graphics layer.
It's pretty simple to code. I'm working on a patch to expose this
functionality as an xv attribute, XV_ALPHA, however, I just
recently
got
The patch available below adds dynamic power management support
(dynamic clock scaling) to the radeon driver. It is based on code I've
been testing from Hui Yu. It seems to work fine in basic testing on my
m6 and the 9200 in my desktop. More testing would be much appreciated
(especially
The attached patch adds alpha blending support to the video overlay on
radeon hardware. It's been tested on my 9200. It adds three new Xv
attributes: XV_ALPHA_MODE, XV_GR_ALPHA, and XV_OV_ALPHA.
XV_ALPHA_MODE - (0 or 1) selects the alpha blending mode. right now it
only supports key and global
Alex Deucher wrote:
The patch available below adds dynamic power management support
(dynamic clock scaling) to the radeon driver. It is based on code
I've
been testing from Hui Yu. It seems to work fine in basic testing
on my
m6 and the 9200 in my desktop. More testing would be much
--- Thomas Winischhofer [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
The attached patch adds alpha blending support to the video overlay
on
radeon hardware. It's been tested on my 9200. It adds three new
Xv
attributes: XV_ALPHA_MODE, XV_GR_ALPHA, and XV_OV_ALPHA.
XV_ALPHA_MODE - (0
put [PATCH] in the bug description maybe?
Alex
--- Alan Coopersmith [EMAIL PROTECTED] wrote:
Is there some way to mark a newly filed bug so it's clear that
there's a patch attached and it just needs to be reviewed and
checked in? According to the bugzilla docs, FIXED means the
code is
in global alpha mode though (on radeon), it
will blend the video with whatever the graphics layer shows so if I
could get rid of that rectangle of color, I'd get a nice blend with the
desktop and any windows over or under it.
Alex
--- Thomas Winischhofer [EMAIL PROTECTED] wrote:
Alex Deucher wrote
1 - 100 of 228 matches
Mail list logo
