-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebased patches from beaker-fork #31
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by Petr Oros <poros@redhat.com>
This patch makes it possible to run cross-platform unit tests by faking the architecture returned by uname(2) to match the format of /proc/cpuinfo.
Not sure how to contribute these back to the Universität Regensburg list...
In spite of its name, the SCSI_IOCTL_GET_PCI ioctl will actually return the kernel name for the underlying SCSI adapter no matter whether it's on the PCI bus or not. For example an IBM VIO SCSI adapter on the vio bus might return 30000002 for this ioctl. Since this doesn't look like a PCI bus address, the guessBusInfo() function would then make a bad guess, returning businfo as parisc@30000002 which is not right. We can figure out the right businfo without guessing by looking in sysfs instead.
Older IBM POWER systems (for example JS20) have a /memory-controller@* node in their device tree, which exposes DIMM info under IBM-specific properties.
The "64-bit capable" bit can also be set for CPUs which are not x86-based, like Itanium and ARM. Changed it to "lm" (long mode) instead which matches the existing Linux CPU flag.
The rest of the codebase expects to only find at most one "memory" node, even though the SMBIOS data may indicate more than one. If we really do find more than one memory array with type System Memory in SMBIOS, we just discard the subsequent ones and place all memory devices (DIMMs) into the first memory array.
This avoids accidentally parenting a SCSI device onto the wrong host from the previous iteration of the loop, if no parent device was found in the current iteration.
This matches the behaviour of guessBusInfo() for USB device names of the form host-port:config.interface. This patch allows SCSI devices where the host is a USB device to be parented correctly.
Signed-off-by: Petr Oros <poros@redhat.com>
merged upstream. |
lyonel
added a commit
that referenced
this pull request
Apr 23, 2020
…ivaprasadbhat/lshw:master into master
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.