[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #5658] Submission of libproccpuinfo

From: Thomas Cort
Subject: [Savannah-register-public] [task #5658] Submission of libproccpuinfo
Date: Sun, 18 Jun 2006 12:22:27 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20060426 Firefox/


                 Summary: Submission of libproccpuinfo
                 Project: Savannah Administration
            Submitted by: tcort
            Submitted on: Sunday 06/18/2006 at 12:22
         Should Start On: Sunday 06/18/2006 at 00:00
   Should be Finished on: Wednesday 06/28/2006 at 00:00
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Percent Complete: 0%
             Open/Closed: Open
                  Effort: 0.00



A new project has been registered at Savannah 
The project account will remain inactive until a site admin approve or
discard the registration.


While this item will be useful to track the registration process, approving
or discarding the registration must be done using the specific "Group
Administration" page, accessible only to site administrators, effectively
logged as site administrators (superuser):


######### REGISTRATION DETAILS ######### 

Full Name:

System Group Name:

  non-GNU software & documentation

  GNU General Public License V2 or later

  libproccpuinfo - GPL C library for parsing /proc/cpuinfo files.

The format of /proc/cpuinfo changes between architectures. For instance, the
clock speed key is "cpu MHz" on amd64/hppa/x86/ia64, while ppc uses "clock",
sparc uses "CPU0ClkTck", alpha uses "cycle frequency [Hz]", and m68k uses
"Clocking". On sparc it gets more complicated as the CPU speed is in hex on
some systems and in decimal on others. On alpha, the clock speed is usually
followed by " est.", but on SMP systems it is not. Those are just a few of
the many little blips one has to look out for. Very few programs that gather
information from /proc/cpuinfo can take into account all of the differences.
That is why I am working on this library for parsing /proc/cpuinfo.

Here is a current snapshot of my code. It is a work in progress.

Other Software Required:
  This library doesn't depend on any libraries or external programs. There is
a chance it might some day depend on bison and flex, but they are both free


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]