From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10171] New: devmem2 w (word) is 8 bytes in x86 64 systems
Date: Sat, 05 Aug 2017 20:20:22 +0000 [thread overview]
Message-ID: <bug-10171-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10171
Bug ID: 10171
Summary: devmem2 w (word) is 8 bytes in x86 64 systems
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ciro.santilli at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
http://free-electrons.com/pub/mirror/devmem2.c
w maps to unsigned long
Let's use uintX_t for all accesses, and introduce q (quadword) for 64 bit
Specially unintuitive since h (half-word) maps to short int, which in x86_64 is
2 bytes, and thus not half of word.
Also can we move the .c source into the buildroot tree itself in the same
directory as the .mk, since it is so tiny. Or create a separate official git
repo for it.
I'll send patch if you agree.
Like this:
https://github.com/cirosantilli/linux-kernel-module-cheat/blob/d871c008fbf0832e502f8ae1367ecf8ab6796aa5/kernel_module/user/devmem3.c
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-08-05 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 20:20 bugzilla at busybox.net [this message]
2017-08-07 13:53 ` [Buildroot] [Bug 10171] devmem2 w (word) is 8 bytes in x86 64 systems bugzilla at busybox.net
2017-08-07 16:00 ` bugzilla at busybox.net
2019-08-11 0:34 ` bugzilla at busybox.net
2019-08-11 6:23 ` bugzilla at busybox.net
2019-08-11 23:16 ` bugzilla at busybox.net
2019-08-12 20:40 ` bugzilla at busybox.net
2019-08-12 23:28 ` bugzilla at busybox.net
2019-09-23 20:10 ` 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-10171-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox