Re: [PATCH] dspbridge: Fix atoi to support hexadecimal numbers correctly

2010-12-22 Thread Ramirez Luna, Omar
On Sun, Dec 12, 2010 at 7:39 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: For some strange reason, the DSP base image node/object properties description string stores hexadecimal numbers with a 'h' or 'H' suffix instead of a '0x' prefix. This causes parsing issue because the

Re: [PATCH] dspbridge: Fix atoi to support hexadecimal numbers correctly

2010-12-22 Thread Ramirez Luna, Omar
On Wed, Dec 22, 2010 at 7:00 PM, Ramirez Luna, Omar omar.rami...@ti.com wrote: On Sun, Dec 12, 2010 at 7:39 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: For some strange reason, the DSP base image node/object properties description string stores hexadecimal numbers with a 'h'

Re: [PATCH] dspbridge: Fix atoi to support hexadecimal numbers correctly

2010-12-16 Thread Laurent Pinchart
Hi everybody, Ping ? On Sunday 12 December 2010 14:39:37 Laurent Pinchart wrote: For some strange reason, the DSP base image node/object properties description string stores hexadecimal numbers with a 'h' or 'H' suffix instead of a '0x' prefix. This causes parsing issue because the dspbridge

[PATCH] dspbridge: Fix atoi to support hexadecimal numbers correctly

2010-12-12 Thread Laurent Pinchart
For some strange reason, the DSP base image node/object properties description string stores hexadecimal numbers with a 'h' or 'H' suffix instead of a '0x' prefix. This causes parsing issue because the dspbridge atoi() implementation relies on strict_strtoul(), which will return an error because