From: "andrew wiggin" <end3er@gmail.com>
To: "Chris Zimman" <czimman@bloomberg.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Serial VS Diagnostic interface
Date: Wed, 14 Jan 2009 13:03:00 -0000 [thread overview]
Message-ID: <69b5c5160901140502x62d7e748uc65136d473f83fb@mail.gmail.com> (raw)
In-Reply-To: <F31C1582037F5041B0CD525FD870AE6A012682AD@ny2545.corp.bloomberg.com>
On Wed, Jan 14, 2009 at 1:20 AM, Chris Zimman <czimman@bloomberg.com> wrote:
>> I am working with eCos on an AT91 platform for several month now, and
>> I have always used the serial port as a diagnostic interface for
>> debugging purpose. However, now I need to use it as a standard serial
>> in order to be able to use the O_NONBLOCK flag but I couldn't find a
>> way to use the 16x55 serial driver instead of the haldiag interface:
>> whatever I do, only the haldiag interface is selected, and removing
>> the haldiag seems to make it impossible to compile.
>>
>> I know I can use the solution consisting in replacing the GETC
>> function with a nonblocking one, and patching whatever function may
>> need blocking calls on it, but I can't imagine there is no way in eCos
>> to select whether my only serial port shall be considered as a
>> diagnostic interface or a _real_ serial port.
>>
>> Any clue will be welcome.
>
> Make sure you have the hardware serial port drivers compiled in. With that
> you can use "/dev/ser0" etc. instead of "/dev/haldiag" and use non-blocking
> interfaces.
>
> --Chris
>
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 ?
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 ?
--
Andrew W.
next prev parent reply other threads:[~2009-01-14 13:03 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 [this message]
2009-01-14 13:25 ` Chris Zimman
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=69b5c5160901140502x62d7e748uc65136d473f83fb@mail.gmail.com \
--to=end3er@gmail.com \
--cc=czimman@bloomberg.com \
--cc=ecos-devel@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).