On Friday 04 May 2007 11:34:40 Jesse Barnes wrote:
> On Thursday, May 03, 2007, Antonino A. Daplas wrote:
> > On Thu, 2007-05-03 at 23:58 -0400, Daniel Hazelton wrote:
> > > On Thursday 03 May 2007 20:39:05 H. Peter Anvin wrote:
> > > > Kyle Moffett wrote:
> > >
> > > I guess I could start on that
On Thursday, May 03, 2007, Antonino A. Daplas wrote:
> On Thu, 2007-05-03 at 23:58 -0400, Daniel Hazelton wrote:
> > On Thursday 03 May 2007 20:39:05 H. Peter Anvin wrote:
> > > Kyle Moffett wrote:
> >
> > I guess I could start on that work again - shouldn't take me all that
> > long to recover the
On Thu, 2007-05-03 at 23:58 -0400, Daniel Hazelton wrote:
> On Thursday 03 May 2007 20:39:05 H. Peter Anvin wrote:
> > Kyle Moffett wrote:
> I guess I could start on that work again - shouldn't take me all that long to
> recover the stuff I lost when a blackout caused my hard drive to get
> corr
On Thursday 03 May 2007 20:39:05 H. Peter Anvin wrote:
> Kyle Moffett wrote:
> > Actually I think the real problem was that "KD_GRAPHICS" got overloaded
> > to mean "some userspace program is probably poking at the GPU in very
> > direct ways possibly including /dev/mem". As such it really isn't s
Kyle Moffett wrote:
>
> Actually I think the real problem was that "KD_GRAPHICS" got overloaded
> to mean "some userspace program is probably poking at the GPU in very
> direct ways possibly including /dev/mem". As such it really isn't safe
> at all for the kernel to write stuff to the screen in
On May 03, 2007, at 16:16:51, Jan Engelhardt wrote:
On May 3 2007 13:15, H. Peter Anvin wrote:
Jan Engelhardt wrote:
Put people didn't like that, and disabled text output when the
console is in KD_GRAPHICS mode...
at the cost of not getting the kernel oops, heh.
I thought the reason we d
On May 3 2007 13:15, H. Peter Anvin wrote:
>Jan Engelhardt wrote:
>>
>>> Put people didn't like that, and disabled text output when the console
>>> is in KD_GRAPHICS mode...
>>
>> at the cost of not getting the kernel oops, heh.
>
>I thought the reason we didn't display text in KD_GRAPHICS mode
Jan Engelhardt wrote:
>
>> Put people didn't like that, and disabled text output when the console
>> is in KD_GRAPHICS mode...
>
> at the cost of not getting the kernel oops, heh.
>
I thought the reason we didn't display text in KD_GRAPHICS mode was that
KD_GRAPHICS might mean "in a completely
On May 3 2007 17:56, Geert Uytterhoeven wrote:
>>
>> Actually, the kernel could just "jump in". That is, when you start
>> in fb mode, you get the regular 8x16 vga font - on your choice of
>> resolution, and can also set it with setfont. So far so nice.
>> Now, when you start fbiterm -- for examp
On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
> I'm having problems with a font I just created. It's a rather big one,
> intended for a framebuffer console in UTF-8 mode. The strace program
> reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
> In reading the kernel
On Thu, 3 May 2007, Jan Engelhardt wrote:
> On May 3 2007 10:14, Albert Cahalan wrote:
> > On 5/3/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> >> On May 3 2007 02:17, Albert Cahalan wrote:
> >
> >> > Those sizes are unreadable on the 200 dpi OLPC XO screen,
On May 3 2007 10:14, Albert Cahalan wrote:
> On 5/3/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>> On May 3 2007 02:17, Albert Cahalan wrote:
>
>> > Those sizes are unreadable on the 200 dpi OLPC XO screen,
>>
>> Hm that should have read, for you:
>> I don't object implementing support for larg
On 5/3/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On May 3 2007 02:17, Albert Cahalan wrote:
> Those sizes are unreadable on the 200 dpi OLPC XO screen,
Hm that should have read, for you:
I don't object implementing support for larger sizes.
(But I wonder how that should work without FB/CV
On Thu, 03 May 2007 00:19:59 -0700
"H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
> Albert Cahalan wrote:
> > Font size is not a sane place to draw the line. Features are.
>
> Font sizes are an eminently sane place to draw the line, because the
> crossover is largely determined by the point at which
H. Peter Anvin wrote:
Albert Cahalan wrote:
Font size is not a sane place to draw the line. Features are.
Font sizes are an eminently sane place to draw the line, because the
crossover is largely determined by the point at which nailing down too
much memory (kernel memory = unswappable
Albert Cahalan wrote:
> Font size is not a sane place to draw the line. Features are.
Font sizes are an eminently sane place to draw the line, because the
crossover is largely determined by the point at which nailing down too
much memory (kernel memory = unswappable memory) gets too expensive.
On May 3 2007 02:17, Albert Cahalan wrote:
> Note: I never suggested going beyond #3.
>
>> 0. yes we want that
>>
>> 1. can't tell
>>
>> 2. utf8 yes, many text files are in that encoding.
>> large fonts - can't tell, I am fine with the regular vga
>> font infrastructure (8x16, 8x8)
>
> Those siz
On 5/2/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On May 1 2007 11:49, Albert Cahalan wrote:
>>
>> Well, I think the consensus is that anything beyond that should be done
>> in userspace; the main such console daemon was Kon2 last I checked.
>
> Font size is not a sane place to draw the line.
On May 1 2007 11:49, Albert Cahalan wrote:
>>
>> Well, I think the consensus is that anything beyond that should be done
>> in userspace; the main such console daemon was Kon2 last I checked.
>
> Font size is not a sane place to draw the line. Features are.
> The levels of support go something lik
On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
>
> BTW, the PSF font format documentation seems to suggest that
> there is a way to make the kernel handle combining accents:
> http://www.win.tue.nl/~aeb/linux/kbd/font-formats-1.html
> Does anybody know if that really works? I coul
On 5/1/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
Antonino A. Daplas wrote:
>
> And this will entail a lot of work to change (Is it worth it to rework
> the code and remove the limitation?). The linux-console project
> (http://linuxconsole.sourceforge.net/) might have , but I don't know its
>
Antonino A. Daplas wrote:
>
> And this will entail a lot of work to change (Is it worth it to rework
> the code and remove the limitation?). The linux-console project
> (http://linuxconsole.sourceforge.net/) might have , but I don't know its
> current status.
>
Well, I think the consensus is tha
On Tue, 2007-05-01 at 13:49 +0200, Geert Uytterhoeven wrote:
> On Tue, 1 May 2007, Albert Cahalan wrote:
> > I'm having problems with a font I just created. It's a rather big one,
> > intended for a framebuffer console in UTF-8 mode. The strace program
> > reports that /bin/setfont fails on a KDFON
On Tue, 1 May 2007, Albert Cahalan wrote:
> I'm having problems with a font I just created. It's a rather big one,
> intended for a framebuffer console in UTF-8 mode. The strace program
> reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
> In reading the kernel code, I find this:
>
24 matches
Mail list logo
