The Xfree86 for NTO as Igor posted on qnxfree.sourceforge.net
only supports serial mouse. Now that we have inputtrap with RTP,
I am thinking of using it so that Xfree86 can support all the mice
that inputtrap supports. This is actually what Xfree86 for QNX4
is doing.
I tried inputtrap start on the text console and get:
devi-hirun kbd fd -d/dev/kbd msoft -3 -R fd -d /dev/ser1
PhOpen at “/home/vanmarle/cvs/photon/devi/lib/photon.c”:255: No such file or directory
Error in connecting to Photon device
It seems RTP’s inputtrap is tightly linked with Photon. Can
you make it de-coupled, like QNX4’s inputtrap?
I think that was planned, at least someone from QNX mentioned it would
be done. Need for that is not very high if people will use
Photon/Xphoton however.
I’m wondering how attractive would be idea to use QNX OS runtime coupled
with Xfree86 and some desktop environment (Gnome/KDE) to form a
‘Linux-like’ distribution. In fact I had such environment (based on beta
NTO2.0 runtime) some time before RTP or even Augusta was released in any
form. Xfree, WindowMaker, self-hosted GCC 2.8.1 plus some toys like
xmcd… they are still somewhere on my hard drive.
I kinda doubt QSSL would like such scenario though
igor
Frank Liu wrote:
The Xfree86 for NTO as Igor posted on qnxfree.sourceforge.net
only supports serial mouse. Now that we have inputtrap with RTP,
I am thinking of using it so that Xfree86 can support all the mice
that inputtrap supports. This is actually what Xfree86 for QNX4
is doing.
I tried inputtrap start on the text console and get:
devi-hirun kbd fd -d/dev/kbd msoft -3 -R fd -d /dev/ser1
PhOpen at “/home/vanmarle/cvs/photon/devi/lib/photon.c”:255: No such file or directory
Error in connecting to Photon device
It seems RTP’s inputtrap is tightly linked with Photon. Can
you make it de-coupled, like QNX4’s inputtrap?
It seems RTP’s inputtrap is tightly linked with Photon. Can
you make it de-coupled, like QNX4’s inputtrap?
We will be redesigning the way input devices (console and mouse) work
so that the code that talks to the raw devices stands alone.
The practical consequence of this is that devc-con will not have any code
in it at all to talk to the 8042 PS/2 controller, and neither will the Photon
input driver.
There will be something like a devc-8042 device that will create a /dev/kbd
and a /dev/aux if there is a mouse attached. The upcoming USB stack will
also create similar devices if you have USB keyboard/mice attached.
Serial mice are already handled by /dev/ser
devc-con will be changed to talk to the /dev/kbd device, which should also
allow us to support international keyboards right from login
You suggest that inputtrap is coupled to photon, and that is not the case.
It’s input itself that is coupled to Photon. devi-hirun will probably go
away and be replaced with something like a devi-photon so that at least you know it is coupled to Photon.
Any kind of xfree86 solution would have to be done by an interested outside
party, but the pieces needed to do so will be there.
The redesign I’m talking about is just starting now, and will probably not
be available until early next year.
It seems RTP’s inputtrap is tightly linked with Photon. Can
you make it de-coupled, like QNX4’s inputtrap?
We will be redesigning the way input devices (console and mouse) work
so that the code that talks to the raw devices stands alone.
The practical consequence of this is that devc-con will not have any code
in it at all to talk to the 8042 PS/2 controller, and neither will the Photon
input driver.
There will be something like a devc-8042 device that will create a /dev/kbd
and a /dev/aux if there is a mouse attached. The upcoming USB stack will
also create similar devices if you have USB keyboard/mice attached.
Serial mice are already handled by /dev/ser
devc-con will be changed to talk to the /dev/kbd device, which should also
allow us to support international keyboards right from login
You suggest that inputtrap is coupled to photon, and that is not the case.
It’s input itself that is coupled to Photon. devi-hirun will probably go
away and be replaced with something like a devi-photon so that at least you know it is coupled to Photon.
Any kind of xfree86 solution would have to be done by an interested outside
party, but the pieces needed to do so will be there.
The redesign I’m talking about is just starting now, and will probably not
be available until early next year.
It seems RTP’s inputtrap is tightly linked with Photon. Can
you make it de-coupled, like QNX4’s inputtrap?
We will be redesigning the way input devices (console and mouse) work
so that the code that talks to the raw devices stands alone.
The practical consequence of this is that devc-con will not have any code
in it at all to talk to the 8042 PS/2 controller, and neither will the Photon
input driver.
There will be something like a devc-8042 device that will create a /dev/kbd
and a /dev/aux if there is a mouse attached. The upcoming USB stack will
also create similar devices if you have USB keyboard/mice attached.
Serial mice are already handled by /dev/ser
devc-con will be changed to talk to the /dev/kbd device, which should also
allow us to support international keyboards right from login
You suggest that inputtrap is coupled to photon, and that is not the case.
It’s input itself that is coupled to Photon. devi-hirun will probably go
away and be replaced with something like a devi-photon so that at least you know it is coupled to Photon.
Any kind of xfree86 solution would have to be done by an interested outside
party, but the pieces needed to do so will be there.
The redesign I’m talking about is just starting now, and will probably not
be available until early next year.
