From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14007 invoked by alias); 15 Jun 2003 02:32:20 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 14794 invoked from network); 15 Jun 2003 02:25:29 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 15 Jun 2003 02:25:29 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 495E72B63; Sat, 14 Jun 2003 22:25:22 -0400 (EDT) Message-ID: <3EEBD912.4050807@redhat.com> Date: Sun, 15 Jun 2003 02:32:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mckennad@esatclear.ie Cc: gdb@sources.redhat.com, insight@sources.redhat.com Subject: Re: USB in GDB/Insight References: <3ee721ee.47d1.0@esatclear.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00293.txt.bz2 > Hi all, > > What is involved in adding a new target to gdb? Also is there any documentation > re this subject? > > At present gdb's RSP supports only Serial and Ethernet communication, and I > am thinking of implementing USB support ( for a PC anyway ). It depends on how the USB's device driver represents the device to the userland. If, for instance, it appears to be a serial device then GDB can talk to it already. If not, things get interesting. You may want to look at the ser* code and implement a serial like usb driver. Andrew