From: Karl Hiramoto <karl@hiramoto.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] arm or armeb?
Date: Fri, 03 Oct 2008 13:53:03 +0200 [thread overview]
Message-ID: <48E6079F.2090508@hiramoto.org> (raw)
In-Reply-To: <8349216a0810030434r3b5d7c29xb5ebc0d8a99cdc6e@mail.gmail.com>
Jean-Marc Beaune wrote:
> Hi,
>
> The details:
>
> - Processor: 16/32 bit *AT91SAM7X256* (ARM7TDMI-S™)
> - 256 K Flash
> - 64 K RAM
> - USB 2.0
> - Ethernet 10/100 Mbits
> - 2 x RS-232
> - ADC (10 bits), CAN, 2 x UARTs, TWI(I2C), 2 x SPI, 3 x timers
> 32bit, SSC, 4 x PWM, WDT, PDC (DMA)
> - Frequency up to 55 MHz
> - JTAG connector (ARM's 2 x 10 pins - ARM-JTAG compatible)
> - Color TFT 128 x 128 pixels
> - SD™/MMC™
> - Mini-joystick
> - Loudspeaker
> - Audio input/output
> - Crystal 18,432 MHz sur support
> - RESET buton
> - Dimension: 128 x 98 mm
>
> The question is not specifically for this hardware but more "when to
> choose arm and when to choose armeb" ?
>
> Thank you
>
AFIK, you can't run linux on an ARM TDMI with 64K of RAM :-)
Using the same endianess as your bootloader will save you from byte
swapping. If you can use the same endianness as the rest of your HW,
it will save the byte sapping operations and may make your system faster.
Some people prefer little endian, because other SW/ drivers has bugs on
little endian machines.
More about endianness you can probably get from googl'ing.
--
Karl
next prev parent reply other threads:[~2008-10-03 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 10:18 [gentoo-embedded] arm or armeb? Jean-Marc Beaune
2008-10-03 11:05 ` Karl Hiramoto
2008-10-03 11:34 ` Jean-Marc Beaune
2008-10-03 11:53 ` Karl Hiramoto [this message]
2008-10-03 13:04 ` Jean-Marc Beaune
2008-10-26 7:59 ` Mike Frysinger
2008-10-03 13:36 ` Jason
2008-10-03 14:32 ` Ned Ludd
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=48E6079F.2090508@hiramoto.org \
--to=karl@hiramoto.org \
--cc=gentoo-embedded@lists.gentoo.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