All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/devmem2: remove package
Date: Wed, 14 Aug 2019 14:18:55 +0200	[thread overview]
Message-ID: <20190814141855.307cf763@windsurf.home> (raw)
In-Reply-To: <20190814102957.23544-1-unixmania@gmail.com>

Hello,

+Peter in Cc.

On Wed, 14 Aug 2019 07:29:57 -0300
unixmania at gmail.com wrote:

> From: Carlos Santos <unixmania@gmail.com>
> 
> It was here just for backwards compatibility and is not used by any
> package or board after commits
> 
>   59856480b6 packages/devmem2: remove from all board configurations
>   2f6e3eae55 package/ti-gfx: do not use devmem2 in script
> 
> There are address casting issues with 32bit access on a 64bit bus (like
> on the SoC FPGA ARM processors) with this tool. The Busybox version of
> devmem is the most up to date and supports quadword access.
> 
> Fixes: https://bugs.busybox.net/show_bug.cgi?id=10171

I don't particularly care about devmem2, but it was not here just for
"backwards compatibility". It was there also for the cases where people
don't want to use Busybox, but still need a devmem implementation. I'm
not sure how much this use case is important, though.

Peter, could you take a decision on this ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-08-14 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 10:29 [Buildroot] [PATCH v2] package/devmem2: remove package unixmania at gmail.com
2019-08-14 12:18 ` Thomas Petazzoni [this message]
2019-09-23 20:10 ` Thomas Petazzoni

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=20190814141855.307cf763@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --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.