Title: this list is archived
you can read this list on http://mail-archive.com, starting now.
Title: RE: ATI card addition to xf86PciInfo.h
> One thing I don't understand about this is that this is an integrated
> graphics chipset, right ? I.e. it uses part of system RAM for
> video RAM.
> There is no code in radeon driver to deal with this yet.
>
> best
Title: RE: Debugging in RH8?
> ftp://people.redhat.com/mharris/gdb-xfree86
>
> Let me know if there are any problems.
Can you please adjust user permissions there?
Thanks.
-Alex.
Title: RE: Debugging in RH8?
on 2nd try i got the listing now - the read error has vanished.
> -Original Message-
> From: Mike A. Harris [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 16, 2003 01:39
> To: Alexander Stohr
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED
Title: RE: s3virge & bigendian
> >Hmm, I have a pdf, but I think I got it from the xfree86 ftp
> devel area,
> >so I'm not sure about the status right now.
>
> If you got it from there, then you can't redistribute it. If you get
> it from another (non-NDA) source, then that's a different ma
Title: RE: s3virge & bigendian
> +
> +#if X_BYTE_ORDER==X_BIG_ENDIAN
> + pScrn->fbOffset = 32*1024*1024; /* bigendian aperture is at 32M */
> +#else
> + pScrn->fbOffset = 0;
> +#endif
> + pScrn->memPhysBase = ps3v->PciInfo->memBase[0] + pScrn->fbOffset;
> +
>
Title: RE: vbe and driver vesa
if you dont get any further feedback
then i would suggest you to send that patch
to [EMAIL PROTECTED] which gets you a
"ticket" for mainline integration.
i had a look into the patch and
do think its quite simple in effect.
even reverting it temporarily could
Title: glapi_x86.S glx86asm.py
according to its headline glapi_x86.S was generated
by the script glx86asm.py - its just that i cannot
find that script in the XFree86 sources. Any hints?
-Alex.
Title: RE: glapi_x86.S glx86asm.py
> From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v
>
> revision 1.2
> date: 2000/12/07 16:12:47; author: dawes; state: dead; lines: +0 -0
> Remove from the trunk the Mesa files that aren't needed.
>
> Latest entry in cvs log of c/extras/Mesa/src/X
> You'd have to ask Brian to be sure, but I believe the
> intention is that
> if the interface ever changes, a new .S file be generated in the Mesa
> tree and imported to the XFree86 & DRI trees. There should
> never be a
> case where the .S file would change in XFree86 and not change in Mesa
what about syncing to the vertical blank?
some cards do provide you an interrupt handler for this.
i mean if you want to do it with OpenGL in fullscreen anyways
then you just have to use double buffered mode and call glSwap()
anytimes you are done with rendering.
if you want to do something more
PCI-gart is a still developing component
that is maintained in the "XFree86 3D instable" tree,
which is better known as "dri-devel" project.
you might have better chances when asking there.
anyways, that far i do know about PCI-gart,
it was under some rather vague development.
there were more pat
> Alexander Stohr wrote:
>
> >what about syncing to the vertical blank?
> >some cards do provide you an interrupt handler for this.
>
> what is the vertical blank ? . do you know somewhere
> where I can
> get more information on this?
www.opengl.org is o
All below subscribes to my poor(!) knowledge
in order to get you a better view of your state:
VendorID
0x1002 means an original ATI chip design
DeviceID
0x4136 "A6" is the A3 chip, which might be better known as
Radeon IGP 320 M (M=Mobility=Laptop/Notebook)
0x4336 "C6" is the U1 chip, wh
> Please forward 'scanpci -v' output to XFree86 support team.
>
> When reporting a problem related to a server crash, please send
> the full server output, not just the last messages.
> This can be found in the log file "/var/log/XFree86.8.log".
i have not seen your XFree86.*.log file.
> Please
> It looks like you need to begin with Linux kernel FAQ:
> http://www.tux.org/lkml/#s4-3
why not point him out to
"Writing Linux Device Drivers, 2nd edition"
from Rubini/Corbet? Its even availabel for download.
> /Matti Aarnio <[EMAIL PROTECTED]>
>
> >
RandR integration with partial enable of features?
> -Original Message-
> From: Alan Hourihane [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 19, 2003 12:15
> To: [EMAIL PROTECTED]
> Subject: RELNOTES for 4.3.0
>
>
> Here's a list of items for the RELNOTES for 4.3.0, if anyone
>
> > A quick question regarding the 9500 and 9700 series Radeons
> - is support for
> > 3D acceleration planned?
>
> Eventually, someday, if ATI releases the relavent documentation and
> enough developers have the time to do the work. In the meantime, if
> you're on x86 Linux (or perhaps some B
Gatos is focussing on video and TV playback,
TV/video-in functionality and video capture.
But they are _not_ focussed on 3D to my understanding.
thanks for the link to the AIW Radeon 9700 comments.
the text outlines that even gatos has not timeframe
how their development will proceed.
for my und
> Anyhow, thanks for the solution! Its a shame that X isn't
> going to be able
> to cope with multiple focus trees, but I agree the issues are
> many, and the
> need little...
>
> Rob
what if it is not at all a software cursor
but something like the x-eyes application?
i mean a free from windo
[snipped the patch]
> Is there a better way to submit patches like this? I've just
> subscribed
> to the devel list in the last 10 minutes :).
>
> Fred Clift
sending to [EMAIL PROTECTED] queues your patch for integration.
maybe unified diffs are the prefered style (diff -u src dst).
it improv
sorry this is the [EMAIL PROTECTED] mailing list,
dealing with the X11 grafical window environment
for the Linux, Unix, BSD and other operating
systems. this specific list handles mainly internal
programming topicis on the mentioned project.
i think you should ask your question somewhere else.
-
please visit e.g. http://midori.transmeta.com
thats what you possibly do want.
XF86 this is really not the emedded Linux helpdesk, thanks.
pgui (PicoGUI) is a grafics centric project,
so you are wrong with posting them as well.
i mean you are currently in process of fiddeling
out which OS and f
Hmm, SonicBlue (aka known as S3) has claimed
bankrupcy (Chapter 11) recently, so its a changing
situation with S3TC compression right now -
who will ever buy that patent and charge the world
for the next 70 years?
Of course the prefered solution would be that some
interested circles buy it as a
(all expressed below is my personal opinion)
there is a sound in the below text
which i dont like for misc reasons.
but ignoring my impressions, there might
be some basic clarifications needed.
the xfree86 developers drove the policy to only
incoroporate highly "important fixes" for releases
th
Diamond/S3 had a series of driver CDs that
were meant for the vendor and service level.
Those were called "ServiceCD" and contained
a current driver collection of all products.
I have to assume that the last release is
at least two years old and might be in stock
for misc people since they were fo
i am seeing constructs like this at
several locations of the XFree86 sources:
*.h:
extern char *Xpermalloc(
#if NeedFunctionPrototypes
unsingend int /* size */
#endif
);
*.c:
char *Xpermalloc(unsigned int length)
{ ... }
#if NeedFunctionPrototypes
XrmQuark XrmStringToQuark(
I dont really know driver or chipset in detail,
but its the way that it needs programming so
that the timing for the LCD does match. black
or striped or whatever effects do indcate
wront timing for the flat pane display.
If the device is capable of dual head in other
OS condtions then it can do it
> From: Mike A. Harris [mailto:[EMAIL PROTECTED]
> I plan on replacing the Cards database in Red Hat Linux with a
> new mechanism sometime in the future which will be much more
> flexible, allow per architecture overrides, allow the config tool
> to know what hardware supports DRI and on what speci
> On Fri, 18 Jul 2003, Mark Vojkovich wrote:
>
> > For consumer desktop that's true. There is one potential business
> > case in the professional desktop market. SGI's, HP's and Sun's old
> > workstation customers have been moving over to Linux.
Thats no market secret to anyone at all. You
> From: William Suetholz [mailto:[EMAIL PROTECTED]
> Mr. Harris, yes I am one of "Those people" who want a device to work
> in my chosen operating system,
/me wants "Commodore 64 - BASIC BIOS 2.0" support, call it my favorite!
Cool machine, boots in 2 seconds to a fully useable prompt.
It must
from 24 hours to 7 days depending on complexity
and on people having time working on it.
-Alex.
> -Original Message-
> From: Sven Goethel [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 24, 2003 19:17
> To: [EMAIL PROTECTED]
> Subject: patch procedure ..
>
>
> sorry for being lazy and n
mobile devices will always have more limitations,
so you wont get rid of any sort of low bpp formats.
in multi buffer environments, such as OGL with front,
back, depth, stencil, overlay, whatever you will be
in need to deal with any sort of pixel depth at the
same time as well.
for imaging progra
> I'm running XFree 4.3.99.8 with kernel 2.6.0.test2 on a via M1
> motherboard.
> I loaded the modules for mtrr, i2c and agpgart for via.
>
> Into XF86Config I choose via driver
> When I start X there's always this warning:
>
> (WW) via(0): Failed to set up write-combining range (0x
> I
> I have laptop with 320m radeon. radeonfb didn't seem
> to work for it on 2.4.21. Has this changed in 2.6.0-test2?
this is the XF86 development mailing list
for the XF86 windowing system infrastructure.
there are other people around that do
work on the framebuffer device support.
you might
just a short comment on the illustrations...
> Mode 1: (fixed width font required for viewing)
>
> +--+
> |++ +-+|
> ||| | ||
> ||| | ||
> ||
> Granted, as the patch stands. However, I don't mind doing the minimal
> fixing up for inclusion, as this information would be
> extremely useful in
> some logs.
>
> Why the extra symbol, if I may ask, instead merely using
> defined(linux)?
i suppose that those feature can be done on non-linu
should be supported in 2D by latest XF86 CVS drop.
maybe supported X4.3.0 release by the "ChipID"
override/fake option of XF86Config file, see man pages.
supported by latest ATI 3.3.x beta drivers
as from Schneider-digital.de and SuSE ftp.
general user questions should possibly
not go to the
CP mode means using an engine on the chip
that gets the command data from main memory
by itselves, some sort of busmaster DMA stream.
MMIO means that the driver does program the
chipset directly via its memory mapped registers.
DRI means direct rendering and is the most common
socket for current
(WW) RADEON(0): monitor1: Using default hsync range of 28.00-33.00kHz
(WW) RADEON(0): monitor1: using default vrefresh range of 43.00-72.00Hz
(II) RADEON(0): Clock range: 20.00 to 350.00 MHz
(II) RADEON(0): Not using default mode "800x600" (hsync out of range)
(II) RADEON(0): Not using mode "800
It looks to me that your grafis hardware is mirrored some 40 times
on the PCI bus scan. and therefore the autodetection tries to load
a bigger bunch of drivers, thus i assume memory exhaustions happens.
Either you do find a way to fix up the PCI bus scan to up to the
very first grafics device (a k
> This is the minimum work to get this program into ansi shape.
> This patch is
> ready for inclusion. If their are no objections to the patch,
> it would be
> very nice to get this in ASAP. It will make some other projects I am
> working on go smoother.
>
> Thanks, Warren Turkal
i have no reas
> So who applies these patches then?
people that do read "[EMAIL PROTECTED]", if you submitted it there,
or people who do read this list with some care.
> I don't have CVS write, nor do I want it at this point.
unlikely to get such an account that fast. (i dont have one.)
anyways patching works
> Since we already have a jmp_buf which is much larger than
> necisarry, all
> that is needed is to take the first offset into it which is properly
> aligned for the given architecture and use that as the system jmp_buf.
> when the compiler can guarentee the proper alignment this becomes a
> 'nop'
is there some x3.3.6 to x4.x.x porting guide around?
-Alex.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Hello,
i stumbled across the above mentioned define and
related code in the XFree86 sources (lnx_video.c).
comparing X4.1.0 and X4.3.0 i found that the
condtitnal coding of "if (base % size)" has
vanished at some point in time and the handling
is now hardcoded at this code location.
to my best k
i tried a "make World"/make on a current CVS
snapshot, using RH Linux 7.3 - and found that
the drm kernel module makefiles will need
root rights on /lib/modules/.
i know that prior versions of xf86 sources
did not force me to be "root" for building
them. and i think it is a bad habit to force
use
> I tried just leaving the display running without doing anything
> interactive with the interface and X ran for several hours before
> freezing. All that was running was Xscreensaver. I then tried
> again using
> X normally but with a different window manager (XFCE 4) and
> it worked for
> about
> I suppose I could have a hardware problem, since my PC is a
> couple years
> old now. However, I can leave the same computer just running a 2.4.x
> kernel for days with no problems. Would the redesigned kernel
> 2.6.x bang the hardware so much more; going beyond that of
> kernel 2.4.x?
It ca
> I always get these errormessage when I load agpgart and fglrx
> and then startx.
>
> The weird thing is that X starts up with this gray screen and
> the mouse
> working. It only crashes the instant when the KDE dialog
> should be coming up.
>
> (==) Using config file: "/etc/X11/XF86Config-4"
> >run ldd on your glxgears or glxinfo executables and see
> which libGL it
> >is using.
>
> It is using the ones from the driver. It uses libGL which
> points to a link
> which is the drvier lib. I made a diff on the file which is
> in the driver
> directory and the installed libGL.so.1.2 and
you do want to report, 2D is okay,
but there are performance issues
and some glitches in 3D?
if yes, then this roughly matches
what is expected state of the art.
2D is solid and maintained by XF86
whilst 3D is hardening in DRI project
for almost some time and the last
merge back into XF86 CVS sho
the _ is the mailmain default but can be canged.
only the fglrx closed source drivers from ATI
for the i386/Linux platform do have 3D.
Data"books" are no longer state of the art
in the information technologies age.
> > On Wednesday 10 December 2003 12:48, wim delvaux wrote:
> > > Any idea
> I have tried these drivers but refuse to work.
> They think I have an (unsupported) OEM card (=powered by ATI)
> while according to the identity check programs
> run under XP it 'should' be an ATI one (=Built by ATI)
There is no general OEM barrier anymore.
It only was i
> Can someone explain why the "<" business is in the
> source file?
That should not be. It looks to me like a broken file.
Either patching or CVS transfer might have failed.
-Alex.
> static void r200SetBuffer( GLcontext *ctx,
>GLframebuffer *colorBuffer,
>
tryout the closed source drivers from ATI´s website.
if you find out about any problem then call either
ATI or SuSE support on them. they must have a solution.
-Alex.
- Original Message -
From: "William W. Austin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, December 28, 2003
if you dont have succes on OpenGL support with the 3.7
drivers from ATI then maybe tryout one of the earlier drivers.
i cant tell you much about the 3.7 driver caracteristics
since i have not had much time in recent 4 weeks
and no equipment ready for testing them myselves.
i do know that UT2003 wa
> Subject: *** GMX Spamverdacht *** Re: Manufacturers who fully disclosed
> It is possible to gain the specs for a chip by discetion for i.e R300
> chip or NV 30 chips with the right tools like a electon microscope?
"full specifications" as the headline does say is more than just the
register
des
- Original Message -
From: "netpython" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 04, 2004 9:38 AM
Subject: *** GMX Spamverdacht *** Re: *** GMX Spamverdacht *** Re:
Manufacturers who fully disclosed specifications for agp cards?
[...]
> (reverse engineering)
>
59 matches
Mail list logo
