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

Bug#946551: marked as done (Enable TI PHY for 5.x kernels)



Your message dated Thu, 26 Dec 2019 14:43:02 +0000
with message-id <bd341f66c7e3e1618274f8ef4ec56ab5bccf0ade.camel@decadent.org.uk>
and subject line Re: Bug#946551: Enable TI PHY for 5.x kernels
has caused the Debian Bug report #946551,
regarding Enable TI PHY for 5.x kernels
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.)


-- 
946551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946551
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Version: 5.3.9-3
Severity: normal

The armmp Linux configuration had CONFIG_TI_CPSW_PHY_SEL enabled to be
built in the kernel up to including the buster kernel version. As this
config was deprecated with 5.1, it was removed from Debian's
configuration. With the 5.x versions comes the successor
CONFIG_PHY_TI_GMII_SEL enabled as a module. This just hit me updating
a BeagleBone Black (that does not load any modules) from buster to
testing.

I have created a merge request with CONFIG_PHY_TI_GMII_SEL=y for
armmp: https://salsa.debian.org/kernel-team/linux/merge_requests/194

--- End Message ---
--- Begin Message ---
On Thu, 2019-12-26 at 15:08 +0100, Bastian Germann wrote:
> I do not install any modules on that device intentionally. If you
> think that this is not supported by Debian, please close the bug.

Indeed it is not supported.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.


Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply to: