From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Date: Thu, 4 Jun 2020 15:10:18 +0200 Subject: [PATCH 6/6] cmd: Add a memory-search command In-Reply-To: References: <20200602192642.1.Ibc067a3d1c5425aa60dfb9314a23d6dc5c2e480d@changeid> <20200602192642.6.Iaf24bd607de3836b8cd474fd0ae88452396ccb62@changeid> <86c37194-8b56-0186-9acb-ecf67ab27c06@xilinx.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 04. 06. 20 15:09, Simon Glass wrote: > Hi Michal, > > On Thu, 4 Jun 2020 at 07:05, Michal Simek wrote: >> >> On 04. 06. 20 15:00, Simon Glass wrote: >>> Hi Michal, >>> >>> On Thu, 4 Jun 2020 at 02:33, Michal Simek wrote: >>>> >>>> On 04. 06. 20 4:59, Simon Glass wrote: >>>>> Hi Michal, >>>>> >>>>> On Wed, 3 Jun 2020 at 01:08, Michal Simek wrote: >>>>>> >>>>>> On 03. 06. 20 3:26, Simon Glass wrote: >>>>>>> It is useful to be able to find hex values and strings in a memory range. >>>>>>> Add a command to support this. >>>>>>> >>>>>>> cmd: Fix 'md' and add a memory-search command >>>>>>> At present 'md.q' is broken. This series provides a fix for this. It also >>>>>>> implements a new memory-search command called 'ms'. It allows searching >>>>>>> memory for hex and string data. >>>>>>> END >>>>>> >>>>>> END likely shouldn't be here. >>>>> >>>>> Oops >>>>> >>>>>> Recently I have met with the case that I have strings in i2c eeprom and >>>>>> need to move them to variable. And I didn't find any way how to do it. >>>>>> That's why I am curious if you are introducing this new command to also >>>>>> in case of string search to fill any variable which will contain this >>>>>> string. >>>>> >>>>> Sorry it is just for memory-mapped things at present. But like we have >>>>> 'i2c md' I suppose we could have 'i2c ms'. >>>> >>>> It wouldn't matter. I can do i2c read to memory and then ms to do it. >>>> But question remains. When you find the string in memory how you want to >>>> work with it? You need to have a way to move it to variable and use it >>>> as the part of your script. >>> >>> Ah OK I didn't think of that. >>> >>> I suppose you could use $mempos to find it, if we had a way to move a >>> string from memory to an env var? Does that exist? If not, setexpr >>> could be enhanced to do it quite easily. >> >> You will find it that what's your ms does. But I haven't seen that >> setexpr part of that. >> Also when I find that string I should be able to for example write my >> variable to that location. >> >> What was the use case you had in your mind how you want to handle string >> when you find it? > > My use case is just to interactively search memory for things - e.g. > ACPI tables, pointers to addresses and the like. Useful for debugging. ok. Got it. M