Re: port-amd64/54808: Visual artifacts in Firefox after bus_space changes

[David Brownlee <abs%absd.org@localhost>]

The following reply was made to PR port-amd64/54808; it has been noted by GNATS.

From: David Brownlee <abs%absd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	netbsd-bugs%netbsd.org@localhost
Subject: Re: port-amd64/54808: Visual artifacts in Firefox after bus_space changes
Date: Sun, 29 Dec 2019 20:46:36 +0000

 Well I've just booted a netbsd-9 kernel with BUS_SPACE_MAP_CACHEABLE
 instead of BUS_SPACE_MAP_PREFETCHABLE and no other changes apart from
 +DIAGNOSTIC (so the bus_space as-is on netbsd-9), and its looking
 good...
 
 Thanks
 
 David
 
 On Sun, 29 Dec 2019 at 19:05, <coypu%sdf.org@localhost> wrote:
 >
 > The following reply was made to PR port-amd64/54808; it has been noted by GNATS.
 >
 > From: coypu%sdf.org@localhost
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: port-amd64/54808: Visual artifacts in Firefox after bus_space
 >  changes
 > Date: Sun, 29 Dec 2019 19:04:21 +0000
 >
 >  I see some cases where the cache behaviour of memory for NetBSD differs
 >  from the upstream, linux ones. I wonder if it can help to make them
 >  match.
 >
 >  sys/external/bsd/drm2/dist/drm/i915/intel_opregion.c
 >
 >
 >  #ifdef __NetBSD__ ... write-combining
 >         err = -bus_space_map(opregion->bst, asls, OPREGION_SIZE,
 >                     BUS_SPACE_MAP_LINEAR|BUS_SPACE_MAP_PREFETCHABLE, &opregion->bsh);
 >
 >  #else
 >         base = memremap(asls, OPREGION_SIZE, MEMREMAP_WB);
 >  #endif
 >
 >  jared states an equivalent to MEMREMAP_WB is BUS_SPACE_MAP_CACHEABLE.
 >