public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Carlos Losada <itel9cl1@yahoo.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] EB40 Virtual Vector Table
Date: Fri, 16 Feb 2007 10:56:00 -0000	[thread overview]
Message-ID: <286795.17012.qm@web62312.mail.re1.yahoo.com> (raw)

I'm having problems getting diag_printf() to work.

Does the EB40 platform implementation use the Virtual
Vector Table mechanism?  Is it fully implemented?

I compared the *.ld files for the POWERPC and ARM and
noticed that the former includes a specific reference
to the VVT which the latter doesn't.  Could just be a
difference in imlementation.

Thanks







 
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2007-02-16 10:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=286795.17012.qm@web62312.mail.re1.yahoo.com \
    --to=itel9cl1@yahoo.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).