h petsc.
>
> I see an effort to migrate scotch build in petsc to cmake
>
> https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7242/__;!!G_uCfscf7eWS!axLWsOWdCnVQSjIurDkWvFmG4riOizNNPbVM78TQoVScHx7ERMUENiQ-VW2Lh5e83QHhKcA7-HO0nDJ_hTez8JffqQz8h1I$
>
> https://urld
Hi Joao,
On Fri, 26 Apr 2024 at 08:42, Joao Paulo Silva Goncalves
wrote:
> On Thu, Apr 25, 2024 at 9:08 AM Lucas Stach wrote:
> > I can reproduce the issue, but sadly there is no simple fix for this,
> > as it's a bad interaction between some of the new features.
> > At the core of the issue is
On Thu, 25 Apr 2024 at 13:08, Lucas Stach wrote:
> I can reproduce the issue, but sadly there is no simple fix for this,
> as it's a bad interaction between some of the new features.
> At the core of the issue is the dmabuf-feedback support with the chain
> of events being as follows:
>
> 1.
Hi PETSc community,
I've been looking at using Spack to build PETSc, in particular I need to
disable the default metis/parmetis dependencies and use PTScotch instead,
for our software.
I've had quite a bit of trouble with this - it seems like something in the
resulting build of our simulator ends
Hi all,
After a bit of a period of inactivity, Matthias Klumpp has agreed to help
update and maintain the XDG specs, including the menu and icon-theme specs in
particular.
If you have any suggestions or anything you want addressed, please discuss it
on the list, or file an issue or merge
/HEIGHT caps, which can only declare
> a one size fits all limit for the whole device.
Acked-by: Daniel Stone
Cheers,
Daniel
/HEIGHT caps, which can only declare
> a one size fits all limit for the whole device.
Acked-by: Daniel Stone
Cheers,
Daniel
On Mon, 26 Feb 2024 at 12:03, Jani Nikula wrote:
> On Mon, 26 Feb 2024, Daniel Stone wrote:
> > It's a fair question. If you want to verify that someone is
> > @intel.com, maybe get them to email you out-of-band to check it. If
> > you want to check something else, just a
On Mon, 26 Feb 2024 at 11:57, Jani Nikula wrote:
> On Mon, 26 Feb 2024, Maxime Ripard wrote:
> > For the recent-ish subscriptions, it's possible since we've required to
> > open a Gitlab issue for a while, so we have the association between the
> > Gitlab account and the SSH account already.
> >
Hi,
On Mon, 26 Feb 2024 at 03:21, Lucas De Marchi wrote:
> All of this should be fixed by now: dim is used for applying and pushing
> patches, which has additional checks so that doesn't happen again. Still
> pending confirmation from Daniel Stone if the git server hooks are ready
>
Hi,
On Mon, 26 Feb 2024 at 03:21, Lucas De Marchi wrote:
> All of this should be fixed by now: dim is used for applying and pushing
> patches, which has additional checks so that doesn't happen again. Still
> pending confirmation from Daniel Stone if the git server hooks are ready
>
Hi,
On Mon, 26 Feb 2024 at 03:21, Lucas De Marchi wrote:
> All of this should be fixed by now: dim is used for applying and pushing
> patches, which has additional checks so that doesn't happen again. Still
> pending confirmation from Daniel Stone if the git server hooks are ready
>
Hi Stephen,
On Tue, 20 Feb 2024 at 22:46, Stephen Rothwell wrote:
> On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone wrote:
> > cc sfr - once we move the DRM repos to a different location, what's
> > the best way to update linux-next?
>
> These are (I think) all the drm
On Tue, 20 Feb 2024 at 09:05, Maxime Ripard wrote:
> On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > This will be mostly transparent to current committers and users: we'll
> > still use dim, in the exact same way, the only change will be the URL of
> > the repo. This will also
Hi,
On Fri, 16 Feb 2024 at 09:00, Tomi Valkeinen
wrote:
> On 13/02/2024 13:39, Daniel Stone wrote:
> > Specifically, you probably want commits 4cde507be6a1 and 58dde0e0c000.
> > I think the window of breakage was small enough that - assuming either
> > those commits or an up
Hi,
On Fri, 16 Feb 2024 at 09:00, Tomi Valkeinen
wrote:
> On 13/02/2024 13:39, Daniel Stone wrote:
> > Specifically, you probably want commits 4cde507be6a1 and 58dde0e0c000.
> > I think the window of breakage was small enough that - assuming either
> > those commits or an up
Hi,
On Tue, 13 Feb 2024 at 10:18, Marius Vlad wrote:
> On Tue, Feb 13, 2024 at 11:57:59AM +0200, Tomi Valkeinen wrote:
> > I haven't. I'm quite unfamiliar with Weston, and Randolph from TI (cc'd) has
> > been working on the Weston side of things. I also don't know if there's
> > something TI
Hi,
On Tue, 13 Feb 2024 at 10:18, Marius Vlad wrote:
> On Tue, Feb 13, 2024 at 11:57:59AM +0200, Tomi Valkeinen wrote:
> > I haven't. I'm quite unfamiliar with Weston, and Randolph from TI (cc'd) has
> > been working on the Weston side of things. I also don't know if there's
> > something TI
On Wed, 31 Jan 2024 at 02:31, Zack Rusin wrote:
> On Tue, Jan 30, 2024 at 6:50 PM Daniel Stone wrote:
> > The entire model we have is that basis timing flows backwards. The
> > 'hardware' gives us a deadline, KMS angles to meet that with a small
> > margin, the comp
Hi,
On Tue, 30 Jan 2024 at 18:39, Zack Rusin wrote:
> In general, yes. Of course it's a little more convoluted because we'll
> act like OpenGL runtime here (i.e. glXSwapBuffers), i.e. our driver
> will fake page-flips because the only memory we'll have is a single
> buffer as the actual
Hi Lucas,
On Fri, 26 Jan 2024 at 17:00, Lucas Stach wrote:
> The dma sync operation needs to be done with DMA_BIDIRECTIONAL when
> the BO is prepared for both read and write operations. With the
> current inverted if ladder it would only be synced for DMA_FROM_DEVICE.
>
> [...]
>
> static
On Fri, 26 Jan 2024 at 00:22, Faith Ekstrand wrote:
> On Thu, Jan 25, 2024 at 5:06 PM Gert Wollny wrote:
>> I think with Venus we are more interested in using utility libraries on
>> an as-needed basis. Here, most of the time the Vulkan commands are just
>> serialized according to the Venus
the transient seat protocol
Daniel Stone (1):
build: Bump version to 1.33
Jonas Ådahl (1):
xdg-shell: Clarify what a toplevel by default includes
Lleyton Gray (1):
staging/drm-lease: fix typo in description
MaxVerevkin (1):
linux-dmabuf: sync changes from unstable to stable
Hi Matt,
On Wed, 17 Jan 2024 at 17:08, Matt Hoosier wrote:
> Does anybody know whether there’s a dedicated mailing list suitable for
> asking questions about the hardware acceleration in the remote desktop
> use-case for those two?
>
> I did a quick look through both repos’ README and
Hi Vignesh,
On Tue, 16 Jan 2024 at 09:55, Vignesh Raman wrote:
> Rename the name of xfail files for mediatek (mt8173 and mt8183),
> to include information about the tested driver and update xfails
> accordingly. Since the correct driver name is passed from the job to
> test gpu and display
Hi Vignesh,
On Wed, 10 Jan 2024 at 10:47, Vignesh Raman wrote:
> On 09/01/24 19:08, Daniel Stone wrote:
> > A better sequencing would be something like:
> >1. add ANX7625 config
> >2. refactor _existing_ MTK display jobs to use YAML includes, change
> > the ex
Hi,
On Wed, 10 Jan 2024 at 10:44, Daniel Vetter wrote:
> On Tue, Jan 09, 2024 at 11:12:11PM +, Andri Yngvason wrote:
> > ţri., 9. jan. 2024 kl. 22:32 skrifađi Daniel Stone :
> > > How does userspace determine what's happened without polling? Will it
> > > only cha
Hi,
On Wed, 10 Jan 2024 at 10:44, Daniel Vetter wrote:
> On Tue, Jan 09, 2024 at 11:12:11PM +, Andri Yngvason wrote:
> > ţri., 9. jan. 2024 kl. 22:32 skrifađi Daniel Stone :
> > > How does userspace determine what's happened without polling? Will it
> > > only cha
Hi,
On Wed, 10 Jan 2024 at 10:44, Daniel Vetter wrote:
> On Tue, Jan 09, 2024 at 11:12:11PM +, Andri Yngvason wrote:
> > ţri., 9. jan. 2024 kl. 22:32 skrifađi Daniel Stone :
> > > How does userspace determine what's happened without polling? Will it
> > > only cha
Hi,
On Tue, 9 Jan 2024 at 18:12, Andri Yngvason wrote:
> + * active color format:
> + * This read-only property tells userspace the color format actually used
> + * by the hardware display engine "on the cable" on a connector. The
> chosen
> + * value depends on hardware
Hi,
On Tue, 9 Jan 2024 at 18:12, Andri Yngvason wrote:
> + * active color format:
> + * This read-only property tells userspace the color format actually used
> + * by the hardware display engine "on the cable" on a connector. The
> chosen
> + * value depends on hardware
Hi,
On Tue, 9 Jan 2024 at 18:12, Andri Yngvason wrote:
> + * active color format:
> + * This read-only property tells userspace the color format actually used
> + * by the hardware display engine "on the cable" on a connector. The
> chosen
> + * value depends on hardware
Hi,
On Wed, 20 Dec 2023 at 12:11, Vignesh Raman wrote:
> Some ARM SOCs have a separate display controller and GPU, each with
> different drivers. For mediatek mt8173, the GPU driver is powervr,
> and the display driver is mediatek. In the case of mediatek mt8183,
> the GPU driver is panfrost,
Hi Vignesh,
On Wed, 29 Nov 2023 at 12:19, Vignesh Raman wrote:
> Expected driver for mt8173 is "mediatek" and for mt8183
> it is "panfrost". Set IGT_FORCE_DRIVER to 'mediatek' as
> the expected driver for mt8173.
Actually, for mt8183 it's both. And for mt8173 it will probably be
mediatek+pvr
t [3]. IGT test available
> at [4].
Series is:
Reviewed-by: Daniel Stone
Hi Vignesh,
On Thu, 19 Oct 2023 at 09:07, Vignesh Raman wrote:
> +# Some tests crashes with malloc error and IGT tests floods
> +# the CI log with error messages and we end up with a warning message
> +# Job's log exceeded limit of 4194304 bytes.
> +# Job execution will continue but no more
Hi Vignesh,
On Thu, 19 Oct 2023 at 09:07, Vignesh Raman wrote:
> +# Some tests crashes with malloc error and IGT tests floods
> +# the CI log with error messages and we end up with a warning message
> +# Job's log exceeded limit of 4194304 bytes.
> +# Job execution will continue but no more
Hi Joe,
On Wed, 18 Oct 2023 at 02:00, Joe M wrote:
> A few questions:
> 1. What other avenues of investigation should I pursue for the swap delay?
> As in, why when I take 12 ms to render do I not see about 4ms for the swap
> call to return? My display is running in at 60hz.
Further to
Hi Shawn,
On Mon, 16 Oct 2023 at 06:23, Shawn Sung (宋孝謙) wrote:
> On Fri, 2023-10-13 at 17:26 +0100, Daniel Stone wrote:
> > If I understand the driver correctly, padding is automatically
> > applied
> > to compensate for unaligned dimensions. The first/last rows/columns
&
On Fri, 6 Oct 2023 at 18:32, Rob Clark wrote:
> ssh logging is the default for mesa, as it is generally more reliable.
> But if there are kernel issues, especially at boot, UART logging is
> infinitely more useful.
Hmm, we should still be capturing the UART boot logs regardless. Those
go into a
Hi Shawn,
On Fri, 6 Oct 2023 at 08:38, Hsiao Chien Sung wrote:
> + Padding provides ability to add pixels to width and height of a layer with
> + specified colors. Due to hardware design, Mixer in VDOSYS1 requires
> + width of a layer to be 2-pixel-align, or 4-pixel-align when ETHDR is
>
On Mon, 18 Sept 2023 at 23:02, Helen Koike wrote:
> On 14/09/2023 05:12, Daniel Vetter wrote:
> > Also yes how that landed without anyone running lockdep is ... not good. I
> > guess we need a lockdep enabled drm ci target that runs vkms tests asap
> > :-)
>
> btw, I just executed a draft version
Hi Jason, CK,
On Tue, 19 Sept 2023 at 04:04, Jason-JH.Lin wrote:
> The patch series provides drm driver support for enabling secure video
> path (SVP) playback on MediaiTek hardware in the Linux kernel.
>
> [...]
>
> Memory Usage in SVP:
> The overall flow of SVP starts with encrypted video
Hey,
On Thu, 14 Sept 2023 at 10:54, Maxime Ripard wrote:
> On Tue, Sep 12, 2023 at 02:16:41PM +0100, Daniel Stone wrote:
> > Hopefully less mangled formatting this time: turns out Thunderbird +
> > plain text is utterly unreadable, so that's one less MUA that is
> > actually
Hi Maxime,
Hopefully less mangled formatting this time: turns out Thunderbird +
plain text is utterly unreadable, so that's one less MUA that is
actually usable to send email to kernel lists without getting shouted
at.
On Mon, 11 Sept 2023 at 15:46, Maxime Ripard wrote:
> On Mon, Sep 11, 2023 at
Hi,
On 04/09/2023 09:54, Daniel Vetter wrote:
On Wed, 30 Aug 2023 at 17:14, Helen Koike > wrote: >> >> On 30/08/2023 11:57, Maxime Ripard wrote: >>> >>> I
agree that we need a baseline, but that baseline should be >>> defined
by the tests own merits, not their outcome on a >>> particular
Hi,
On Fri, 25 Aug 2023 at 08:56, Hsia-Jun Li wrote:
> On 8/25/23 15:40, Pekka Paalanen wrote:
> > if userspace cannot access things like an image's HDR metadata, then it
> > will be impossible for userspace to program KMS to have the correct
> > color pipeline, or to send intended HDR metadata
Hi Geert,
On Thu, 24 Aug 2023 at 16:09, Geert Uytterhoeven wrote:
> struct drm_client_dev *client = buffer->client;
> - struct drm_mode_fb_cmd fb_req = { };
> - const struct drm_format_info *info;
> + struct drm_mode_fb_cmd2 fb_req = { };
> int ret;
>
> -
Hi,
On 11/08/2023 17:35, Robin Murphy wrote:
On 2023-08-09 17:53, Boris Brezillon wrote:
+obj-$(CONFIG_DRM_PANTHOR) += panthor.o
FWIW I still think it would be nice to have a minor
directory/Kconfig/Makefile reshuffle and a trivial bit of extra
registration glue to build both drivers into
Userspace should not be able to trigger DRM_ERROR messages to spam the
logs; especially not through atomic commit parameters which are
completely legitimate for userspace to attempt.
Signed-off-by: Daniel Stone
Fixes: 7707f7227f09 ("drm/rockchip: Add support for afbc")
---
drive
Make it a little bit more clear what's going on and fix some formatting.
Signed-off-by: Daniel Stone
---
Documentation/driver-api/dma-buf.rst | 24
1 file changed, 16 insertions(+), 8 deletions(-)
v2: New.
diff --git a/Documentation/driver-api/dma-buf.rst
b
-by: Daniel Stone
---
Documentation/driver-api/dma-buf.rst | 8 +
Documentation/gpu/drm-uapi.rst| 7 +
.../userspace-api/dma-buf-alloc-exchange.rst | 384 ++
Documentation/userspace-api/index.rst | 1 +
4 files changed, 400 insertions(+)
create
Hi all,
This is v2 to the linked patch series; thanks to everyone for reviewing
the initial version. I've moved this out of a pure DRM scope and into
the general userspace-API design section. Hopefully it helps others and
answers a bunch of questions.
I think it'd be great to have
On Thu, 3 Aug 2023 at 16:46, Daniel Stone wrote:
> On Tue, 9 Nov 2021 at 09:13, Daniel Vetter wrote:
> > Seconded on just landing this without trying to perfect it first, because
> > I was just looking for it and didn't find it anywhere :-/
>
> Swing and a miss ...
>
ce around negotiating, allocating, importing, and
> > > > using buffers when crossing context/process/device/subsystem boundaries.
> > > >
> > > > This ties up all of dmabuf, formats and modifiers, and their usage.
> > > >
> > > > Signed-off-by
of the MD flag in any of the cmake files provided
with hypre, so it looks like the -MD flag is being added by the cmake Ninja
generator as a kind of default (and maybe in a confused way - why the -
instead of /?)
So the task now seems to be to convince cmake to stop doing this.
On Mon, Jul 24, 20
I have this working.
>
> Tested-by: Rob Clark
> Acked-by: Rob Clark
And it's also:
Acked-by: Daniel Stone
It's been back and forth a few times by now and reviewed pretty
heavily by all the people who are across the CI details. I think the
next step is to answer all the workflow q
On Mon, 24 Jul 2023 at 18:58, Justin Green wrote:
> + if (cmd->modifier[0] &&
>
This is not DRM_FORMAT_MOD_INVALID. Please either explicitly compare
against INVALID if that's what you meant, or against LINEAR if that's what
you meant, or both.
Cheers,
Daniel
Hello PETSc Users/Developers,
A collegue of mine is looking into implementing an adaptive implicit method
(AIM) over
PETSc in our simulator. This has led to some interesting questions about
what can
be done with blocked matrices, which I'm not able to answer myself - does
anyone have
any insight?
ul 2023, Barry Smith via petsc-users wrote:
> >>>
> >>>>
> >>>> You cannot use this version of PETSc, 3.19, with the version of hypre
> you installed. In hypre they recently changed hypre_Error from an integer
> to a struct which completely
> >> self.liblist = [['libHYPRE.a']]
> > >> self.buildLanguages = ['C','Cxx']
> > >>
> > >>
> > >> Satish
> > >>
> > >>
> > >> On Wed, 19 Jul 2023, Barry Smith wrote:
> > >>
>
t;>
> > >>
> > >> On Wed, 19 Jul 2023, Barry Smith wrote:
> > >>
> > >>>
> > >>> You don't indicate what type of libraries you built hypre with;
> static or shared. My guess is you ended up with shared
> > >>>
> > >>> I think the answer to your
Hello,
I'm working on getting a petsc build running on windows. One necessary
package to include is Hypre. I've been able to build Hypre seperately using
cmake, and confirmed that the library works
by setting up a VS project to run some of the example programs.
My attempted petsc build is being
Hi Huy,
On Wed, 12 Jul 2023 at 16:15, huy nguyen
wrote:
> I have a Linux system based on weston wayland. I run MPV player and expect
> it displays a video window at (0,0) position on the screen (top left corner
> of the display). I already use x11egl backend option to MPV to support a
> fixed
Hi Huy,
On Sat, 8 Jul 2023 at 08:39, huy nguyen wrote:
> I have a Linux system based on weston wayland and I need to get the
> current setting of the display resolution.
> Unfortunately, xrandr command does not work on Wayland.
> After much searching, I came to this information which is about
Hi Dawn,
On Thu, 22 Jun 2023 at 18:09, Dawn HOWE wrote:
> I am developing an (embedded) medical device which is required to have a
> touchscreen display and also mirror the output to a monitor connected via
> HDMI. The device is using Wayland/Weston on TorizonCore (based on a yocto
>
Hi Namit,
On Thu, 15 Jun 2023 at 16:37, Namit Solanki (QUIC) <
quic_nsola...@quicinc.com> wrote:
>
> As we all know Weston 10 has bitbakes files available for Yocto kirkstone
> version. Can Weston 12 work with Kirkstone as well?
>
>
>
> Is Weston 12 compatible with Kirkstone?
>
>
>
> Do we need
Hi Joe,
On Wed, 14 Jun 2023 at 21:33, Joe M wrote:
> Thanks Daniel. Do you know if wl_output instances are decoupled from each
> other, when it comes to display refresh?
>
Yep, absolutely.
> The wl_output geometry info hints that each output can be thought of as a
> region in a larger
Hi,
On Tue, 13 Jun 2023 at 10:20, Pekka Paalanen wrote:
> On Tue, 13 Jun 2023 01:11:44 + (UTC)
> Joe M wrote:
> > As I understand, there is one global wl_display. Is there always one
> > wl_compositor too?
>
> That is inconsequential.
>
Yeah, I think the really consequential thing is that
On Thu, 8 Jun 2023 at 16:54, Martin Petzold wrote:
> Am 08.06.23 um 16:58 schrieb Daniel Stone:
>
> On Thu, 8 Jun 2023 at 14:28, Pekka Paalanen wrote:
>
>> On Thu, 8 Jun 2023 14:49:37 +0200
>> Martin Petzold wrote:
>> > btw. we are using a Weston
Hi,
On Thu, 8 Jun 2023 at 14:28, Pekka Paalanen wrote:
> On Thu, 8 Jun 2023 14:49:37 +0200
> Martin Petzold wrote:
> > btw. we are using a Weston 9 package from NXP and there may be important
> > fixes for our i.MX8 platform in there.
>
> Oh. We cannot support modified Weston, sorry.
Hi Christian,
On Thu, 30 Mar 2023 at 20:15, Christian Gudrian wrote:
> We're running a custom Wayland compositor based on Qt Wayland on an i.MX6
> Quad system with a Vivante GC2000 GPU using the Mesa Gallium driver. While
> the compositor itself displays correctly, client buffers are displayed
Hi,
On Tue, 21 Mar 2023 at 12:08, Jani Nikula wrote:
> On Tue, 21 Mar 2023, Daniel Stone wrote:
> > There have been some threads - mostly motivated by MacBooks and the
> > Asahi team - about creating a KMS property to express invisible areas.
> > This would be the same thi
Hi,
On Tue, 21 Mar 2023 at 11:24, Jani Nikula wrote:
> On Tue, 21 Mar 2023, Michael Nazzareno Trimarchi
> wrote:
> > On Tue, Mar 21, 2023 at 11:43 AM Jani Nikula
> > wrote:
> >> On Tue, 21 Mar 2023, Michael Nazzareno Trimarchi
> >> wrote:
> >> > I would like to know the best approach in the
Hi Daniel,
On Fri, 10 Mar 2023 at 14:28, Levin, Daniel wrote:
> We are currently attempting to update from Weston 9.0.0 to Weston 10+ and
> facing issues with GLES2 compatibility at both build time and run time.
>
> For instance, gl_renderer_setup() exits with error if GL_EXT_unpack_subimage
>
Hi Martin,
On Fri, 17 Feb 2023 at 11:27, Martin Petzold wrote:
> Feb 17 12:16:24 tavla DISPLAY Wayland[957]: [12:16:24.624] Loading module
> '/usr/lib/aarch64-linux-gnu/libweston-9/g2d-renderer.so'
> Feb 17 12:16:25 tavla DISPLAY Wayland[957]: [ 1] Failed to open device:
> No such file or
Hi,
On Thu, 16 Feb 2023 at 09:25, Simon Ser wrote:
> On Thursday, February 16th, 2023 at 10:11, Pekka Paalanen
> wrote:
> > Btw. does this also mean that if you use GETFB2 to get handle A, you
> > export that as dmabuf and import in the same open device instance, you
> > again get handle A?
>
On Wed, 15 Feb 2023 at 20:54, Harry Wentland wrote:
> On 2/15/23 06:46, Daniel Stone wrote:
> > On Tue, 14 Feb 2023 at 16:57, Harry Wentland wrote:
> >> On 2/14/23 10:49, Sebastian Wick wrote:
> >> From what I've seen recently I am inclined to favor an incremental
>
On Wed, 15 Feb 2023 at 20:54, Harry Wentland wrote:
> On 2/15/23 06:46, Daniel Stone wrote:
> > On Tue, 14 Feb 2023 at 16:57, Harry Wentland wrote:
> >> On 2/14/23 10:49, Sebastian Wick wrote:
> >> From what I've seen recently I am inclined to favor an incremental
>
Hi,
On Tue, 14 Feb 2023 at 16:57, Harry Wentland wrote:
> On 2/14/23 10:49, Sebastian Wick wrote:
> From what I've seen recently I am inclined to favor an incremental
> approach more. The reason is that any API, or portion thereof, is
> useless unless it's enabled full stack. When it isn't it
Hi,
On Tue, 14 Feb 2023 at 16:57, Harry Wentland wrote:
> On 2/14/23 10:49, Sebastian Wick wrote:
> From what I've seen recently I am inclined to favor an incremental
> approach more. The reason is that any API, or portion thereof, is
> useless unless it's enabled full stack. When it isn't it
Hi Sascha,
On Mon, 6 Feb 2023 at 15:49, Sascha Hauer wrote:
> On Mon, Feb 06, 2023 at 03:04:48PM +0100, Sascha Hauer wrote:
> > I guess a first step would be to limit the maximum resolution of vopl
> > to what the hardware can do. We would likely end up with 1080p by
> > default then for the
Hello all,
I am currently having to figure out a way to get petsc working on windows,
using compilers from the intel oneAPI package. This means new compiler
names, such as "icx" for the c compiler and "ifx" for the fortran one.
I see from the installation instructions, and from old notes from a
Hi Randy,
On Tue, 29 Nov 2022 at 10:11, Hsia-Jun Li wrote:
> Currently, we assume all the pixel formats are multiple planes, devices
> could support each component has its own memory plane.
> But that may not apply for any device in the world. We could have a
> device without IOMMU then this is
rnel.org/pub/scm/linux/kernel/git/ogabbay/accel.git/log/?h=accel_v4
Series is:
Acked-by: Daniel Stone
Cheers,
Daniel
ready clarified in some vulkan discussions, but I
> can't find that anywhere anymore. At least not in a public link.
I seem to recall the policy being set in an IRC discussion at some
point (or perhaps during the AFBC merge?). This is a good
clarification of what we already do in practice.
Acked-by: Daniel Stone
Hi Christian,
On Fri, 28 Oct 2022 at 18:50, Christian König
wrote:
> Am 28.10.22 um 17:46 schrieb Nicolas Dufresne:
> > Though, its not generically possible to reverse these roles. If you want to
> > do
> > so, you endup having to do like Android (gralloc) and ChromeOS (minigbm),
> > because
Hi all,
On Tue, 25 Oct 2022 at 08:32, Daniel Vetter wrote:
> On Fri, 9 Sept 2022 at 19:18, Daniel Stone wrote:
> > But equally - and sorry for not jumping on the IRC (?) discussion as I was
> > in the middle of other stuff when it came up - I'm don't think this is the
Hi,
This libffi upgrade also completely breaks all use of Wayland on
aarch64. We use libffi to dispatch protocol messages (requests
received by the server and events received by the client) to
native-code handlers, and we are now getting completely nonsensical
values from it.
Can this upgrade
Hi,
This libffi upgrade also completely breaks all use of Wayland on
aarch64. We use libffi to dispatch protocol messages (requests
received by the server and events received by the client) to
native-code handlers, and we are now getting completely nonsensical
values from it.
Can this upgrade
Hi,
This libffi upgrade also completely breaks all use of Wayland on
aarch64. We use libffi to dispatch protocol messages (requests
received by the server and events received by the client) to
native-code handlers, and we are now getting completely nonsensical
values from it.
Can this upgrade
@collabora.com>
>
And also:
Acked-by: Daniel Stone
I was worried about INVALID being passed through, but for the most part it
seems like it magically turns into LINEAR through either zero extension or
explicit initialisation to zero.
Cheers,
Daniel
Hi Justin,
On Wed, 12 Oct 2022 at 20:12, Justin Green wrote:
> @@ -226,6 +249,32 @@ int mtk_ovl_layer_check(struct device *dev, unsigned
> int idx,
> if (state->fb->format->is_yuv && rotation != 0)
> return -EINVAL;
>
> + if (state->fb->modifier) {
>
Please spell
Hi,
On Tue, 20 Sept 2022 at 15:31, Ville Syrjälä
wrote:
> On Tue, Sep 20, 2022 at 03:56:18PM +0200, Thomas Zimmermann wrote:
> > Set partial updates on a plane if the framebuffer has not been changed
> > on an atomic commit. If such a plane has damage clips, the driver will
> > use them;
Hi,
On Fri, 9 Sept 2022 at 15:15, Tomeu Vizoso
wrote:
> Also include a configuration file that points to the out-of-tree CI
> scripts.
>
I think this para is outdated given ...
v8:
> - Move all files specific to testing the kernel into the kernel tree
> (thus I have dropped the r-bs I
On Fri, 9 Sept 2022 at 12:50, Simon Ser wrote:
> On Friday, September 9th, 2022 at 12:23, Hans de Goede <
> hdego...@redhat.com> wrote:
> > "people using
> > non fully integrated desktop environments like e.g. sway often use custom
> > scripts binded to hotkeys to get functionality like the
On Fri, 9 Sept 2022 at 12:50, Simon Ser wrote:
> On Friday, September 9th, 2022 at 12:23, Hans de Goede <
> hdego...@redhat.com> wrote:
> > "people using
> > non fully integrated desktop environments like e.g. sway often use custom
> > scripts binded to hotkeys to get functionality like the
.
>
> Fixes: 2af104290da5 ("drm: introduce fb_modifiers_not_supported flag in
> mode_config")
> Suggested-by: Shao-Chuan Lee
> Signed-off-by: Chia-I Wu
Reviewed-by: Daniel Stone
.
>
> Fixes: 2af104290da5 ("drm: introduce fb_modifiers_not_supported flag in
> mode_config")
> Suggested-by: Shao-Chuan Lee
> Signed-off-by: Chia-I Wu
Reviewed-by: Daniel Stone
___
Virtualization mailing li
Hi,
On Tue, 30 Aug 2022 at 22:42, Alan Coopersmith
wrote:
> We document autoconf 2.62 as the minimum release required in:
> https://www.x.org/wiki/Building_the_X_Window_System/
> and most modules have AC_PREREQ([2.60]). If I recall correctly, a decade
> ago
> we didn't want to force use of
1 - 100 of 9457 matches
Mail list logo
