From: Charles Brown <cab_77573@yahoo.com>
To: development@lists.ipfire.org
Subject: Re: CU 186 testing: AX88179 USB LAN adapter broken
Date: Tue, 04 Jun 2024 07:27:48 -0500 [thread overview]
Message-ID: <254676b7-97b3-48c2-bfe1-ca5ad6b734ea@yahoo.com> (raw)
In-Reply-To: <2cdcc3a3-a626-45a0-a033-3386de9cc0cf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
Okay, I found it and it is currently set thusly in master
"kernel/kernel.config.x86_64-ipfire:CONFIG_USB_NET_CDC_NCM=m".
Does that already imply that it is enabled?
On 6/4/2024 7:20 AM, Charles Brown wrote:
> Hi Michael, I would be happy to give that shot. I did a fresh pull of
> master into local git repo and have been grepping about looking for
> where to enable CONFIG_USB_NET_CDC_NCM. I am a bit of a novice here at
> this sort of thing. Could you point me where to do the enable thing
> for this config setting? -cab
>
> On 6/3/2024 4:29 AM, Michael Tremer wrote:
>> Hello Charles,
>>
>> No, that is something that we cannot do as we would reintroduce all
>> security vulnerabilities that have been fixed in the last 17 kernel
>> releases.
>>
>> However, did you confirm that enabling CONFIG_USB_NET_CDC_NCM works?
>> You mentioned this here:
>>
>> https://bugzilla.ipfire.org/show_bug.cgi?id=13692#c2
>>
>> -Michael
>>
>>> On 2 Jun 2024, at 20:04, Charles Brown <cab_77573(a)yahoo.com> wrote:
>>>
>>> With the issue reported in Bug# 13692, would it be possible to
>>> revert the kernel to 6.6.15 in CU 186?
>>>
next prev parent reply other threads:[~2024-06-04 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14c4c4b7-4060-4846-8abb-915a49261275.ref@yahoo.com>
2024-06-02 19:04 ` Charles Brown
2024-06-03 9:29 ` Michael Tremer
2024-06-04 12:20 ` Charles Brown
2024-06-04 12:27 ` Charles Brown [this message]
2024-06-04 12:43 ` Michael Tremer
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=254676b7-97b3-48c2-bfe1-ca5ad6b734ea@yahoo.com \
--to=cab_77573@yahoo.com \
--cc=development@lists.ipfire.org \
/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