>> oops, missed them.  I guess I could #ifdef them out (richard?).  Those 
>> assignments haven't done anything useful since 2002-02-08 when the arm 
>> became multi-arch partial.
> 
> 
> Erm, maybe.  When you open a remote target via RDP you get the option to 
> ask the target to set the endianness (or you can ask "tell me your 
> endianness").  If you select an endianness and it isn't supported, you 
> should get back the error RDIError_WrongByteSex; if you ask it to tell 
> you, it will report back either RDIError_BigEndian or 
> RDIError_LittleEndian.  The idea is to allow the board to tell you what it 
> can support.
> 
> What should be done will depend on when we open the connection to the 
> board.  If it's after we've selected an image to send, then we should pass 
> the endianness of the image in the initial connection.  If it's before, 
> then we should ask the board.  I think the best solution is to delay 
> connecting to the target until we have an image if possible.  That avoids 
> the situation where we have a target that is bi-endian (eg a simulator -- 
> most boards are fixed-endian) and it reports the one we don't want -- 
> there's no way for the remote end to say "I'm currently foo, but I can 
> also to bar".

Try the attached.  It warns the user of the conflict and points them at 
"set endian" for how to change it.  The other alternative is to force 
the endianess based on what the target indicates, but as you note, that 
could lead to interesting conflicts.

Andrew