From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Spartan FPGA patch
Date: Wed, 07 Nov 2007 14:33:24 +0100 [thread overview]
Message-ID: <20071107133324.CBCAC248D3@gemini.denx.de> (raw)
In-Reply-To: Your message of "Wed, 07 Nov 2007 13:43:32 +0200." <4731A4E4.20308@inaccessnetworks.com>
In message <4731A4E4.20308@inaccessnetworks.com> you wrote:
>
> > So let me repeat my question: is there any special reason why "val"
> > has to be a "char" type? Why not making it an "int" ?
>
> Because you will run into endianness problems. You want to treat an
> "unsigned char" buffer as a bitstream, reading the MSB every time. How
> are you going to do this portably (in both big and little endian
> architectures) with an "int" type, which is at least 2 bytes wide?
Oops? I can't parse that. What's the difference between "signed char"
and "int" except the number of bits?
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
"Wish not to seem, but to be, the best." - Aeschylus
next prev parent reply other threads:[~2007-11-07 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 15:51 [U-Boot-Users] Spartan FPGA patch Aggelos Manousarides
2007-11-03 21:46 ` Wolfgang Denk
2007-11-05 12:58 ` Aggelos Manousarides
2007-11-05 19:21 ` Wolfgang Denk
2007-11-07 11:43 ` Aggelos Manousarides
2007-11-07 13:33 ` Wolfgang Denk [this message]
2007-11-07 16:49 ` Andreas Schweigstill
2007-11-07 19:51 ` Wolfgang Denk
2007-11-14 12:05 ` Aggelos Manousarides
2007-11-14 19:46 ` Wolfgang Denk
2007-11-07 14:29 ` Matthias Fuchs
2007-11-07 19:48 ` Wolfgang Denk
2007-11-07 21:07 ` Jerry Van Baren
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=20071107133324.CBCAC248D3@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