|
Bugzilla – Full Text Bug Listing |
| Summary: | LX2160A Networking not supported | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Josua Mayer <josua.m> |
| Component: | Kernel | Assignee: | Yousaf Kaukab <yousaf.kaukab> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | guillaume.gardet, mbrugger, tiwai, yousaf.kaukab |
| Version: | Leap 15.2 | ||
| Target Milestone: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Josua Mayer
2020-12-18 13:41:21 UTC
Please attach your DPC settings. Please try changing the link_type of the MAC you are using to MAC_LINK_TYPE_FIXED in DPC. DPC is embedded in firmware (acpi). What's then needed as a bare minimum is access to the mcbin for setting up interfaces with NXPs restool, e.g. sudo ls-addni dpmac.9 This part currently requires additional patches to Linux not yet mainline :( There are also patches for configuring the 1gbps interface from ACPI tables which need to be carried. From my sources what's been taking so long is the standardization of mdio in acpi - which apparently - was new. The device-tree story may be different in that I was clearly testing it wrong. I should be using U-Boot but did not, so there is a chance that something actually works contrary to my testing. Any comments to possible paths from here? Is SUSE aware of the network ports functioning on Honeycomb in any configuration? (In reply to Josua Mayer from comment #2) > DPC is embedded in firmware (acpi). ACPI is not fully supported. Switch hardware description to device-tree if you want to use EDK2 based firmware. > What's then needed as a bare minimum is access to the mcbin for setting up > interfaces with NXPs restool, e.g. sudo ls-addni dpmac.9 > This part currently requires additional patches to Linux not yet mainline :( > > There are also patches for configuring the 1gbps interface from ACPI tables > which need to be carried. From my sources what's been taking so long is the > standardization of mdio in acpi - which apparently - was new. > > The device-tree story may be different in that I was clearly testing it > wrong. > I should be using U-Boot but did not, so there is a chance that something > actually works contrary to my testing. > > Any comments to possible paths from here? Try following kernel: https://kernel.suse.com/SLE15-SP3.html > Is SUSE aware of the network ports functioning on Honeycomb in any > configuration? Sorry I don't have access to this hardware. Please reopen if you are still facing this issue. |