similar to: crc

From: Lyude Paul <lyude at redhat.com> (Just forwarding this to nouveau's ml, since I completely forgot to before) Nouveau has finally gotten CRC support, hooray! Well, it's under review at least: https://patchwork.freedesktop.org/series/74804/ (it has a cover letter, but nouveau's mailing list configuration has blocked the email so I'm waiting for a moderator to fix that)

From: Lyude Paul <lyude at redhat.com> Nouveau has finally gotten CRC support, hooray! Well, it's under review at least: https://patchwork.freedesktop.org/series/74804/ (it has a cover letter, but nouveau's mailing list configuration has blocked the email so I'm waiting for a moderator to fix that) So, this series adds the relevant tests for it since nvidia's CRC

From: Lyude Paul <lyude at redhat.com> Nouveau has finally gotten CRC support, hooray! Well, it's under review at least: https://patchwork.freedesktop.org/series/74804/ (it has a cover letter, but nouveau's mailing list configuration has blocked the email so I'm waiting for a moderator to fix that) So, this series adds the relevant tests for it since nvidia's CRC

From: Lyude Paul <lyude at redhat.com> We're finally getting CRC support in nouveau, so let's start testing this in igt as well! While the normal CRC capture tests are nice, there's a number of Nvidia-specific hardware characteristics that we need to test as well. The most important one is known as a "notifier context flip". Basically, Nvidia GPUs store generated CRCs

From: Lyude Paul <lyude at redhat.com> Nouveau has finally gotten CRC support, and at this point that support has made its way upstream. Hooray! So, let's start adding some relevant tests for it since nvidia's CRC implementation has some rather interesting design choices that needed to be worked around. Lyude Paul (5): lib/igt_core: Fix igt_assert_fd() documentation

On Mon, 2020-09-28 at 17:36 -0400, Jeremy Cline wrote: > Hi, > > On Tue, Aug 18, 2020 at 05:00:51PM -0400, Lyude wrote: > > From: Lyude Paul <lyude at redhat.com> > > > > We're finally getting CRC support in nouveau, so let's start testing > > this in igt as well! While the normal CRC capture tests are nice, > > there's a number of

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests that we'll be sending in just a short bit. This additionally adds a feature that Ville Syrj?l? came up with: vblank works. Basically, this is just a generic DRM

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests that we'll be sending in just a short bit. This additionally adds a feature that Ville Syrj?l? came up with: vblank works. Basically, this is just a generic DRM

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrj?l? came up

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrj?l? came up

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrj?l? came up

Nvidia released some documentation on how CRC support works on their GPUs, hooray! So: this patch series implements said CRC support in nouveau, along with adding some special debugfs interfaces for some relevant igt-gpu-tools tests (already on the ML). First - we add some new functionality to kthread_work in the kernel, and then use this to add a new feature to DRM that Ville Syrj?l? came up

From: Lyude Paul <lyude at redhat.com> Signed-off-by: Lyude Paul <lyude at redhat.com> --- tests/kms_pipe_crc_basic.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/tests/kms_pipe_crc_basic.c b/tests/kms_pipe_crc_basic.c index d169b7bd..f121e27e 100644 --- a/tests/kms_pipe_crc_basic.c +++ b/tests/kms_pipe_crc_basic.c @@ -65,15 +65,14 @@ static void

ogg.k.ogg.k at googlemail.com wrote, on 7/14/2009 7:16 AM: >> easy to replace. The second packet is the metadata, which we can lose. >> It's just the third packet that needs to be reconstructed. After that, >> you could start at any packet division in the rest of the file and it >> would play fine? So this generic restore tool that I'm positing would >> just

I'm trying to simply regenerate the comment header checksum on the ogg file "test.ogg" I ripped the checksum function from libvorbis, and only modified it in that I hard-coded what I think is the comment header (as far as I can tell from the docs). However it seems to generate an invalid checksum (according to ogginfo) Here is a url to the two files, please help :)

Other gpu drivers have some driver-specific documentation, so it would nice if nouveau did as well. This adds a bare-bones ReStructured Text document with sections for module parameter documentation, an overview of the driver architecture, a section for internal API documentation, and a glossary for nouveau-specific terms. To make the document a little less bare, I've included docblocks for

Monty Montgomery wrote, on 7/14/2009 1:44 AM: > On Tue, Jul 14, 2009 at 1:41 AM, Erik de Castro > Lopo<mle+la at mega-nerd.com> wrote: >> Monty Montgomery wrote: >> >>> Yes. Without the first three packets (which hold all the codec >>> settings and all the instruction how to handle the subsequent packets) >>> the rest of the stream is gibberish.

This is not complete documentation, but covers the pieces I read through while reviewing the IGT CRC tests for nouveau. It covers the nouveau-specific debugfs file, an overview of why the code is more complicated than the DRM display CRC support documentation would lead one to expect, and the nv50_crc_func vtable. Many of the details were gleaned from Lyude's commit message, but I think

Hi, I am exploring extending Kyle Jones' patch (which implements post-transfer filter in receiver.c) to pre-filter or otherwise pre-process the file before it is sent. Kyle Jones patch can be found here <http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=b6f55s%24256q%241%40FreeBSD.csie.NCTU.edu.tw&rnum=6> and the rationale for what I am trying to do here

From: Lyude Paul <lyude at redhat.com> We're finally getting CRC support in nouveau, so let's start testing this in igt as well! While the normal CRC capture tests are nice, there's a number of Nvidia-specific hardware characteristics that we need to test as well. The most important one is known as a "notifier context flip". Basically, Nvidia GPUs store generated CRCs