From: Marc Aurele La France [EMAIL PROTECTED]
On Sun, 9 Apr 2006, Sergey Babkin wrote:
I've attached the patch that adds word- and byte-sized
PCI configuration reads and writes for the ix86
platform. The particular reason was to fix the
Tha patch was done against the X.org 6.9.0 code
From: Marc Aurele La France [EMAIL PROTECTED]
On Sun, 9 Apr 2006, Sergey Babkin wrote:
I've attached the patch that adds word- and byte-sized
PCI configuration reads and writes for the ix86
platform. The particular reason was to fix the
Tha patch was done against the X.org 6.9.0 code
Hi,
I'm not sure if it's a good idea to cc: to both X.org and
XF86 mailing lists, but the subject is kind of useful
for both.
I've attached the patch that adds word- and byte-sized
PCI configuration reads and writes for the ix86
platform. The particular reason was to fix the
support of
Sergey Babkin wrote:
Hi,
I'm not sure if it's a good idea to cc: to both X.org and
XF86 mailing lists, but the subject is kind of useful
for both.
Well, turns out that X.org list doesn't accept e-mail from
non-subscribers. So be it, XF86 only then. :-)
-SB
From: Salvatore Celsomino [EMAIL PROTECTED]
there is a system in order to convert a font .bdf or .pcf into font .fon or
.ttf. i have tried bdftofon.exe and pcftofon.exe, but for the my font,they
have errors: too many characters. thanks
ttf2pt1 (http://ttf2pt1.sf.net) can convert .bdf to
Type1
Fred Gleason wrote:
On Wednesday 25 May 2005 08:15, Sergey Babkin wrote:
The drivers have the defaults compiled into them
which can be changed from XF86Config. The problem
is that the ELO driver has (had?) it's defaults
set to 0-16K as well, so without an explicit
setting
useful manner.
-SB
-Original Message-
From: Sergey Babkin [mailto:[EMAIL PROTECTED]
Sent: Saturday, May 21, 2005 2:52 AM
To: devel@XFree86.Org
Subject: Re: Touch Input Driver port 3.3.6 - 4.x
Fred Gleason wrote:
On Wednesday 18 May 2005 18:48, Quentin Olson wrote:
I have
Fred Gleason wrote:
On Wednesday 18 May 2005 18:48, Quentin Olson wrote:
I have the source for an old input driver that was written for XFree86
3.3.6 that I would like to use under 4.x (4.5). Is there any
documentation on what is required, howtos, etc.?
Which touch hardware in
[EMAIL PROTECTED] wrote:
Hi everybody,
I am interested in getting the magictouch driver running. According to the
cvs comments, it needs updating to the new 4.x interfaces. My questions
are then:
- If there is no good sample driver, which driver would be a good starting
point ? i.e. up
Juliusz Chroboczek wrote:
DD [XFree86] was not, as a whole, FSF-free before the change, let
DD alone GPL-compatible. Same after the change. But then XFree86
DD has never factored in those two licensing criteria.
That's not quite the point, David.
Of the many reasons for which I was
Mike A. Harris wrote:
On Tue, 3 Feb 2004, Knut J Bjuland wrote:
Date: Tue, 03 Feb 2004 15:52:53 +0100
From: Knut J Bjuland [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format=flowed
Subject: Re: Manufacturers who fully
Tim Roberts wrote:
Andrew C Aitchison wrote:
XFree86 does not in general need kernel framebuffer support for
hardware which is supported by an XFree86 driver, as it has its own
framebuffer interface.
There are two cases where XFree86 does need kernel support.
* Chipsets like the
zhang hui wrote:
Hi, everyone
does anyone know any tools which can convert BDF to TTF in linux OS? the
tool is important to my current project,so if anyone got the tool,would you
please tell me where to download it?
please reply me to [EMAIL PROTECTED] as soon as possible
thank you very
David Dawes wrote:
return not NULL pointer but a valid pointer to some trash value,
so that their caller would be able to reference it without crashing
before the interpreter has a chance to halt.
Yes, that is a problem. The INTR_HALTED flag isn't tested until too
late. The potential problem
Hi,
I've been running XFree86 4.3.0.1 on a machine with a particularly
weird videocard and I've got the VESA driver craching. If anyone
wonders, the BIOS data in the log is:
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 1024 kB
(II)
All,
I've been thinking about the fonts stuff and I think I've got
an interesting idea about the font servers.
Normally a font server runs as a TCP/IP server and the X server
connects to it as a client. This is not very convenient because
it makes running the running of a font server by a
Alexander Gelfenbain wrote:
On Wed, Dec 19, 2001 at 07:20:45PM -0500, Sergey Babkin wrote:
Alan Coopersmith wrote:
applications. We have designed a display and platform-independent text
architecture, the Standard Type Services (ST) framework, which handles
not just font rendering
Alan Coopersmith wrote:
applications. We have designed a display and platform-independent text
architecture, the Standard Type Services (ST) framework, which handles
not just font rendering, but text layout and font management as well.
ST incorporates typographically sophisticated features
Alan Coopersmith wrote:
applications. We have designed a display and platform-independent text
architecture, the Standard Type Services (ST) framework, which handles
not just font rendering, but text layout and font management as well.
ST incorporates typographically sophisticated features
19 matches
Mail list logo
