From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unaligned data transfers?
Date: Fri, 04 Jun 2010 17:44:07 +0200 [thread overview]
Message-ID: <20100604154407.D4CCE16068C@gemini.denx.de> (raw)
In-Reply-To: <1275655059.2450.78.camel@tor-desktop>
Dear Tor Krill,
In message <1275655059.2450.78.camel@tor-desktop> you wrote:
>
> Is it safe to assume that the address is correct or bail out with an
> error message if source/destinaton address isn't correctly aligned for
> the underlaying HW?
No, you are supposed to know what you are doing and provide addresses
that are valid.
Like Perl, U-Boot gives you enough rope to hang yourself.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A quarrel is quickly settled when deserted by one party; there is no
battle unless there be two. - Seneca
prev parent reply other threads:[~2010-06-04 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 12:37 [U-Boot] Unaligned data transfers? Tor Krill
2010-06-04 15:44 ` Wolfgang Denk [this message]
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=20100604154407.D4CCE16068C@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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