All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6404] New: Buildroot's coreutils 'uname -p' reports 'Unknown' on recent ARM kernels
Date: Thu,  1 Aug 2013 04:30:02 +0000 (UTC)	[thread overview]
Message-ID: <bug-6404-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6404

           Summary: Buildroot's coreutils 'uname -p' reports 'Unknown' on
                    recent ARM kernels
           Product: buildroot
           Version: 2013.05
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: daniel.price at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Buildroot's coreutils uname(1) command has a special patch applied as part of
buildroot.  When you run 'uname -p', it tries to print out extended information
about the processor you are running.  It does this by parsing /proc/cpuinfo. 
I'm not sure of the provenance of this enhancement, but you can read the code
in package/coreutils/coreutils-uname.patch.

However, on recent ARM kernels, the format of /proc/cpuinfo has changed
incompatibly.  Several packages subsequently break.  I believe the commit in
question is this:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=82b5df7bf27ca6cf642499bc3bcae1c93b9ac4ba

So, I recently discovered that when matched with recent ARM kernels, uname -p
on buildroot is simply reporting 'Unknown'.  I'm not really sure what the right
answer might be.  The code doesn't really seem set up to parse the
/proc/cpuinfo file in more than one way.

I am presently using buildroot 2012.11, but the code seems to be the same in
the latest release as well.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-08-01  4:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  4:30 bugzilla at busybox.net [this message]
2013-08-12 20:32 ` [Buildroot] [Bug 6404] New: Buildroot's coreutils 'uname -p' reports 'Unknown' on recent ARM kernels Arnout Vandecappelle
2013-08-13  0:14   ` Martin Banky
2013-08-13  9:20     ` Thomas Petazzoni
2013-08-13 10:12       ` Martin Banky
2013-08-14 12:30   ` Gustavo Zacarias
2013-08-15 13:50     ` Thomas Petazzoni
2013-10-30 22:30 ` [Buildroot] [Bug 6404] " bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-6404-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.