Hi Paul.

On Sat, 17 Jan 2015 18:26:38 +0300, Paul Fertser wrote:
> BTW, thank you for investigating the bug,

It's nice to finally be able to contribute some code. ;)

> I was about to try to reproduce it on STM32F4's I got (thanks to you again),
> and would ultimately fail, of course, as I was going to do that on a LE 
> machine.

At some point, I hope that we can use Cortex-A boards for BE testing (I'm 
hoping to migrate my primary workstation to one myself, thus I can get rid of 
the fan-noise).

> I'm atm preparing an OpenWrt build to be able to run on MIPS devices
> easily.

That sounds cool. I believe that OpenOCD is quite stable on Big Endian hosts 
now - but then again, I've only been using LPC and STM devices, so I have not 
tested with other devices.

(I felt the the big breakthrough in 0.8.0; a real joy to be able to use OpenOCD 
on my host computer)

> On Sat, Jan 17, 2015 at 04:12:20PM +0100, Jens Bauer wrote:
>>> commit 2436ffa9b44911cee7646a197c0eea1e5743c591
>>> 
>>>     Use (uint8_t *) for buf_(set|get)_u(32|64) instead of (void *)
>> 
>> I don't believe that typecasts are evil, but ... at times, they can 
>> silently hide terrible bugs.
> 
> By braces here I meant specific types, not typecasting, please see the
> patch, it doesn't introduce unnecessary casts, I hope.

Sorry for the confusion - I wasn't referring to the description, but the 
problem that required the patch. ;)
There's nothing wrong with the patch or the description in my opinion!


Love
Jens

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to