From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10171] devmem2 w (word) is 8 bytes in x86 64 systems
Date: Sun, 11 Aug 2019 23:16:50 +0000 [thread overview]
Message-ID: <bug-10171-163-UsOomBwktP@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10171-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10171
--- Comment #5 from Carlos Santos <unixmania@gmail.com> ---
(In reply to Ciro Santilli from comment #4)
I found that ti-gfx contains a script using devmem2 and submitted a patch to
remove the dependency: https://patchwork.ozlabs.org/patch/1145451/
There are still 8 board configurations that select devmem2, for reasons that I
don't know:
- at91sam9x5ek_dev_defconfig
- at91sam9x5ek_mmc_dev_defconfig
- atmel_sama5d27_som1_ek_mmc_dev_defconfig
- atmel_sama5d2_xplained_mmc_dev_defconfig
- atmel_sama5d3_xplained_dev_defconfig
- atmel_sama5d3_xplained_mmc_dev_defconfig
- atmel_sama5d4_xplained_dev_defconfig
- atmel_sama5d4_xplained_mmc_dev_defconfig
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-11 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 20:20 [Buildroot] [Bug 10171] New: devmem2 w (word) is 8 bytes in x86 64 systems bugzilla at busybox.net
2017-08-07 13:53 ` [Buildroot] [Bug 10171] " 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 [this message]
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-UsOomBwktP@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