From: Jon Smirl <jonsmirl@gmail.com>
To: kenoti maembe <kenotimaembe@gmail.com>,
James Simmons <jsimmons@www.infradead.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Virtual Terminal switching problem with a 2.6.10 kernel with a ruby patch
Date: Thu, 9 Jun 2005 13:51:20 -0400 [thread overview]
Message-ID: <9e4733910506091051311d2d47@mail.gmail.com> (raw)
In-Reply-To: <396a6e000506090749265a5066@mail.gmail.com>
On 6/9/05, kenoti maembe <kenotimaembe@gmail.com> wrote:
> Am working on a dual head project for my final year project at the
> university of nairobi in kenya and come across a discussion where it
> was stated that the linux kernel (by then 2.4) does not allow for two
> or more virtual terminals to exist concurrently..I have a few
> questions I would like to ask
> 1. Is this still the case with the 2.6 kernel? Thought of working
> through these by creating a new XFree86 and using the XFree86
> prefbusid patch from.from http://www.ltn.lv/~aivils/ bt still only one
> vt works at a time.
> 2. Have tried to assign devices to the different vts but cant seemt to
> get a way to assign the usb keyboard.All input device modules and usb
> modules are load in the kernel so dont understand what the issue is.
You need the ruby kernel patch set to support multiple VTs.
http://linuxconsole.sourceforge.net/
http://linuxconsole.bkbits.net/
There are also patches for supporting multiple video cards/users from
X but I don't know where they are. Ask on the x.org list or James will
know.
I'm not sure how multiple keyboards are handled in ruby. For Xegl I am
using the new evdev interface.
http://www.frogmouth.net/hid-doco/c537.html for examples.
Dealing with multiple video cards is very challenging especially
without the hardware documentation.
For a different project you might want to try implementing the EGL
interface on a 3D card. Documentation for ATI Rage128 and Mach64 (no
one is working on these) is available so if you could get your hands
on a PCI version (about $30) of one of those you'd be set. You want a
PCI version for target debug, then you run X and your debugger on the
Nvidia AGP card.
http://mesa3d.sf.net
http://lists.freedesktop.org/mailman/listinfo/dri-egl
Implementing EGL is more narrow in scope and should be easier to do.
EGL forms the basis of Xegl which is the new 3D accelerated X server.
> CPU: Athlon 1200+
> RAM: 384Mb
> Videocards: NVIDIA GeForce4 MX 440 (AGP), S3 Tio (PCI)
> Motherboard: Via
> Keyboards: one PS/2 keyboards, one USB keyboard
> Mice: one serial, one USB
> Monitors: 17'', 15''
> on a mandrake 10.0
>
> Thank you all.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
prev parent reply other threads:[~2005-06-09 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <396a6e00050608091524b97479@mail.gmail.com>
2005-06-09 14:49 ` Fwd: Virtual Terminal switching problem with a 2.6.10 kernel with a ruby patch kenoti maembe
2005-06-09 17:51 ` Jon Smirl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4733910506091051311d2d47@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=jsimmons@www.infradead.org \
--cc=kenotimaembe@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.