Hi,
I just update my box. I confirm too that r270322 fixed the problem.
Thanks for fix it,
--
Carlos Jacobo Puga Medina
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any m
On 22 August 2014 01:47, Jean-Sébastien Pédron
wrote:
> On 19.08.2014 18:28, Jean-Sébastien Pédron wrote:
>>
>> Here's a first version of the patch I was talking about:
>> https://people.freebsd.org/~dumbbell/vt/vt-vga.5.patch
>
>
> This is now in HEAD, as of r270322. Again, this is unfinished wor
On 19.08.2014 18:28, Jean-Sébastien Pédron wrote:
Here's a first version of the patch I was talking about:
https://people.freebsd.org/~dumbbell/vt/vt-vga.5.patch
This is now in HEAD, as of r270322. Again, this is unfinished work, but
it already brings improvements.
--
Jean-Sébastien Pédron
_
Hi,
On 19 August 2014 12:40, Jean-Sébastien Pédron wrote:
> On 19.08.2014 21:20, Adrian Chadd wrote:
>> Hey, this is cool!
>>
>> So hm, why are you still doing any reading? Don't you now have all the
>> information you need to write out the font and cursor information for
>> each given set of 8
On 08/19/14 12:02, Jean-Sébastien Pédron wrote:
On 19.08.2014 19:46, Nathan Whitehorn wrote:
On 08/19/14 09:28, Jean-Sébastien Pédron wrote:
o vt_vga introduces a new callback, vd_bitblt_text_t, which takes
as argument the text buffer, the dirty area, the font and the
On 19.08.2014 21:20, Adrian Chadd wrote:
> Hey, this is cool!
>
> So hm, why are you still doing any reading? Don't you now have all the
> information you need to write out the font and cursor information for
> each given set of 8 pixels?
I read a lot about VGA in the past days but I'm new to thi
Hey, this is cool!
So hm, why are you still doing any reading? Don't you now have all the
information you need to write out the font and cursor information for
each given set of 8 pixels?
-a
___
freebsd-current@freebsd.org mailing list
http://lists.fre
On 19.08.2014 19:46, Nathan Whitehorn wrote:
> On 08/19/14 09:28, Jean-Sébastien Pédron wrote:
>> o vt_vga introduces a new callback, vd_bitblt_text_t, which takes
>> as argument the text buffer, the dirty area, the font and the
>> cursor (position, map, colors).
>
> Why is th
On 08/19/14 09:28, Jean-Sébastien Pédron wrote:
On 19.08.2014 10:42, Jean-Sébastien Pédron wrote:
On 16.08.2014 01:51, Nathan Whitehorn wrote:
It also has bad effects on boot time. My desktop takes something like 3
times as long to boot after r269471. If it can't be fixed quickly, it
needs to
On 19.08.2014 10:42, Jean-Sébastien Pédron wrote:
> On 16.08.2014 01:51, Nathan Whitehorn wrote:
>> It also has bad effects on boot time. My desktop takes something like 3
>> times as long to boot after r269471. If it can't be fixed quickly, it
>> needs to be reverted.
>
> Just a quick note: I'm w
On 16.08.2014 01:51, Nathan Whitehorn wrote:
> It also has bad effects on boot time. My desktop takes something like 3
> times as long to boot after r269471. If it can't be fixed quickly, it
> needs to be reverted.
Just a quick note: I'm working on an update to vt_vga. The current patch
already fi
It also has bad effects on boot time. My desktop takes something like 3
times as long to boot after r269471. If it can't be fixed quickly, it
needs to be reverted.
-Nathan
On 08/15/14 15:27, Adrian Chadd wrote:
keep in mind that the vt_vga code will be used for new VGA bring-up on
hardware tha
keep in mind that the vt_vga code will be used for new VGA bring-up on
hardware that exposes legacy VGA bits and pieces, at least until EFI
booting is guaranteed everywhere. Trying to do development on the
console of something using the current vt_vga in order to bring up
things like an ethernet dr
On Tue, 12 Aug 2014 23:28:07 +0200
Carlos Jacobo Puga Medina wrote:
> > I believe it's still broken. There's a related PR at
> > http://bugs.freebsd.org/192452 and, I suspect, 192456. Aleksandr, would
> > you mind reverting this reversion? It seems to have created a lot of
> > problems.
> > -N
> I believe it's still broken. There's a related PR at
> http://bugs.freebsd.org/192452 and, I suspect, 192456. Aleksandr, would
> you mind reverting this reversion? It seems to have created a lot of
> problems.
> -Nathan
Yes, I think that ray@ is around here somewhere to fix this :P
Regards,
15 matches
Mail list logo