Misschien leuk voor u
- Deze mail is doorgezonden omdat iemand dacht dat u wellicht interesse zou kunnen hebben. Mocht u na het lezen van deze mail geen interesse hebben dan kunt u de boodschap verwijderen, u ontvangt geen verdere berichten meer tenzij u daar uitdrukkelijk om verzoekt. Computervrienden De club computervrienden gaat zich lanceren in mei 2002. Voordat deze datum wordt bereikt willen wij het volgende bereiken: 1. Een leuke vriendenkring (leden). 2. Een proffesionele website. 3. Een aantal sponsors. Om dit te bereiken hebben we uw hulp nodig! Wij vragen u dan ook om deze mail door te sturen naar vrienden en bekenden. Maar verzoeken u uitdrukkelijk dit niet te doen aan onbekenden of posten in nieuwsgroepen ed. Wat gaat Computervrienden doen? -Het verhelpen van computerproblemen voor beginners en gevorderden. -Het geven van gratis lessen door middel van e-books, irc en forums. -Het uitgeven van een leuk gratis maandblad (electronisch), boordevol tips en informatie. -Het lanceren van projecten, bijvoorbeeld online games maken. -Het organiseren van compitities bij online gamen. -Gezamelijk hard en software inkopen om prijzen te reduceren. -Bemiddelen met providers als er problemen zijn, bijv slechteverbindingen, slechte helpdesks enz -Ter zijnertijd een eigen telefonische helpdesk opzetten tegen normaal telefoontarief. -Het uitwerken van plannen welke door leden zijn aangebracht om het werken/spelen met de computer zo leuk mogelijk te maken. Hoe gaat Computervrienden dit doen? Ons ledenbestand gaat alle niveau's bevatten, bijvoorbeeld de huisvrouw die af en toe de computer aanraakt tot aan de doorgewinterde programmeur. Het is dan ook de bedoeling dat leden elkaar gaan helpen. Bijvoorbeeld iemand stelt een vraag in het forum, een ander geeft het antwoord. Dit kan ook per e-mail en zal centraal worden geregeld. Dus in het kort: elk lid dat actief mee wil doen, kan zijn steentje bijdragen. Lid worden is erg simpel: Stuur een e-mail naar : [EMAIL PROTECTED] en schrijf een kort berichtje dat je lid wilt worden van computervrienden, en wat relevante gegevens. De relevante gegevens zijn alleen de gegevens die je kwijt wilt, je naam, je adres, enz... Je mag dus zo anoniem blijven als je wilt. Kosten: Lidmaatschap is gratis, maar je ontvangt elk jaar een uitnodiging voor een vrijwillige bijdrage. Deze bijdrage bedraagd slechts 6 euro per jaar. Betalende leden zorgen ervoor dat wij onze website kunnen hosten, en later leuke dingen kunnen organiseren. Er gaat veel meer gebeuren met dit geld, en uiteraard worden alle betalende leden op de hoogte gehouden van de inkomsten en uitgaven van de club. Wat gaat er gebeuren? Tot mei nog weinig! U wordt wel op de hoogte gehouden van tussentijdse besluiten en projecten. Als u mee wilt werken bij de ontwikkeling (beginfase) van onze club, schrijf ons dan alstublieft op [EMAIL PROTECTED] Wij kunnen echt alle hulp gebruiken, en dat is ook het moraal van onze club. Hartelijk dank voor uw aandacht en tijd, en vergeet niet deze mail door te sturen naar vrienden, bekenden en mischien bedrijven die willen sponsoren! ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Invitation for public discussion about the future of X
[Announcement and call for comments elided] What I'd like to see are Keith's reasons for wanting the fork, a chance to see if they're valid, and some progress on resolving what comes out as a result of all this. I've been watching this project since 1992, and wouldn't want it to collapse under political pressures. We don't need a NetXF86, OpenXF86 and a FreeXF86 type of situation. Stephen -- The time you enjoy wasting is not wasted time - Bertrand Russell ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
4.2.0 vesa depth 4 broken
The death of a disk drive on my old 486 gave me the opportunity to upgrade the software (Suse 6.1) to something more contemporary (redhat 7.3). This encouraged yhe upgrade of XFree86 from 3.3.x to 4.2.0. In 3.3.x, to run a dual headed system, the color card was limited to mono or 4 bit, so those were my initial tests. The monitor on this box is a MultiSync II, which was old when the 486 was new. The vesa driver is more flexible in locating clocks and agreed to drive the monitor at [EMAIL PROTECTED] That's probably enough history. Running with 4 bit depth, the shadow buffer size computation uses 4 bits per pixel, but the pixmap format says to use 8 and that is what shadowUpdatePlanar4 uses, walking off the end of the buffer and video memory, causing a signal 11. Doubling the size of the buffer stops the signal 11, but the screen is double width, wrapped on top of itself. Halving the size in the pixmap format fixes the window width problem, but funts are still double width. Turning off the shadow buffer solves the problem. Depths 8 and 16 work great, and with the new architecture in 4.x, the requirement of sharing memory models across displays goes away, so I'm not likely to use 4bpp again. Getting the hercules running will be a later message. Enjoy Lee [EMAIL PROTECTED] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Possible bug in xaaFillPoly.c
This is not the correct solution. Mono8x8PatternRectHelper needs
a pattern, yet the API doesn't pass one. It was intended that
it be passed in pCache-pat, yet that wasn't set up. There
was a scratch cache structure set aside for that type of thing.
Can you try the attached patch?
MArk.
On Wed, 19 Mar 2003, Mark Vojkovich wrote:
There's definitely a bug there. I'm not sure if that's the
correct solution, or there is a bigger problem. I will review
this code tonight. Thanks for pointing this out.
Mark.
On Wed, 19 Mar 2003, Alexandr Andreev wrote:
Hi,
Possible, there is a bug in the Mono8x8PatternRectHelper() function.
Lets look at XAAFillPolygonStippled():
Assume:
1. type == DO_MONO_8x8,
2. infoRec-Mono8x8PatternFillFlags:
HARDWARE_PATTERN_SCREEN_ORIGIN is NOT set,
HARDWARE_PATTERN_PROGRAMMED_BITS is set,
HARDWARE_PATTERN_PROGRAMMED_ORIGIN is NOT set.
In this case, pCache == NULL, and RectFunc = Mono8x8PatternRectHelper
Later, in Mono8x8PatternRectHelper() we will crash when trying to access
pCache-pat0.
I think that this patch may help, but i'm not sure.
*** xaaFillPoly.c.old Thu Mar 20 10:46:51 2003
--- xaaFillPoly.c Thu Mar 20 10:54:21 2003
***
*** 770,776
pCache = (*infoRec-CacheMono8x8Pattern)(
infoRec-pScrn, patx, paty);
patx = pCache-x; paty = pCache-y;
! }
RectFunc = Mono8x8PatternRectHelper;
}
--- 770,780
pCache = (*infoRec-CacheMono8x8Pattern)(
infoRec-pScrn, patx, paty);
patx = pCache-x; paty = pCache-y;
! } else {
! pCache = (infoRec-ScratchCacheInfoRec);
! pCache-pat0 = patx;
! pCache-pat1 = paty;
! }
RectFunc = Mono8x8PatternRectHelper;
}
Re: Install errors with 4.3.0 on RH7.3?
No responses to this question? I really would like to figure out why the build is not installing on this machine. Perhaps this is not the right forum and there is a better mailing list to ask these questions about build breaks? Kendall Bennett [EMAIL PROTECTED] wrote: I have finished a clean build of 4.3.0 on my Red Hat 7.3 machine, and the log indicates there are no errors (grep for ] Error). However when I do a 'make install' I get errors about halfway through I think related to some @Aliases file or something. I have attached my install.log file. Can someone tell me what is wrong and how I can fix this to get the install to work properly? Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
hercules driver for 4.x
The attachments are the pieces I used to build the hga driver for
hercules cards. The Imakefile was cloned
from the one for vesa and probably has extra cruft, but it does the job.
Thes files expect to be in hw/xfree86/drivers/hga. You will need the
resource conflict fixes I posted earlier to get it running.
Don't forget to add hga to your driver list in site.def if you want it
built automatically.
If you run linux and use mdacon, there are some interaction issues.
XFree86 switches the active
console to an unused one, but you have two in use, so one is exposed to
console driver activities.
Bringing up a dual headed X from an mda console steps through a console
driver bad pointer when X
terminates (at least it does on Redhat 7.3, 2.4.18-3), leaving stuck
displays. Ctrl-alt-del still works,
but thats about it.
Enjoy
Lee Olsen
[EMAIL PROTECTED]
/*
* Copyright 2003 by Lee Olsen [EMAIL PROTECTED]
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that copyright
* notice and this permission notice appear in supporting documentation, and
* that the name of Lee Olsen not be used in advertising or publicity
* pertaining to distribution of the software without specific, written
* prior permission. Lee Olsen makes no representations about the suitability
* of this software for any purpose. It is provided as-is express or
* implied warranty.
*
* LEE OLSEN DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
* INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
* EVENT SHALL LEE OLSEN BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL
* DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
* PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
* ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
* THIS SOFTWARE.
*/
#ifndef _HGA_H_
#define _HGA_H_
/* All drivers should typically include these */
#include xf86.h
#include xf86_OSproc.h
#include xf86Resources.h
/* All drivers need this */
#include xf86_ansic.h
#include compiler.h
#if 0
/* Drivers for PCI hardware need this */
#include xf86PciInfo.h
/* Drivers that need to access the PCI config space directly need this */
#include xf86Pci.h
#endif
/* ShadowFB support */
/* from hw/xfree86/shadowfb, not miext/shadow */
#include shadowfb.h
/* bank switching */
#include mibank.h
#if 0
/* Dga definitions */
#include dgaproc.h
#include xf86Resources.h
#include xf86RAC.h
#endif
#include xf1bpp.h
#include fb.h
#include mfb.h
#define HGA_VERSION 4000
#define HGA_NAMEHGA
#define HGA_DRIVER_NAME hercules
#define HGA_MAJOR_VERSION 0
#define HGA_MINOR_VERSION 1
#define HGA_PATCHLEVEL 0
#ifdef CSRG_BASED
#define MONOBASE 0xFF00
#else
#define MONOBASE 0xF000
#endif
/*
* Define the generic HGA I/O Ports
*/
#define HGA_INDEX 0x3B4
#define HGA_DATA0x3B5
#define HGA_MODE0x3B8
#define HGA_STATUS 0x3BA
#define HGA_CONFIG 0x3BF
#define DSP_VSYNC_MASK 0x80
#define DSP_ID_MASK 0x70
#define BITS_PER_GUN 1
#define COLORMAP_SIZE 2
#define HGA6845MapBase ((unsigned char *)0xB)
#define HGA6845MapSize 0x8000
#define HGA6845ScanLineWidth720
#define HGA6845HDisplay 720
#define HGA6845VDisplay 348
/*XXX*/
typedef struct {
unsigned char config; /* write only conf register at port 0x3BF */
unsigned char mode; /* write only mode register at port 0x3B8 */
unsigned char tbl[16];
} hga6845Rec, *hga6845Ptr;
typedef struct _HGARec
{
EntityInfoPtr pEnt;
CARD16 major, minor;
GDevPtr device;
#if 0
pciVideoPtr pciInfo;
PCITAG pciTag;
#endif
miBankInfoRec bank;
int curBank, bankSwitchWindowB;
CARD16 maxBytesPerScanline;
int mapPhys, mapOff, mapSize; /* video memory */
void *base, *VGAbase;
hga6845Ptr state, pstate; /* Video state */
int statePage, stateSize, stateMode;
int page;
Bool shadowFB, primary;
CARD8 *textContents;
CARD8 *shadowPtr;
CARD32 shadowPitch;
CARD32 windowAoffset;
CARD32 frameX;
CARD32 frameY;
CloseScreenProcPtr CloseScreen;
OptionInfoPtr Options;
} HGARec, *HGAPtr;
typedef enum save_restore {
MODE_SAVE,
MODE_RESTORE
} SaveRestoreFunction;
#endif /* _HGA_H_ */
/*
* Copyright 2003 by Lee Olsen [EMAIL PROTECTED]
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that copyright
* notice and this permission notice appear in supporting documentation, and
* that the name of Lee Olsen not be used in advertising or publicity
*
Re: Install errors with 4.3.0 on RH7.3?
On Tue, 18 Mar 2003, Kendall Bennett wrote: Hi Guys, I have finished a clean build of 4.3.0 on my Red Hat 7.3 machine, and the log indicates there are no errors (grep for ] Error). However when I do a 'make install' I get errors about halfway through I think related to some @Aliases file or something. Sorry, I thought I'd replied, seems I never pressed send :-( Why grep ] Error I use grep '\*\*' to determine whether the make World has succeeded. It looks to me as if your make World failed (but kept going as it usually does) so install tried again and failed. I have xc/programs/rstart/contexts/@Aliases xc/programs/rstart/samples/contexts.odt1/@Aliases xc/programs/rstart/samples/contexts.sun/@Aliases all with matching ,v files, so it may be a problem with your check out, or another case of one broken platform in 12. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Generic rootless code home
On Thu, Mar 20, 2003 at 04:32:23PM -0800, Torrey Lyons wrote: XDarwin's generic rootless code is generally useful for anyone implementing an X server on top of another windowing system. It was written to abstract the implementation details of dealing with the underlying window system. It is used by XDarwin to provide a rootless X server on Mac OS X and by XDirectFB to do the same over DirectFB. The code is sufficiently mature and generally useful that we would like to move it out into a more accessible place instead of being buried in Xserver/hw/darwin/quartz. Are there any suggestions for a suitable home? Likely candidates are Xserver/rootless or Xserver/miext/rootless. Xserver/miext/rootless sounds like a plan. I'm sure the cygwin folks could use it too over the top of Windows. I'd certainly be interested in it. Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Install errors with 4.3.0 on RH7.3?
Andrew C Aitchison [EMAIL PROTECTED] wrote: Why grep ] Error I use grep '\*\*' to determine whether the make World has succeeded. Probably because that was the simplest way I could find, and it seems that whenever an error is found, the above string is always there ;-) It looks to me as if your make World failed (but kept going as it usually does) so install tried again and failed. I believe the make World succeeded just fine. I will grep with your error string tomorrow and see what I dig up (it is on a differetn hard disk to the one I am installing Linux distros on now in my test box ;-). I have xc/programs/rstart/contexts/@Aliases xc/programs/rstart/samples/contexts.odt1/@Aliases xc/programs/rstart/samples/contexts.sun/@Aliases all with matching ,v files, so it may be a problem with your check out, or another case of one broken platform in 12. Well I am not checking the code out of CVS at all, but building from the raw tar.gz files unzipped on my system. Perhaps this file is in CVS but is missing from the source archives? I will check tomorrow and see what i can find out. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
