[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1011240: marked as done (linux-image-5.10.0-14-amd64: Please consider adding CONFIG_XILLYBUS kernel configuration flag)

Your message dated Thu, 01 May 2025 16:59:20 +0200 (CEST)
with message-id <20250501145920.D7BCEBE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1011240,
regarding linux-image-5.10.0-14-amd64: Please consider adding CONFIG_XILLYBUS kernel configuration flag
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 owner@bugs.debian.org
immediately.)


-- 
1011240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011240
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 5.10.113-1
Severity: wishlist
X-Debbugs-Cc: debian-bug-report@billauer.co.il

Dear Maintainer,

Please consider enabling Xillybus' drivers as modules on future kernels
releases.

Currently we have:
$ grep XILLY /boot/config-5.10.0-14-amd64 

Actual result:

# CONFIG_XILLYBUS is not set

Desired result:

CONFIG_XILLYBUS_CLASS=m
CONFIG_XILLYBUS=m
CONFIG_XILLYBUS_PCIE=m
CONFIG_XILLYUSB=m

Additional info:

Xillybus is a solution for communication between programmable hardware (FPGA)
and a host using the PCIe bus (and possibly other buses on embedded platforms).
It's further explained in the kernel tree's Documentation/xillybus.txt and at
http://www.xillybus.com.

The suggested fix enables the compilation of the driver for Xillybus as a
module. This driver has been in the kernel under drivers/char/xillybus/ since
kernel v3.18 (and as a staging driver since v3.12) and is beneficial for FPGA
hardware developers using the relevant hardware component.

Being a kernel module for a PCIe device, it's activated only on a Vendor/Device
IDs match, so this change has no possible impact on users who have no direct
interest in it. Regardless, the module is stable for several years, and is
enabled in Ubuntu and its derivatives for several years as well.

CONFIG_XILLYBUS_PCIE=m enables the module which supports Xillybus based upon
PCIe. CONFIG_XILLYBUS=m is required by CONFIG_XILLYBUS_PCIE (contains the
core driver for Xillybus which is common with Xillybus for embedded platforms).
CONFIG_XILLYUSB=m is the USB variant for the same solution.

CONFIG_XILLYBUS_CLASS=m is activated automatically by the kernel config system.

Thanks in advance,
  Eli

-- Package-specific info:
** Version:
Linux version 5.10.0-14-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.113-1 (2022-04-29)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-amd64 root=UUID=8b5e89d9-ecb6-44da-8ef8-d4b10cf3e4b2 ro quiet

--- 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 ---
Reply to: