On Tue, Jul 14, 2020 at 12:15:37PM +0200, Frederic Cambus wrote:
> The diff makes sense to me, I will commit it this week with some minor
> style(9) fixes for the switch statement (don't indent the case), unless
> I hear objections.
Committed, thanks again!
On Sun, Jul 12, 2020 at 07:16:13PM +0200, Frederic Cambus wrote:
> On Fri, Jun 26, 2020 at 07:42:50AM -0700, jo...@armadilloaerospace.com wrote:
> > Optimized 32 bit character rendering with unrolled rows and pairwise
> > foreground / background pixel rendering.
> >
> > If it weren't for the 5x8
On Fri, Jun 26, 2020 at 07:42:50AM -0700, jo...@armadilloaerospace.com wrote:
> Optimized 32 bit character rendering with unrolled rows and pairwise
> foreground / background pixel rendering.
>
> If it weren't for the 5x8 font, I would have just assumed everything
> was an even width and made the
and doesn't actually implement write-combining for mappings
with the BUS_SPACE_MAP_PREFETCHABLE flag set. So that has to be fixed
as well.
> ---- Original Message
> Subject: RE: [PATCH} Optimized rasops32 putchar
> From:
> Date: Sat, June 27, 2020 11:13 am
> To: "Mark Kettenis"
o that has to be fixed
as well.
> ---- Original Message
> Subject: RE: [PATCH} Optimized rasops32 putchar
> From:
> Date: Sat, June 27, 2020 11:13 am
> To: "Mark Kettenis"
> Cc: "tech@openbsd.org"
>
> I believe it is mapped as normally ca
drivers is to get fully hardware
accelerated drawing in X, there isn't any reason why they can't
support dumb framebuffer mappings as well.
Original Message
Subject: RE: [PATCH} Optimized rasops32 putchar
From:
Date: Sat, June 27, 2020 11:13 am
To: "Mark Kettenis"
prefetching kicking in and
reading the following cacheline.
Original Message
Subject: Re: [PATCH} Optimized rasops32 putchar
From: Mark Kettenis
Date: Sat, June 27, 2020 7:56 am
To:
Cc: tech@openbsd.org
> From:
> Date: Fri, 26 Jun 2020 07:42:50 -0700
>
> Opti
> From:
> Date: Fri, 26 Jun 2020 07:42:50 -0700
>
> Optimized 32 bit character rendering with unrolled rows and pairwise
> foreground / background pixel rendering.
>
> If it weren't for the 5x8 font, I would have just assumed everything
> was an even width and made the fallback path also
Optimized 32 bit character rendering with unrolled rows and pairwise
foreground / background pixel rendering.
If it weren't for the 5x8 font, I would have just assumed everything
was an even width and made the fallback path also pairwise.
In isolation, the 16x32 character case got 2x faster, but
