From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13556 invoked by alias); 17 Nov 2003 16:22:26 -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 13545 invoked from network); 17 Nov 2003 16:22:23 -0000 Received: from unknown (HELO mic.dspfactory.com) (216.16.237.2) by sources.redhat.com with SMTP; 17 Nov 2003 16:22:23 -0000 Subject: RE: [RFC] upload/download command Date: Mon, 17 Nov 2003 16:22:00 -0000 MIME-Version: 1.0 To: kewarken@qnx.com, gdb@sources.redhat.com Cc: From: "Ken Dyck" Message-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-11/txt/msg00128.txt.bz2 >Our QNX pdebug protocol supports an upload/download command.=20=20 >This is handy >for putting binaries onto target system and getting back things like >corefiles. Out of curiosity, which way is up? In some circles, particularly in DSP development, which I am most familiar with (I'm not sure if it extends to the rest of the embedded community), the term 'download' usually refers to pushing data down onto the target from the host machine. In the internet world, on the other hand, the term is used to mean pulling some data down from a remote machine onto a local host. In what sense is the pdebug protocol using the terms? Ken