harry wrote:
Using gdb-xfreemod 6.0 instead of gdb-xfreemod 5.11-2.0 , I could use gdb to
debug XFree86 430 under redhat 9.0.
Just curious: any reason why the xfree mods to gdb haven't been merged
upstream? A religious issue, maybe?
--
.:.
Bryan W
.
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
, if somebody replaced Athena with Gtk or Qt or Fox or ___,
who'd be upset?
/flame
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
for ideas?
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Tim Roberts wrote:
On Fri, 03 Oct 2003 15:55:47 -0500, Bryan W. Headley wrote:
It's 3 curves of 256 datapoints. Floating point or integer. What you
have to assume is that every point on the curve is grabbable, either
through a spline curve widget, or something like
datapoint [123]^ red [ 45
David Dawes wrote:
On Tue, Sep 30, 2003 at 12:51:55PM -0500, Bryan W. Headley wrote:
David Dawes wrote:
On Mon, Sep 29, 2003 at 09:52:16AM -0500, Bryan W. Headley wrote:
David,
How is the work on the XF86Config parser coming? I ask because I noticed
that the 'Option Device /dev/input/event
.
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
' products
work with X?) num programs.
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
David Dawes wrote:
On Mon, Sep 29, 2003 at 09:52:16AM -0500, Bryan W. Headley wrote:
David,
How is the work on the XF86Config parser coming? I ask because I noticed
that the 'Option Device /dev/input/event?' is getting weird, like I
thought it would when we were discussing Input System
...
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
to know what the incoming packets look like. Have you
dropped a line to Hantouch? If you have, and they're unwilling to help,
you probably can track RS-232 communications between the touchscreen and
the Windows driver...
Good luck!
--
.:.
Bryan W. Headley
Egbert Eich wrote:
Bryan W. Headley writes:
o Packet building. This would be input device/interface type specific.
It would know that a packet of incoming data is 'x' bytes in length; it
might understand that bit 4 is always set for synchronization purposes.
It composes
Egbert Eich wrote:
Bryan W. Headley writes:
No. I have merged the VIA driver and I did some work on it
to fix some issues that violated the driver design guidelines.
Cool.
2) How is it going?
3) I notice that Via also has L4V and DRM code for X, too. Do you know
if they're putting
through other
means (the ubiquitous procfs/sysfs)
Numbers 2 and 3 potentially have a pretty open vocabulary, as they are
driver type and driver-specific. Number 3 I've been calling QoS all this
time, as its primary use is #3a.
--
.:.
Bryan W
and DRM code for X, too. Do you know
if they're putting it into the distribution?
4) That hardware MPEG-2 decoder of theirs is going to drive everyone
nuts. I'm already there...
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
Egbert Eich wrote:
Bryan W. Headley writes:
True, and that's a whole other set of problems. At least, in your
example, everything is in the XI layer, if not in the individual driver.
I'm more worried about an XI layer that talks to its drivers, but
there's also a layer in Misc
Egbert Eich wrote:
Bryan W. Headley writes:
Egbert Eich wrote:
A lot of error conditions can only be fixed by the administrator.
Can you come up with a really good real life example?
I suppose 'Battery Low' would be one.
That's the easiest one for everyone to grasp. Let's see
Egbert Eich wrote:
Bryan W. Headley writes:
Egbert Eich wrote:
As you said a HID device is more or less unidirectional. Therefore
you won't be able to detect from the device interface that something
is wrong. The HID interface itself would have to provide QoS.
Anyway QoS would
Egbert Eich wrote:
Bryan W. Headley writes:
I do understand the 'the battery in the cordless mouse is getting low'
message. This would better live in the hardware messaging, ie. the
successor of todays xf86misc extension.
Ah! You're concerned about which layer supports the messaging. I'm
not interested or I got thrown into
his junk email filter. Much like your email did -- don't know why. Need
a Bayessian debugger to watch it's decision tree... :-)
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel
callback structs will get punished.
Just because I like to incite riots, if it turns out we send XML
messages back and forth, I won't be too hot bothered about it. (Now,
duck!)
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
/switch mode commands we
asked for). I'm trying to think what would be a less-than-disasterous
but still inconvenient situation for a video card to report...
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel
Egbert Eich wrote:
Bryan W. Headley writes:
Egbert Eich wrote:
Bryan W. Headley writes:
I do understand the 'the battery in the cordless mouse is getting low'
message. This would better live in the hardware messaging, ie. the
successor of todays xf86misc extension.
Ah! You're
monitor for complaints...
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Egbert Eich wrote:
Bryan W. Headley writes:
Maybe not everything... Some things only make sense at server startup,
but yes, I want to make things configurable on the fly - but using
another extension, not XI.
Correct. My outlook is a more generic client -- driver API
Elliott Mitchell wrote:
From: Bryan W. Headley [EMAIL PROTECTED]
Egbert Eich wrote:
Bryan W. Headley writes:
4) Then, some level of user-customizable API. E.g., all parameters have
names that are converted to Atoms, whose values are type-safely
converted back and forth. Gad, it sounds like
run X locally on a server in the server room,
consider the Win32 admin, who thinks it natural to have a login screen
on every one of his machines. They are out there...
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
Egbert Eich wrote:
Bryan W. Headley writes:
Egbert Eich wrote:
Claus Matthiesen writes:
Let's just forget about expanding the _XDeviceInfo struct for a minute
and just concentrate on the -type field. Because as regards legacy
software: Does anybody use the -type field? I
,
and then have a single point of failure to architect around.
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
the Display and screen.
But it certainly can be generalized, so any device driver can
receive/reply to messages.
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org
Warren Turkal wrote:
Bryan W. Headley wrote:
No but you don't want to be a jerk and compete with somebody else. As
if there were enough developers to go around that we'd steal each
other's projects :-)
Sometimes a little competition can improve the final product. Think lvm2 v.
evms
to send a sequence to
the tablet to switch between relative and absolute coordinates. Unless
of course you also wrote the kernel device driver and somehow know how.
Which I did and I do, but I've been known to cheat :-)
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
with default settings
4) Then, some level of user-customizable API. E.g., all parameters have
names that are converted to Atoms, whose values are type-safely
converted back and forth. Gad, it sounds like SOAP / XML/RPC! Maybe it is...
--
.:.
Bryan W. Headley
Claus Matthiesen wrote:
- Original Message -
From: Bryan W. Headley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 9:43 PM
Subject: Re: XInput: The device type in XListInputDevices comes up again...
Cut a bit of code
The problem is, there's a type field and a name
:-)
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
-types. Is it possible to
have more?
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Egbert Eich wrote:
Bryan W. Headley writes:
[EMAIL PROTECTED] wrote:
{
_XDeviceInfo* device_list = XListInputDevices(display, n);
if (device_list[a].type == XInternAtom(display, XI_TABLET, true))
{
printf(Device %s is a tablet, device_list[a].name
W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
issues.
Excuse my stupidity, why are you not using GetTimeInMillis?
OTOH, we could wait for the message passing in Xext to extend to input
drivers, as I have read somewhere there is someone working on it.
How's progress with that?
--
.:.
Bryan W. Headley
, I don't see where you get to
specify WHICH device you are writing to. Every device driver serving
Display* x, screen y?
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http
Rafa³ Rzepecki wrote:
On Tuesday 12 of August 2003 16:53, Bryan W. Headley wrote:
I'm working on mouse.c personally, trying to add cordless mouse status
reporting and some cordless-specific runtime control, such as RF channel
switching. Unfortunately the only way I've found to communicate
...
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
for this. Anyone else working on this that I can share
ideas/complaints with?
Bryan
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
to pass along hardware insertion/removal events generated
by hotplug. So there's some infrastructure there already: the question
is whether leveraging off of that is a good way to go...
Any guilty heads out there?
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
Guys,
What's the procedure to submit code for approval in next roll of XF86? I
saw some code being attached to email, but wasn't sure if that's what
you like...
Bryan
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
stupid
questions until everyone feels comfortable with each other.
Do we have a volunteer to ask/answer dumb questions from we newbies?
--
.:.
Bryan W. Headley - [EMAIL PROTECTED]
___
Devel mailing list
[EMAIL
the line to:
id:2:initdefault:
I don't know if RedHat also uses '2'
Level 3, I thought.
After rebooting you can login and configure your graphics card as usual.
Hope that helps.
--
.:.
Bryan W. Headley - [EMAIL PROTECTED
47 matches
Mail list logo
