Re: [U-Boot] [PATCH] net: Use u32 instead of ulong for transaction ID in bootp

2015-04-15 Thread Michal Simek
On 04/15/2015 03:45 PM, Joe Hershberger wrote: > Hi Michal, > > On Wed, Apr 15, 2015 at 5:50 AM, Michal Simek > wrote: >> >> From: Siva Durga Prasad Paladugu >> >> Based on rfc951 transaction ID has 4 bytes which is not the case when >> ulong type is used on ARM64. >> Use u32 type which is well

Re: [U-Boot] [PATCH] net: Use u32 instead of ulong for transaction ID in bootp

2015-04-15 Thread Joe Hershberger
Hi Michal, On Wed, Apr 15, 2015 at 5:50 AM, Michal Simek wrote: > > From: Siva Durga Prasad Paladugu > > Based on rfc951 transaction ID has 4 bytes which is not the case when > ulong type is used on ARM64. > Use u32 type which is well defined for all archs. > > BOOTP_VENDOR_MAGIC is also 4 bytes

Re: [U-Boot] [PATCH] net: Use u32 instead of ulong for transaction ID in bootp

2015-04-15 Thread Thierry Reding
On Wed, Apr 15, 2015 at 12:50:59PM +0200, Michal Simek wrote: > From: Siva Durga Prasad Paladugu > > Based on rfc951 transaction ID has 4 bytes which is not the case when > ulong type is used on ARM64. > Use u32 type which is well defined for all archs. > > BOOTP_VENDOR_MAGIC is also 4 bytes. >

[U-Boot] [PATCH] net: Use u32 instead of ulong for transaction ID in bootp

2015-04-15 Thread Michal Simek
From: Siva Durga Prasad Paladugu Based on rfc951 transaction ID has 4 bytes which is not the case when ulong type is used on ARM64. Use u32 type which is well defined for all archs. BOOTP_VENDOR_MAGIC is also 4 bytes. Based on RFC1048 Time Offset (code 2) is also 4bytes long and IP Address Leas