https://bugs.kde.org/show_bug.cgi?id=400079
--- Comment #16 from Brian Kaye <b...@unb.ca> --- (In reply to Harald Sitter from comment #2) > I wonder, I wonder... maybe we should just dump the dmidecode output in a > text KCM. It'd be fairly cheap to do and maintain that way. > > The other option would be to feed selective data into the about system kcm. > BUT that is probably fairly costly from a code POV since we need a whole > bunch of heuristics to determine if a given field is indeed useful (e.g. on > any device that isn't from one of the big computer OEMs any number of the > fields may not be filled which usually means they are filled with > placeholder garbage that we need to manually filter out). Smaller ODMs in > particular also fail to fill fields properly at times. > > e.g. my system is custom built so I have > > System Information > Manufacturer: System manufacturer > Product Name: System Product Name > Version: System Version > Serial Number: System Serial Number > Wake-up Type: Power Switch > SKU Number: SKU > Family: To be filled by O.E.M. Harald :In your case where you have a custom build, you probably don't need the smbios information. But it does raise the issue of custom bios where you might like to put your custom info into the bios. -- You are receiving this mail because: You are watching all bug changes.
