Hi Asias,
On 06/12/11 23:00, Asias He wrote:
> On 12/06/2011 06:24 PM, Pekka Enberg wrote:
>> On Tue, Dec 6, 2011 at 5:40 AM, Matt Evans wrote:
>>> term_getc()'s int c has one byte written into it (at its lowest address) by
>>> read_in_full(). This is expected to be the least significant byte, b
On 12/06/2011 06:24 PM, Pekka Enberg wrote:
> On Tue, Dec 6, 2011 at 5:40 AM, Matt Evans wrote:
>> term_getc()'s int c has one byte written into it (at its lowest address) by
>> read_in_full(). This is expected to be the least significant byte, but that
>> isn't the case on BE! Use correct type,
On Tue, Dec 6, 2011 at 5:40 AM, Matt Evans wrote:
> term_getc()'s int c has one byte written into it (at its lowest address) by
> read_in_full(). This is expected to be the least significant byte, but that
> isn't the case on BE! Use correct type, unsigned char. A similar issue
> exists
> in t
term_getc()'s int c has one byte written into it (at its lowest address) by
read_in_full(). This is expected to be the least significant byte, but that
isn't the case on BE! Use correct type, unsigned char. A similar issue exists
in term_getc_iov(), which needs to write a char to the iov rather
