Hi all,
The attached patch teaches the NFS client to respect the 2^32 - 1 B
NFSv2 file size limit.
Without this patch accesses to offsets at or above 4 GiB would silently
be remapped to the mod 4 2^32 location.
--
Nick Withers
Embedded Systems Programmer
Department of Nuclear Physics, Research
Hello Qiao Yang,
On Monday 03 of August 2015 22:06:31 QIAO YANG wrote:
> On Aug 03, 2015, at 08:34 AM, QIAO YANG wrote:
> > On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
> >> On 29/07/2015 8:04 pm, Sebastian Huber wrote:
> >>> A custom workspace initialization can be done via
> >>> bsp_work_a
On Aug 03, 2015, at 08:34 AM, QIAO YANG wrote:
On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
On 29/07/2015 8:04 pm, Sebastian Huber wrote:
A custom workspace initialization can be done via
bsp_work_area_initialize().
On the zynq the ethernet driver from Ric (SLAC) for the in tree
(
On Jul 29, 2015, at 07:56 AM, Pavel Pisa wrote:
Hello Qiao Yang,
On Tuesday 28 of July 2015 01:35:45 Pavel Pisa wrote:
Hello Qiao Yang,
On Friday 24 of July 2015 18:04:47 QIAO YANG wrote:
> Some updates for you. I've found out that my previous problem with
> cmdline due to my minicom didn't
On Jul 29, 2015, at 02:03 PM, Chris Johns wrote:
On 29/07/2015 8:04 pm, Sebastian Huber wrote:
A custom workspace initialization can be done via
bsp_work_area_initialize().
On the zynq the ethernet driver from Ric (SLAC) for the in tree
(existing) IP stack there is:
uint8_t* start;
size_t
