On Wed, Feb 13, 2002 at 08:39:14PM +0100, Diego Roversi wrote:
> Have you take a look to SuperVGATextMode?
Yes, I know it (and use it actually). However, as the name suggests, it
uses SVGA. SGVA is different from card to card, and I will not burden
myself with that. I think I have all the info
On Thu, Feb 14, 2002 at 11:38:30PM +0100, Niels Möller wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > Esp with the input below, I feel much better about Unicode now (although
> > I would not like to support the whole lot of it right from the
> > start, esp the compose characters A +
On Thu, Feb 14, 2002 at 04:12:32PM -0500, Roland McGrath wrote:
> > I thought there might be problems because the UTF-8 encoding is multi-byte.
> > I don't see a problem with transfering UTF-8 data through our system (that's
> > what UTF-8 is about), but I thought term and maybe other things need
On Thu, Feb 14, 2002 at 11:42:18PM +0100, Niklas Höglund wrote:
> I think there is a program for the Linux console that does this. I
> remember seing this a while ago. I did a quick search in apt-cache,
> and found dynafont. I'm not sure if this is the program I remember,
> though. I couldn't find
[EMAIL PROTECTED] (Niels Möller) writes:
[removed a good insight in unicode<->char-code translation]
>
> > But using X for telling how to get characters from keyboard scancodes
> > to Unicode is compatible with using Unicode internaly.
>
> Huh? I don't understand you. My point is that it is e
Anders Jackson <[EMAIL PROTECTED]> writes:
> > For the input part, the complexity hits whatever component it is that
> > converts unicode or utf8 to a local charset like latin1 (and given the
> > current level of support for utf8 in tools like emacs and TeX, I don't
> > think eightbit charsets wi
[EMAIL PROTECTED] (Niels Möller) writes:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > Esp with the input below, I feel much better about Unicode now (although
> > I would not like to support the whole lot of it right from the
> > start, esp the compose characters A + ["] = Ä and stuff li
On Thu, Feb 14, 2002 at 11:46:56PM +0100, Niels Möller wrote:
> I.e. the responsibility for sane gfx state should be in some
> privileged process. A non-privileged user should not be able to shoot
> it down (but he should still be able to kill his own X server, and
> certainly his fb applications,
On Tue, Feb 12, 2002 at 10:20:42PM +0100, Marcus Brinkmann wrote:
Hello,
just my 2c tips:
> The output half is similar. The only driver initially will be a standard
> VGA driver (Super VGA might be an option for later). I have found some
> documentation on VGA cards (FreeVGA Project), and w
> Ok, I understand if that is the current goal, but I think the Right
> Thing should (1) behave in a sane way if the X server is kill -9:ed
> (i.e. cleanup bound to a no-senders notification somewhere), and (2)
> support arbitrary frame buffer applications in a simple and robust
> way.
I think X
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> If you have the console server and X as the only players, the
> mentioned protocol ensures that X can safely grab control over the
> graphic card and the keyboard (the console server might in fact act
> as an repeater for the keyboard input on /dev/k
On Thu, Feb 14, 2002 at 08:53:24PM +, Adam Olsen wrote:
>
> On Thu, Feb 14, 2002 at 09:14:05PM +0100, Marcus Brinkmann wrote:
> > [...] The interesting way is to prescan as much
> > characters as available, and, taking all the characters into account that
> > are visible on the screen at that
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> Esp with the input below, I feel much better about Unicode now (although
> I would not like to support the whole lot of it right from the
> start, esp the compose characters A + ["] = Ä and stuff like that).
Yes, unicode is a lot more complex than o
> The console seems to be the natural place where you configure the system
> wide default encoding. I am not sure how an alternative would look like.
> Where would the actual conversion took place if we were to use UTF-8
> unconditionally?
There would be no conversion on input in any part of the
On Thu, Feb 14, 2002 at 09:14:05PM +0100, Marcus Brinkmann wrote:
> THAT makes me thinking! I am running out of time, but I just had this hell
> of an idea: If we would use UTF-8 throughout, we would end up with the vga
> backend receiving UTF-8 characters. Now it can do one of two things: The
Hi,
thanks for your reply, it is very useful. I am on the jump between two
conferences, so I can not do the research right now, but some comments
I can make right now.
On Wed, Feb 13, 2002 at 04:36:31AM -0500, Roland McGrath wrote:
> > * A kernel driver to get the keyboard events from. To redu
On Wed, Feb 13, 2002 at 10:56:45AM +0100, Niels Möller wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> > The output half is similar. The only driver initially will be a standard
> > VGA driver (Super VGA might be an option for later). I have found some
> > documentation on VGA cards (Fre
> Do you have a plan for how to coordinate access to the hardware with
> other programs, like framebuffers and X?
Ah, this is something I forgot about. There are existing ioctl interfaces
for this on Linux and BSD (linux/vt.h, sys/consio.h) that are almost the
same on the two platforms. So we m
Sounds cool.
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> The output half is similar. The only driver initially will be a standard
> VGA driver (Super VGA might be an option for later). I have found some
> documentation on VGA cards (FreeVGA Project), and we will do all the VGA
> card progra
> I am preparing for the console server
You're the man.
> * A kernel driver to get the keyboard events from. To reduce kernel code,
> raw scan code events will be consumed in the ix86 version.
> Status: GNU Mach can provide them, I have a hack for OSKit-Mach here that
> needs to be polish
On Tue, Feb 12, 2002 at 10:20:42PM +0100, Marcus Brinkmann wrote:
> What needs to be done:
* Backend drivers for the MAC of course! (But not by me)
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNUhttp://www.gnu.org
Hi,
I am preparing for the console server, and here is sort of a rough outline,
call for comments, requests, and opinions, as well as some update on the
status.
The console will be built of several parts:
* A kernel driver to get the keyboard events from. To reduce kernel code,
raw scan code
22 matches
Mail list logo
