Your message dated Thu, 01 May 2025 17:43:18 +0200 (CEST)
with message-id <20250501154318.97320be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1052676,
regarding linux-config: Enabling Kernel Configurations for MediaTek Platforms
(CONFIG_ARCH_MEDIATEK) (config-linux-6.5)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-config-6.5
Version: 6.5.3-1
Severity: normal
Release: bookworm, trixie
Dear Maintainers,
[RESEND] Sorry for bothering because the format of bug report was
incorrect in previous mail.
I am currently working on enabling Debian on MediaTek platforms. The
target SoCs include MT8365, MT8195/MT8395, and MT8188/MT8390. I
attempted to use a USB flash drive with the latest Debian release DVD
image on these boards, but there were no logs available after jumping
into the kernel from grub.
Upon examining the kernel configurations, I noticed that none of the
MediaTek-related kernel configurations are enabled by default. As a
result, I plan to submit patches and file issues with the Debian
community. I think the very beginning configration will be
"CONFIG_ARCH_MEDIATEK=y" and other necessary peripherals like
power/clock/uart, etc.
Although I have experience as a Debian user, I am new to the role of an
issue reporter. I have read the bug report how-to guide, but I still
have some questions about submitting patches for SoC enablement on
Debian. This is particularly challenging as this is the first time to
port MediaTek platforms to the Debian distribution. I have registered
for the kernel mailing list and created a GitLab account for sending
merge requests.
Here are my questions:
1. What is the best way to file issues with patches? Should I file one
issue per patch or per single configuration change?
2. Should I send a series of patches for platform enablement as a single
issue via GitLab, or should I send patches through the mailing list (bug
report system)?
3. Should I submit bugs for enabling kernel configurations to multiple
kernel versions? (6.1, 6.4, 6.5) This might cause same issues for
different kernel versions show up in bug tracking system.
4. Should I send patches for different branches separately? For
instance, I have cloned
"https://salsa.debian.org/kernel-team/linux.git";. Should I send patches
or merge requests for different branches like bookworm and trixie to
keep the setting in future releases?
5. Is there a verification method for kernel configurations on Debian? I
currently have a running Ubuntu on MediaTek platforms and can debug
kernel configurations on Ubuntu. However, I don't have a bootable Debian
on these boards. Should I use debootstrap
"https://wiki.debian.org/Debootstrap"; on Ubuntu boards to install Debian
and build the Debian kernel at the initial stage?
I appreciate your guidance on these matters. I am eager to contribute to
kernel configurations on Debian for MediaTek platforms.
Best regards,
Macpaul Lin
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
