Re: [Openocd-development] RFC Release Cycle

2011-06-21 Thread Xiaofan Chen
On Tue, Jun 21, 2011 at 1:30 PM, Øyvind Harboe oyvind.har...@zylin.com wrote: After some consideration, I've changed my view to that the release manager should have git access and that the master branch developers *should* follow the release managers marching orders and that we follow the

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Steve Bennett
On 21/06/2011, at 3:59 PM, Laurent Gauch wrote: On 21/06/2011, at 1:07 AM, Laurent Gauch wrote: / // / On Mon, Jun 20, 2011 at 1:00 PM, Steve Bennett steveb at workware.net.au https://lists.berlios.de/mailman/listinfo/openocd-development wrote: // // On 20/06/2011, at 8:54 PM, Øyvind

Re: [Openocd-development] Openocd release known issues

2011-06-21 Thread Spencer Oliver
Try this: http://repo.or.cz/w/jimtcl.git/commit/fbc998db178da5c462e164b63da128a7d7412e37 With your recent changes, now 'make distcheck' works for me. Many thanks :-) I am away on holiday at the moment so will not get time to look at this again until next week. Cheers Spen

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Laurent Gauch
Steve Bennett wrote: On 21/06/2011, at 3:59 PM, Laurent Gauch wrote: On 21/06/2011, at 1:07 AM, Laurent Gauch wrote: / // / On Mon, Jun 20, 2011 at 1:00 PM, Steve Bennett steveb at workware.net.au https://lists.berlios.de/mailman/listinfo/openocd-development wrote: //

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Steve Bennett
On 21/06/2011, at 4:45 PM, Laurent Gauch wrote: Steve Bennett wrote: On 21/06/2011, at 3:59 PM, Laurent Gauch wrote: On 21/06/2011, at 1:07 AM, Laurent Gauch wrote: / // / On Mon, Jun 20, 2011 at 1:00 PM, Steve Bennett steveb at workware.net.au

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Xiaofan Chen
On Tue, Jun 21, 2011 at 2:45 PM, Laurent Gauch laurent.ga...@amontec.com wrote: Latest version, 1.0.4. Same behaviour on both MacOSX and Linux. Sure. I'll ask if they would like to fix this problem. I will let you know what useful response I get. Great. But are you sure to have the

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Xiaofan Chen
On Tue, Jun 21, 2011 at 2:55 PM, Xiaofan Chen xiaof...@gmail.com wrote: But are you sure to have the correct libusb version. On linux and mac, the libusb is the kernel driver for the d2xx. This has been discussed before and I think in this case an exception should be granted and the patch

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Steve Bennett
On 21/06/2011, at 5:01 PM, Xiaofan Chen wrote: On Tue, Jun 21, 2011 at 2:55 PM, Xiaofan Chen xiaof...@gmail.com wrote: But are you sure to have the correct libusb version. On linux and mac, the libusb is the kernel driver for the d2xx. This has been discussed before and I think in this case

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal / OBJECTION

2011-06-21 Thread Laurent Gauch
Xiaofan Chen wrote: On Tue, Jun 21, 2011 at 2:55 PM, Xiaofan Chen xiaof...@gmail.com wrote: But are you sure to have the correct libusb version. On linux and mac, the libusb is the kernel driver for the d2xx. This has been discussed before and I think in this case an exception should

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal

2011-06-21 Thread Laurent Gauch
Steve Bennett wrote: On 21/06/2011, at 5:01 PM, Xiaofan Chen wrote: On Tue, Jun 21, 2011 at 2:55 PM, Xiaofan Chen xiaof...@gmail.com wrote: But are you sure to have the correct libusb version. On linux and mac, the libusb is the kernel driver for the d2xx. This has been

Re: [Openocd-development] [PATCH 2/3] ft2232: Failure to get latency should not be fatal

2011-06-21 Thread Steve Bennett
On 21/06/2011, at 5:18 PM, Laurent Gauch wrote: Steve Bennett wrote: On 21/06/2011, at 5:01 PM, Xiaofan Chen wrote: On Tue, Jun 21, 2011 at 2:55 PM, Xiaofan Chen xiaof...@gmail.com wrote: But are you sure to have the correct libusb version. On linux and mac, the libusb is the

[Openocd-development] [OpenOCD] [PATCH 1/1] load_image should use virtual (p_vaddr) instead of physical (p_paddr) ELF segment addr

2011-06-21 Thread Drasko DRASKOVIC
Hi all, yesterday I run into the ELF like this : Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x74 0x8000 0x 0xe1f18 0xe1f18 RWE 0x1 LOAD 0x0e1f8c 0x0060f028 0x 0x1103f 0x1103f RWE 0x1 As it can be

Re: [Openocd-development] [OpenOCD] [PATCH 1/1] load_image should use virtual (p_vaddr) instead of physical (p_paddr) ELF segment addr

2011-06-21 Thread Drasko DRASKOVIC
Some more posts on this interesting topic : http://blackfin.uclinux.org/gf/project/u-boot/tracker/?action=TrackerItemEdittracker_item_id=642 http://lists.gnu.org/archive/html/bug-gnu-utils/2002-08/msg00324.html Seems to me that solution proposed in the patch is OK, but I am still wondering : is

Re: [Openocd-development] bitbanging ft2232 dongle port from TCL is TOO DANGEROUS : PLEASE COMMENT

2011-06-21 Thread Phil Fong
My objective is not to block feature.Never,never,never ... But we have to avoid any trouble in generic ft2232 driver regarding specific layout. That's all. Your TCL bitbang will control the port of the FTDI from an higher level than FT2232.c. OK but you TCL

Re: [Openocd-development] [OpenOCD] [PATCH 1/1] load_image should use virtual (p_vaddr) instead of physical (p_paddr) ELF segment addr

2011-06-21 Thread Øyvind Harboe
http://www.mail-archive.com/bug-grub@gnu.org/msg00715.html From 1999? Time flies, eh? What do you think ? Until we understand this better, I think we can wait with applying the patch. Look at gdb source code? Perhaps bfd library? -- Øyvind Harboe Can Zylin Consulting help on your

Re: [Openocd-development] [OpenOCD] [PATCH 1/1] load_image should use virtual (p_vaddr) instead of physical (p_paddr) ELF segment addr

2011-06-21 Thread Drasko DRASKOVIC
On Tue, Jun 21, 2011 at 6:18 PM, Øyvind Harboe oyvind.har...@zylin.com wrote: http://www.mail-archive.com/bug-grub@gnu.org/msg00715.html From 1999? Time flies, eh? For BDF time flies slowely ;)... Anyway, I gave this just as example of implementation (as I underlined, btw.), but real reasons

Re: [Openocd-development] Request for review: driver for Keil ULINK

2011-06-21 Thread Christopher Harvey
On Tue, 21 Jun 2011 18:34:16 +0200, Martin Schmölzer martin.schmoel...@student.tuwien.ac.at wrote: Hi, my ULINK driver for OpenOCD is finally in a usable state. Attached is a patch set that adds this driver + the custom firmware for the ULINK adapter. Currently, this is only tested with an

Re: [Openocd-development] [OpenOCD] [PATCH 1/1] load_image should use virtual (p_vaddr) instead of physical (p_paddr) ELF segment addr

2011-06-21 Thread Michael Schwingen
Am 06/21/2011 07:19 PM, schrieb Drasko DRASKOVIC: Perhaps bfd library? Yes, that would be the right place, but I hoped to avoid further digging ;). Here is something interesting, from the gdb's src/bfd/elf.c, line 963 (and it is related to one of the posts I mentioned previously) : if

Re: [Openocd-development] Request for review: driver for Keil ULINK

2011-06-21 Thread Martin Schmölzer
On Tuesday 21 June 2011 19:11:17 Christopher Harvey wrote: Hi Martin, I've got a ulink at home with an MCB board (I forgot the exact number), so this is exciting news for me. I've been wanting to lean the internals of OCD and Jtag for a while, could anybody suggest some technical