From: Grant Edwards <grante@visi.com>
To: jeremy <chienyul@home.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] HAL register write problem
Date: Fri, 19 Jan 2001 08:33:00 -0000 [thread overview]
Message-ID: <20010119103729.A11030@visi.com> (raw)
In-Reply-To: <000e01c08183$65c3bf00$7c6509c0@viatech.com>
On Thu, Jan 18, 2001 at 11:17:55AM -0800, jeremy wrote:
> #define CYG_DEVICE_SERIAL_RS232_UART_UBRDIV \
> ((volatile cyg_uint16 *) CYG_DEVICE_SERIAL_RS232_UART_BASE + 0x14)
Are you sure that you want
((volatile cyg_uint16 *)XXX + 0x14)
and not
((volatile cyg_uint16 *)(XXX+0x14))
I've been bitten by that one...
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-01-19 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 14:07 jeremy
2001-01-18 15:11 ` Gary Thomas
2001-01-18 19:04 ` Jonathan Larmour
2001-01-19 8:33 ` Grant Edwards [this message]
2001-01-19 19:37 ` jeremy
2001-01-22 0:40 ` Jesper Skov
2001-01-23 16:16 jeremy
2001-01-24 7:18 ` Grant Edwards
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=20010119103729.A11030@visi.com \
--to=grante@visi.com \
--cc=chienyul@home.com \
--cc=ecos-discuss@sourceware.cygnus.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).