public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Roland Caßebohm" <roland.cassebohm@visionsystems.de>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Again Big endian ARM HAL_WRITE_UINT8 problem
Date: Fri, 10 Oct 2003 16:28:00 -0000	[thread overview]
Message-ID: <200310101827.58265.roland.cassebohm@visionsystems.de> (raw)

Hi,

there is still the problem, that the HAL_WRITE_UINT8() macro
on bigendian ARM hardware does not work.

In the following message is a solution suggested, which would
be good IMO.
http://sources.redhat.com/ml/ecos-discuss/2002-07/msg00415.html

I don't know which platform have to use the macros for bigendian
like they are, maybe pid target? I uses the macro and can be set
to bigendian.

I would like to make a patch, but if I use a flag like 
HAL_IO_MACROS_ADDRESS_MUNGING a platform who needs the macros as
they are have to define the flag not to be broken.
Or should I define a flag like HAL_IO_MACROS_NO_ADDRESS_MUNGING
for platforms like snds which don't need the address munging?

Another discussion about this topic:
http://sources.redhat.com/ml/ecos-discuss/2002-07/msg00160.html

Regards,
Roland
-- 

___________________________________________________

VS Vision Systems GmbH, Industrial Image Processing
Dipl.-Ing. Roland Caßebohm
Aspelohe 27A, D-22848 Norderstedt, Germany
http://www.visionsystems.de
___________________________________________________


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

             reply	other threads:[~2003-10-10 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 16:28 Roland Caßebohm [this message]
2003-10-12 12:05 ` Andrew Lunn

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=200310101827.58265.roland.cassebohm@visionsystems.de \
    --to=roland.cassebohm@visionsystems.de \
    --cc=ecos-discuss@sources.redhat.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).