On 02/03/2024 10:48 pm, Gustavo Padovan wrote:
On Friday, March 01, 2024 18:56 -03, Guillaume Tucker
wrote:
On 29/02/2024 17:28, Nicolas Dufresne wrote:
Hi,
Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit :
On 2/29/24 2:20 PM, Guillaume Tucker wrote:
Hello,
On 28/02
On 29/02/2024 17:28, Nicolas Dufresne wrote:
> Hi,
>
> Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit :
>> On 2/29/24 2:20 PM, Guillaume Tucker wrote:
>>> Hello,
>>>
>>> On 28/02/2024 23:55, Helen Koike wrote:
>>>>
Hello,
On 28/02/2024 23:55, Helen Koike wrote:
> Dear Kernel Community,
>
> This patch introduces a `.gitlab-ci` file along with a `ci/` folder, defining
> a
> basic test pipeline triggered by code pushes to a GitLab-CI instance. This
> initial version includes static checks (checkpatch and
On 29/02/2024 12:41, Mark Brown wrote:
> On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote:
>> On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote:
>
>>> Of course. You're also welcome to join the #kernelci channel on libera.chat.
>
>> Isn't that a bit pointless if
On 14/12/2022 14:50, Mark Brown wrote:
> On Wed, Dec 14, 2022 at 01:55:03PM +0100, Guillaume Tucker wrote:
>
>> Maybe you could retrieve the original thread and rely to it with
>> the report? That's the ideal way of following up on a patch I
>> think. You can ge
On 14/12/2022 15:03, Geert Uytterhoeven wrote:
> Hi Guillaume,
>
> On Wed, Dec 14, 2022 at 1:54 PM Guillaume Tucker
> wrote:
>> On 14/12/2022 11:06, Geert Uytterhoeven wrote:
>>> On Tue, Dec 13, 2022 at 5:58 PM Mark Brown wrote:
>>>> On Tue, Dec 13, 2022
Hi Mark,
Maybe you could retrieve the original thread and rely to it with
the report? That's the ideal way of following up on a patch I
think. You can get the mbox file this way:
./kci_bisect get_mbox \
--commit ca871659ec1606d33b1e76de8d4cf924cf627e34 \
--kdir ~/src/linux
On 14/12/2022
der features.
>
> Fixes: b33340e33acd ("drm/meson: dw-hdmi: Ensure that clocks are enabled
> before touching the TOP registers")
> Reported-by: Guillaume Tucker
Although I am triaging kernelci bisections, it was initially
found thanks to our friendly bot. So if you're OK w
Hi Marc,
On 19/11/2020 11:58, Marc Zyngier wrote:
> On 2020-11-19 10:26, Neil Armstrong wrote:
>> On 19/11/2020 11:20, Marc Zyngier wrote:
>>> On 2020-11-19 08:50, Guillaume Tucker wrote:
>>>> Please see the automated bisection report below about some kernel
Please see the automated bisection report below about some kernel
errors on meson-gxbb-p200.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org, however this one
looks valid.
The bisection started with next-20201118 but the errors are
Please see the bisection report below about a boot failure.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
This bisection was run with exynos_defconfig but the issue can
also be reproduced with
when applied on top
of next-20181206 (what I used for the bisection last week):
http://lava.baylibre.com:10080/scheduler/job/71109
However the fix doesn't appear to have been applied in any
upstream tree yet.
Guillaume
> On Fri, 2018-12-07 at 23:31 +, Guillaume Tucker wrote
Please find below an automated bisection report for a kernel Oops
seen during the initialisation of the nouveau GPU driver on
jetson-tk1.
All the LAVA test jobs for this bisection can be found here:
http://lava.baylibre.com:10080/scheduler/alljobs?length=25=lava-bisect-staging-7366#table
his
change is preventing Tegra124 devices from booting when Nouveau is
enabled. To allow Tegra124 to boot, remove the teardown helper for
gk20a.
This is based upon a previous patch by Guillaume Tucker but limits
the workaround to only gk20a GPUs.
Fixes: bbb163e18960 ("drm/nouveau/bar: implement bar1 tear
do on these platforms before the rework
(i.e. assign the parent clock to sor->clk instead). There might
be a more correct way of fixing this, hence the RFC.
[1] https://patchwork.kernel.org/patch/10124637/
[2] e1335e2f0cfc ("drm/tegra: sor: Reimplement pad clock")
Guillaume Tucker (1):
drm/tegr
gra124 and should also affect tegra210
as they both don't support HDMI and DP. Tested on tegra124 only.
Fixes: e1335e2f0cfc ("drm/tegra: sor: Reimplement pad clock")
Signed-off-by: Guillaume Tucker <guillaume.tuc...@collabora.com>
CC: Thierry Reding <tred...@nvidia.com>
---
dri
On 05/12/17 18:32, Ben Skeggs wrote:
On Wed, Dec 6, 2017 at 12:30 AM, Jon Hunter <jonath...@nvidia.com> wrote:
On 04/12/17 18:37, Guillaume Tucker wrote:
If the firmware fails to load then ->fini() will be called before the
device has been initialised, causing the kernel to hang whi
: implement bar1 teardown")
Signed-off-by: Guillaume Tucker <guillaume.tuc...@collabora.com>
CC: Ben Skeggs <bske...@redhat.com>
---
drivers/gpu/drm/nouveau/nvkm/subdev/bar/gf100.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouvea
gra124.
Fixes: e1335e2f0cfc ("drm/tegra: sor: Reimplement pad clock")
Signed-off-by: Guillaume Tucker <guillaume.tuc...@collabora.com>
CC: Thierry Reding <tred...@nvidia.com>
---
drivers/gpu/drm/tegra/sor.c | 24 ++--
1 file changed, 14 insertions(+),
19 matches
Mail list logo
