From: Nicolas Baranger <nicolas.baranger@3xo.fr>
To: dri-devel@lists.freedesktop.org
Cc: Tzimmermann <tzimmermann@suse.de>,
airlied@redhat.com, Jocelyn Falempe <jfalempe@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
linux-kernel@vger.kernel.org
Subject: Include ASPEED ast-drm 1.15.1 video driver in kernel tree
Date: Wed, 12 Feb 2025 19:58:50 +0100 [thread overview]
Message-ID: <194c4656963debcf074d87e89ab1a829@3xo.fr> (raw)
In-Reply-To: <d507f6268ea3158b5af82b6860ca7b71@3xo.fr>
Dear maintener
I did include ast-drm driver version 1.15.1 (in replacement of version
0.1.0) on the new mainline kernel too (6.14.0-rc2) and I issue a new
dkms patch
Last DKMS patch had been sucessfully tested on mainline.
And last ast.ko version 1.15.1 included in linux tree had also been
sucessfully tested
Online directory is updated with :
- new DKMS patch
- new DKMS srouces
- new DKMS debian package
- new tarball of mainline included ast_new ported in kernel tree
- new kernel debian package (mainline with ast_new)
NB: online directory is here:
https://xba.soartist.net/ast-drm_nba_20250211/
Please let me know what I should do to see this change in linux-next
Thanks for help
Kind regards
Nicolas Baranger
Le 2025-02-11 19:15, Nicolas Baranger a écrit :
> Dear maintener
>
> For my own usage, I did make work the ASPEED ast-drm 1.15.1 video
> driver on mainline kernel (6.13.0 + 6.13.1).
>
> ASPEED video driver is availiable here:
> https://www.aspeedtech.com/file/support/Linux_DRM_1.15.1_4.tar.gz
>
> But it only work for LTS kernel
> So I modify the DKMS package and I build a new Debian DKMS package with
> the adapted source.
> My patch can be find here :
> https://xba.soartist.net/ast-drm_nba_20250211/nba-dkms/astdiff.patch
> See the README:
> https://xba.soartist.net/ast-drm_nba_20250211/nba-dkms/README
>
> Using this new 'ast 1.15.1' driver, performance are amazing compared to
> the 'ast' driver include in kernel tree, specially when using a
> discrete GPU and offloading VULKAN / 3D on it but using AST VGA card as
> the main video card and as the main and only video output (the discrete
> GPU is used only for offloading 3D or for cuda/opencl)
>
> So to make things easier, I include the new 'ast 1.15.1' driver in
> kernel tree as AST_NEW : linux-6.13.1-ast/drivers/gpu/drm/ast_new'
> It's working fine as you can see on this video :
> https://xba.soartist.net/ast-drm_nba_20250211/vulcan_nvidia_prime_render_offload_on_ast_vga_card.webm
>
> I upload all the work I've done here :
> https://xba.soartist.net/ast-drm_nba_20250211/
>
> See the global README :
> https://xba.soartist.net/ast-drm_nba_20250211/README
>
> and the README in nba-kernel sub-directory :
> https://xba.soartist.net/ast-drm_nba_20250211/nba-kernel/README
>
> I'm not a developer so please let me know if I made the things the
> right way and if this new 'ast 1.15.1' driver can be ported to
> linux-next or linux-? ?
> If you need more explanations, do not hesitate to contact me, I would
> be happy to help
>
> Kind regards
> Nicolas Baranger
next parent reply other threads:[~2025-02-12 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d507f6268ea3158b5af82b6860ca7b71@3xo.fr>
2025-02-12 18:58 ` Nicolas Baranger [this message]
2025-02-12 19:14 ` Include ASPEED ast-drm 1.15.1 video driver in kernel tree Maarten Lankhorst
2025-02-13 7:57 ` Thomas Zimmermann
[not found] ` <984c317de1027f5886390a65f1f66126@3xo.fr>
2025-02-13 9:36 ` Nicolas Baranger
2025-02-14 9:11 ` Jocelyn Falempe
2025-02-14 12:36 ` Thomas Zimmermann
2025-02-14 15:01 ` Nicolas Baranger
2025-02-14 17:03 ` Nicolas Baranger
2025-02-14 17:52 ` Nicolas Baranger
2025-02-17 8:11 ` Thomas Zimmermann
2025-02-17 8:37 ` Nicolas Baranger
2025-02-21 11:57 ` Nicolas Baranger
2025-02-24 8:53 ` Jani Nikula
2025-02-24 9:57 ` Nicolas Baranger
2025-02-14 12:46 Thomas Zimmermann
2025-02-14 15:10 ` Nicolas Baranger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=194c4656963debcf074d87e89ab1a829@3xo.fr \
--to=nicolas.baranger@3xo.fr \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox