Thank you,

All right, but actually I didn't buy this hardware yet, I'm just
investigating and ceating crossdev toolchain.

So, not possible to know what's the difference between 'arm' and 'armeb'
machines?

Cheers,
/JM

On Fri, Oct 3, 2008 at 1:53 PM, Karl Hiramoto <karl@hiramoto.org> wrote:

> 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
>
>
>
>
>
>
>
>


-- 
Jean-Marc