From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 11525C433DB for ; Mon, 15 Feb 2021 17:09:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D498A64E02 for ; Mon, 15 Feb 2021 17:08:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232764AbhBORId (ORCPT ); Mon, 15 Feb 2021 12:08:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43890 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232022AbhBOPzZ (ORCPT ); Mon, 15 Feb 2021 10:55:25 -0500 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 877B3C061788; Mon, 15 Feb 2021 07:54:38 -0800 (PST) Received: by mail-wr1-x436.google.com with SMTP id v7so9447042wrr.12; Mon, 15 Feb 2021 07:54:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pNbLw2bB0q9Jg17V7PmEJoybP6JsSyuWKoXpx/sdxy8=; b=uyVQW/vo9XkF+fT10kUIaOPX1SeLXbJoWLZwRRZCwvjl5fSJlgHukG8BGhfLoJOdjl /XVtAeVsyfCrx9DZWkKbA7K8ihabkBEtNmzr10PgsqS54/L6aG00NfdtO8C/17Pf5Qz1 Tfb2QalMf6KQPm0zuI/mq283wjCn3//0op5CJExCKLWQWjDm3w8FI5c42UmP9XrrDFB0 HchdzlOeYo9+0FMQ872j5CMOTjZy4gXwyADpKrh40PYjYKFt0faekaRG/6rHscKNprl9 317jqdKzniz/3V1oY4MQ7LWToj5yHYE1sxDvW2kxlS8wlHz3XMnJdMyPqAyfKivy2sWC rNEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pNbLw2bB0q9Jg17V7PmEJoybP6JsSyuWKoXpx/sdxy8=; b=HnMYw4L71A3Kp8ZcJeKwzGsff3jb1nkX8AngfDwB6Z1Qq8Wmgz+wEx3jfp5HIZy+Cg bbAHO60FP1AEFlzIzJXFYkFgIM6tVaCMpROjwDWfkBJanBivCOKpq1u4MRscKiYFDsTB 534y5UEiWUK9rHJ8UBgnIMlBB60Ph2+z3k1nu8j49t0EZKsCjFzjTekFHX/zcgoKfeW0 5LDwsJY7unTPv8i/591sYwB7ORwYyJ2FDVNKiK7Riq9yYUiqLN8lVzhi/1/VyWLnxYaE Ad0B+zmhmEC6nVChm2W5cg2ub74uhWKYaZH37QWiBA4597oOpG+tM8snbEWHKc3N/rNU WSqA== X-Gm-Message-State: AOAM531/s/2k6rKtmjgfmR7Z1GVGxIfp5uyGkeA6SH1XiXK9/8QOA02L 4V51WG9lGxHujaLRrShvl/tXnoY2rE0mos711LA= X-Google-Smtp-Source: ABdhPJxD6STXfO+mTL5nBlJSqH3ry36wSlJoY+Tz9IuCcgq4zAG/0UMDTGjzrIBlGbuuzLst3BaLuURIwm1WUwtwbkg= X-Received: by 2002:a05:6000:18a:: with SMTP id p10mr8525247wrx.166.1613404477234; Mon, 15 Feb 2021 07:54:37 -0800 (PST) MIME-Version: 1.0 References: <20210203163348.30686-1-TheSven73@gmail.com> <804285cff81878a2c188d1b823182114f891ca38.camel@ndufresne.ca> <20210211143233.GA1360@pengutronix.de> <10bfc6f5aaa02ad5858186ccee1894424fc0dd39.camel@pengutronix.de> In-Reply-To: <10bfc6f5aaa02ad5858186ccee1894424fc0dd39.camel@pengutronix.de> From: Sven Van Asbroeck Date: Mon, 15 Feb 2021 10:54:25 -0500 Message-ID: Subject: Re: [BUG REPORT] media: coda: mpeg4 decode corruption on i.MX6qp only To: Lucas Stach Cc: Philipp Zabel , Nicolas Dufresne , Mauro Carvalho Chehab , Adrian Ratiu , Fabio Estevam , linux-media , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Lucas, On Mon, Feb 15, 2021 at 5:15 AM Lucas Stach wrote: > > The straight forward way to fix this would be to just disable the PRE > when the stride is getting too large, which might not work well with > all userspace requirements, as it effectively disables the ability to > scan GPU tiled surfaces when the stride is getting too large. Thank you for your very knowledgeable input, really appreciate it. I am wondering why I am the first to notice this particular corner case. Is this perhaps because X+armada plugin allocate a huge bitmap that fits all displays, and other software frameworks do not? Are people on i.MX6 mostly using X or Wayland? If Wayland allocates a separate bitmap for each display, this PRE bug will of course never show up... Sven