public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Chris Zimman" <czimman@bloomberg.com>
To: "andrew wiggin" <end3er@gmail.com>
Cc: <ecos-devel@ecos.sourceware.org>
Subject: RE: Serial VS Diagnostic interface
Date: Wed, 14 Jan 2009 13:25:00 -0000	[thread overview]
Message-ID: <F31C1582037F5041B0CD525FD870AE6A012682BA@ny2545.corp.bloomberg.com> (raw)
In-Reply-To: <69b5c5160901140502x62d7e748uc65136d473f83fb@mail.gmail.com>

> Actually as it just inline code. I have already checked it is
> correctly included. Maybe I should have been more explicit: Is there
> anything to ensure the HW serial driver is correctly initialized ?
> Where should pc_serial_lookup() be called in a normal behavior ?

If you can build the serial tests and they pass, you should be in good shape.
Alternatively, if opening "/dev/ser0" succeeds, you're good to go.
 
> I would have another question then, I have noticed that with GCC 4.2.2
> (which is the one I use), the DEVTAB_ENTRY may be removed if the
> TABLE_END is declared before adding any additional entry. Is anybody
> else having the same issue ?

I don't use GCC 4.x having moved to EABI a while ago, so I'm afraid I can't
offer any advice here.

--Chris

  reply	other threads:[~2009-01-14 13:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 19:58 andrew wiggin
2009-01-14  0:21 ` Chris Zimman
2009-01-14 13:03   ` andrew wiggin
2009-01-14 13:25     ` Chris Zimman [this message]
2009-01-14 13:30       ` damien millescamps
2009-01-14 14:19         ` Nick Garnett
2009-01-14 14:58           ` damien millescamps
2009-01-14 15:10             ` Nick Garnett
2009-01-16 16:20               ` andrew wiggin
2009-01-16 16:23                 ` Chris Zimman
2009-01-16 17:35                   ` Jonathan Larmour
2009-01-16 19:02                     ` andrew wiggin
2009-01-14 13:45       ` Chris Zimman

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=F31C1582037F5041B0CD525FD870AE6A012682BA@ny2545.corp.bloomberg.com \
    --to=czimman@bloomberg.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=end3er@gmail.com \
    /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).