smxi/inxi

Fork 2

Code Issues 14 Pull requests Projects Releases Packages Wiki Activity

E2K: fixed getting bitness for MCST Elbrus CPU when using "-f" option #196

Closed

r-a-sattarov wants to merge 1 commit from master into master

pull from: master

merge into: smxi:master

smxi:two

smxi:one

Conversation 2 Commits 1 Files changed 1 +1 -1

r-a-sattarov commented

2019年11月02日 13:38:41 +01:00

(Migrated from github.com)

Copy link

After editing:
CPU: Topology: 8-Core model: E8C bits: 64 type: MCP L2 cache: N/A
Speed: 1300 MHz min/max: N/A Core speeds (MHz): 1: 1300 2: 1300 3: 1300 4: 1300 5: 1300 6: 1300 7: 1300 8: 1300
Flags: N/A

About this processor:

https://en.wikipedia.org/wiki/Elbrus-8S

Before editing: CPU: Topology: 8-Core model: E8C bits: N/A type: MCP L2 cache: N/A Speed: 1300 MHz min/max: N/A Core speeds (MHz): 1: 1300 2: 1300 3: 1300 4: 1300 5: 1300 6: 1300 7: 1300 8: 1300 Flags: N/A After editing: CPU: Topology: 8-Core model: E8C bits: 64 type: MCP L2 cache: N/A Speed: 1300 MHz min/max: N/A Core speeds (MHz): 1: 1300 2: 1300 3: 1300 4: 1300 5: 1300 6: 1300 7: 1300 8: 1300 Flags: N/A About this processor: - https://en.wikipedia.org/wiki/Elbrus-8S

smxi commented

2019年11月02日 18:57:11 +01:00

(Migrated from github.com)

Copy link

Please file a normal issue so I can get full elbrus e2k support added, I didn't realize this was an entirely new cpu type.

I need to see as a basic starting point, but file this as an issue, not as a pull request, /proc/cpuinfo, but I will probably need to see more because this is a new type, unless it falls under sparc logic, in which case, I need to trigger spark test events. I've added this patch to pinxi so you can test it but it's better to add all the support at once rather than in little bits and pieces.

To add support I need ideally a /proc/cpuinfo output for each type of this cpu, including the latest one, then we can see if L1/L2/L3 cache data is obtainable. But don't do it in pull requests, do it in a normal issue so we can get full support done.

Please file a normal issue so I can get full elbrus e2k support added, I didn't realize this was an entirely new cpu type. I need to see as a basic starting point, but file this as an issue, not as a pull request, /proc/cpuinfo, but I will probably need to see more because this is a new type, unless it falls under sparc logic, in which case, I need to trigger spark test events. I've added this patch to pinxi so you can test it but it's better to add all the support at once rather than in little bits and pieces. To add support I need ideally a /proc/cpuinfo output for each type of this cpu, including the latest one, then we can see if L1/L2/L3 cache data is obtainable. But don't do it in pull requests, do it in a normal issue so we can get full support done.

smxi commented

2019年11月02日 21:04:40 +01:00

(Migrated from github.com)

Copy link

Note, a quick look shows that more than just a single elbrus cpu id, e2k, is needed, there are many, so I'd like to get that handled in a more complete way, this fix only handles one variant.

Pull request closed

Please reopen this pull request to perform a merge.

Reviewers

No reviewers

Labels

Clear labels

Android

Ansible-Chef-Motd

Apple-output-error-fixes-only

OSX is not supported beyond fixing Perl output errors.

Character-encoding-issue

Chuckler

Brings a smile...

Close-If-No-Response

Closed-No-Response

Once a user fails to respond, within a few weeks, replace close if no response label with this one

Completed

Cygwin

yep, running on windows!!

The issue is about an inxi feature that is intended, and is not a bug

Feature-request-exists

A feature request issue for something inxi already supports

Fixed

Flatpak-Snap-Appimage

FreeBSD-closed-no-data-supplied

Tired of having to get Linux users to do FreeBSD's work for them, no data, no help!

related to adding html output switch

Inadequate-Data-Source

Interesting-problem

Not necessarily related to inxi but still interesting.

Intermittent-issue

Issue comes and goes, and is not inxi related, though inxi exposes it when it happens

Invalid

Invalid-Leave-Visible

JSON-XML-export

Legacy Issue - Non Current inxi

Legacy Issue - Pre v 3.0

Locales

non C locales support

Microsoft WSL

MIPS-CPU

Mips, Loongson

Not-Currently-Possible

Ongoing-Updates

OSX

Outside-Of-Program-Scope

Oversight

Forgot to add in data type in one area

Packaging

packaging issues belong to the distro making the package. With one exception: TinyCore.

Required-Debugger-Data-Ignored

The poster failed to supply the required debugger data, and so the issue cannot be resolved.

Required-Work-Not-Done

If one of the Required labels was applied, and the issue poster did not do that work, and I did, keep this as a reminder.

Requires-Code

This issue requires the person making the request supply the code needed to resolve the issue.

Requires-Debugger-Data

This issue poster must supply the requested debugger data, it cannot be resolved without it.

Requires-Docs

This issue requires that the person requesting it supply the related documentation data and files.

Requires-Research

This issue requires that the poster do the research needed to understand and complete the issue. Research is easily 95% of any task in inxi.

Review

RTFM-(or -h)

Yes, an issue cased by not reading anything.

SSH-Access-Not-Given

SSH-Required

no support without SSH access, non trivial system issue.

Task

Waiting-Fix-Confirm

Wayland

anything where wayland seems to be the cause

Windows

No, really, people have asked!

Won't-Fix

ZFS

ZFS fs specific issues

No labels

Android

Ansible-Chef-Motd

Apple-output-error-fixes-only

Character-encoding-issue

Feature-request-exists

Fixed

Flatpak-Snap-Appimage

FreeBSD-closed-no-data-supplied

Inadequate-Data-Source

Interesting-problem

Intermittent-issue

Invalid

Invalid-Leave-Visible

JSON-XML-export

Legacy Issue - Non Current inxi

Legacy Issue - Pre v 3.0

Locales

Microsoft WSL

MIPS-CPU

Not-Currently-Possible

Ongoing-Updates

OSX

Outside-Of-Program-Scope

Required-Debugger-Data-Ignored

Required-Work-Not-Done

Requires-Code

Requires-Debugger-Data

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

smxi/inxi!196

No description provided.

Delete branch "master"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?