From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3817 invoked by alias); 7 May 2005 07:54:59 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 2814 invoked from network); 7 May 2005 07:54:43 -0000 Received: from unknown (HELO pcsmail.patni.com) (203.124.139.197) by sourceware.org with SMTP; 7 May 2005 07:54:43 -0000 Received: from ruby.patni.com (ruby [204.165.186.9]) by pcsmail.patni.com (8.12.11/8.12.9) with ESMTP id j477s4IS029124 for ; Sat, 7 May 2005 13:24:05 +0530 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sat, 07 May 2005 08:27:00 -0000 Message-ID: <374639AB1012AA4C840022842AA95BC20506A77F@ruby.patni.com> From: "Bhatia, Deepak" To: Subject: [ECOS] Understanding Not Clear About VSR X-SW-Source: 2005-05/txt/msg00101.txt.bz2 Hello, Referring to the para below "The VSR table is located at a fixed memory location. This allows an applic= ation running from RAM, which is a typical debug configuration, to take control over cert= ain exception service routines while keeping the ROM monitor in charge of debug exception handler= s." In case the application is running in RAM under debug mode do can applicati= on use the VSR for exception handling. Regards Deepak -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss