From kde-core-devel Mon Jul 30 22:30:51 2007 From: Matthew Woehlke Date: Mon, 30 Jul 2007 22:30:51 +0000 To: kde-core-devel Subject: Re: State of kdefx Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118583472614778 Kevin Ottens wrote: > Le lundi 30 juillet 2007, Matthew Woehlke a écrit : >> Well it's possibly ugly and not a patch, but see kdefx/kcpuinfo.cpp :-). > > *looks* Uuurgh! heh, I guess now you know why we don't like kdefx ;-). But see below... > Well, seeing it's very low level and the amount of code, it'd be best to port > this as a HAL probing addon... Shouldn't be that difficult. And then it's > trivial to expose via solid. Ok. But I am increasingly lost how to go about that, my ability to do something unaided is going down, down... :-) > Advantages of doing it this way is that the > probing of the processor would be done only once in the system, not each time > an application ask for the information. I was going to complain that 'CPUID' is much cheaper than a function call. Then I looked at kcpuinfo.cpp :-). Actually to do this well is even worse than the current kdefx code, because you have to (at least, you would be nice to ;-) ) support MS and Solaris compilers also (and maybe others?), but I'd still trust that over /proc/cpuinfo (which is brittle on Linux and non-existant on other OS's, at least on Windows). I can (and would be happy to) help with that much at least. -- Matthew "...anyway, that's my 0.02 toasters" (with apologies to Niel)