lp:~canonical-kernel/ubuntu/+source/linux-nvidia/+git/jammy

Owned by Canonical Kernel
Get this repository:
git clone https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-nvidia/+git/jammy
Members of Canonical Kernel can upload to this repository. Log in for directions.

Branches

Name Last Modified Last Commit
main-next--2024.04.29-1--auto 2024-05-08 16:58:05 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1059.60

Author: Ubuntu Kernel Bot
Author Date: 2024-05-08 16:58:05 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1059.60

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

nvidia-6.5-next--2024.04.29-1--auto 2024-05-08 14:45:17 UTC
UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1020.20

Author: Ubuntu Kernel Bot
Author Date: 2024-05-08 14:45:17 UTC

UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1020.20

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

nvidia-6.5-next 2024-05-06 19:41:16 UTC
gpio: tegra186: Fix tegra186_gpio_is_accessible() check

Author: Prathamesh Shete
Author Date: 2024-04-24 09:55:14 UTC

gpio: tegra186: Fix tegra186_gpio_is_accessible() check

BugLink: https://bugs.launchpad.net/bugs/2064549

The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.

This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:

  - SCR_SEC_REN + SCR_SEC_WEN both set

    or

  - SCR_SEC_REN + SCR_SEC_WEN both set and
    SCR_SEC_G1R + SCR_SEC_G1W both set

Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.

Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
Acked-by: Thierry Reding <treding@nvidia.com>
(cherry-picked from commit d806f474a9a7993648a2c70642ee129316d8deff linux-next)
Signed-off-by: Jamie Nguyen <jamien@nvidia.com>
Acked-by: Brad Figg <bfigg@nvidia.com>
Acked-by: Noah Wager <noah.wager@canonical.com>
Acked-by: Jacob Martin <jacob.martin@canonical.com>
Signed-off-by: Brad Figg <bfigg@nvidia.com>

main-next 2024-05-06 15:37:43 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1055.56

Author: Jacob Martin
Author Date: 2024-05-06 15:37:43 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1055.56

Signed-off-by: Jacob Martin <jacob.martin@canonical.com>

nvidia-6.8-next 2024-05-03 19:22:49 UTC
gpio: tegra186: Fix tegra186_gpio_is_accessible() check

Author: Prathamesh Shete
Author Date: 2024-04-24 09:55:14 UTC

gpio: tegra186: Fix tegra186_gpio_is_accessible() check

BugLink: https://bugs.launchpad.net/bugs/2064549

The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.

This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:

  - SCR_SEC_REN + SCR_SEC_WEN both set

    or

  - SCR_SEC_REN + SCR_SEC_WEN both set and
    SCR_SEC_G1R + SCR_SEC_G1W both set

Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.

Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
Acked-by: Thierry Reding <treding@nvidia.com>
(cherry-picked from commit d806f474a9a7993648a2c70642ee129316d8deff linux-next)
Signed-off-by: Jamie Nguyen <jamien@nvidia.com>
Acked-by: Brad Figg <bfigg@nvidia.com>
Acked-by: Noah Wagner <noah.wagner@canonical.com>
Acked-by: Jacob Martin <jacob.martin@canonical.com>
Signed-off-by: Brad Figg <bfigg@nvidia.com>

nvidia-6.5-next--s2024.04.01-1--auto 2024-05-02 02:00:38 UTC
UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1019.19

Author: Ubuntu Kernel Bot
Author Date: 2024-05-02 02:00:35 UTC

UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1019.19

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

main-next--s2024.04.01-1--auto 2024-05-01 01:25:56 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1055.56

Author: Ubuntu Kernel Bot
Author Date: 2024-05-01 01:25:56 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1055.56

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

nvidia-6.5-next--s2024.03.04-1--auto 2024-04-03 05:29:56 UTC
UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1015.15

Author: Ubuntu Kernel Bot
Author Date: 2024-04-03 05:29:56 UTC

UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1015.15

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

main-next--s2024.03.04-1--auto 2024-04-03 03:51:15 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1049.49

Author: Ubuntu Kernel Bot
Author Date: 2024-04-03 03:51:14 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1049.49

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

main-next--2024.03.04-1--auto 2024-03-22 09:51:43 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1048.48

Author: Ubuntu Kernel Bot
Author Date: 2024-03-22 09:51:43 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1048.48

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

main-next--s2024.02.05-1--auto 2024-03-22 01:33:34 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1047.47

Author: Ubuntu Kernel Bot
Author Date: 2024-03-22 01:33:34 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1047.47

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

main-next--s2024.02.05-1 2024-03-19 12:48:18 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1046.46

Author: Ian May
Author Date: 2024-02-13 14:41:57 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1046.46

Signed-off-by: Ian May <ian.may@canonical.com>

main-next--s2024.01.08-1--auto 2024-03-14 13:02:47 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1045.45

Author: Ubuntu Kernel Bot
Author Date: 2024-03-14 13:02:47 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1045.45

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

main-next--2024.02.05-1--auto 2024-03-13 23:42:39 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1046.46

Author: Ubuntu Kernel Bot
Author Date: 2024-03-13 23:42:39 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1046.46

Signed-off-by: Ubuntu Kernel Bot <ubuntu-kernel-bot@canonical.com>

nvidia-6.2-next 2024-01-17 15:10:55 UTC
UBUNTU: Ubuntu-nvidia-6.2-6.2.0-1015.15

Author: Ian May
Author Date: 2024-01-17 15:10:55 UTC

UBUNTU: Ubuntu-nvidia-6.2-6.2.0-1015.15

Signed-off-by: Ian May <ian.may@canonical.com>

nvidia-6.5 2023-10-04 19:06:22 UTC
UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1001.1

Author: Ian May
Author Date: 2023-10-04 05:20:42 UTC

UBUNTU: Ubuntu-nvidia-6.5-6.5.0-1001.1

Signed-off-by: Ian May <ian.may@canonical.com>

nvidia-5.19-next 2023-07-28 21:18:56 UTC
NVMe/MVMEeOF: Patch NVMe/NVMeOF driver to support GDS on Linux 5.19 Kernel

Author: Sourab Gupta
Author Date: 2023-07-19 01:02:51 UTC

NVMe/MVMEeOF: Patch NVMe/NVMeOF driver to support GDS on Linux 5.19 Kernel

BugLink: https://bugs.launchpad.net/bugs/1982519

With this change, the NVMe and NVMeOF driver would be
enabled to support GPUDirectStorage(GDS).
The change is around nvme/nvme rdma map_data()
and unmap_data(), where the IO request is
first intercepted to check for GDS pages and
if it is a GDS page then the request is served
by GDS driver component called nvidia-fs,
else the request would be served by the standard NVMe driver code.

Acked-by: Prashant Prabhu prashantp@nvidia.com
Acked-by: Rebanta Mitra rmitra@nvidia.com
Signed-off-by: Sourab Gupta sougupta@nvidia.com
Acked-by: Brad Figg <bfigg@nvidia.com>
Acked-by: Ian May <ian.may@canonical.com>
Acked-by: Jacob Martin <jacob.martin@canonical.com>
Signed-off-by: Brad Figg <bfigg@nvidia.com>

nvidia-6.2 2023-04-27 15:56:43 UTC
UBUNTU: [Config] nvidia-6.2: update annotations

Author: Ian May
Author Date: 2023-04-27 03:39:58 UTC

UBUNTU: [Config] nvidia-6.2: update annotations

Signed-off-by: Ian May <ian.may@canonical.com>

nvidia-5.19 2023-03-17 17:09:29 UTC
UBUNTU: Ubuntu-nvidia-5.19-5.19.0-1008.8

Author: Brad Figg
Author Date: 2023-03-17 16:33:54 UTC

UBUNTU: Ubuntu-nvidia-5.19-5.19.0-1008.8

Signed-off-by: Brad Figg <bfigg@nvidia.com>

main 2023-02-01 03:00:59 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1017.17

Author: Brad Figg
Author Date: 2023-02-01 03:00:14 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1017.17

Signed-off-by: Brad Figg <bfigg@nvidia.com>

main-prep 2022-05-17 15:42:30 UTC
UBUNTU: Ubuntu-nvidia-5.15.0-1001.1

Author: Zachary Tahenakos
Author Date: 2022-05-17 15:42:30 UTC

UBUNTU: Ubuntu-nvidia-5.15.0-1001.1

Signed-off-by: Zachary Tahenakos <zachary.tahenakos@canonical.com>

121 of 21 results
This repository contains Public information 
Everyone can see this information.