There is no reason it cannot be committed. If the strupr replacement is provided in the same patch, it will be checked in to the trunk.

Rick


On Jan 17, 2009, at 8:50 PM, SimonQian wrote:

Yes.
If this patch can be commited, I'll provide a patch for the entire change to add svf support(including replacement of strupr and vsllink update).
If not, it's OK. I'll only provide an update for vsllink.
Actually, I implemented svf player in my tools.
So I'm not using OpenOCD for svf, but I can test OpenOCD to make sure it works with my targets.

2009-01-18
Best Regards, Simon Qian

SimonQian([email protected]) ---- www.SimonQian.com
发件人: Rick Altherr
发送时间: 2009-01-18  04:23:22
收件人: SimonQian
抄送: 貀vind_Harboe; openocd-development
主题: Re: [Openocd-development] svf support

On Jan 16, 2009, at 7:11 AM, SimonQian wrote:

Hi,
Attachment is patch for svf support and Versaloon update.

command is: svf <filename.svf>
Tested OK to config EMP240T100 with Versaloon.

2009-01-16
Best Regards, Simon Qian

SimonQian([email protected]) ---- www.SimonQian.com
< svf .patch><vsllink.patch>_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development


Everything looks good except that strupr doesn't exist on my system (OS X 10.5). In fact, I don't see any function to do its equivalent either. toupper() is the only thing close, but that only works on a character by character basis. If you need to use the strupr functionality, it should get implemented as a replacement function in src/helper/replacements.c.

--
Rick Altherr
[email protected]

"He said he hadn't had a byte in three days. I had a short, so I split it with him."
 -- Unsigned





--
Rick Altherr
[email protected]

"He said he hadn't had a byte in three days. I had a short, so I split it with him."
 -- Unsigned



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to