The syscall ABI includes the gcc functional calling ABI since a syscall
implies userland caller and kernel callee.
The current gcc ABI (v3) for ARCv2 ISA required 64-bit data be passed in
even-odd register pairs, (potentially punching reg holes when passing such
values as args). This was partly
Hi Arnd,
On 08/15/2016 09:28 PM, Alexey Brodkin wrote:
> As it was discussed quite some time ago (see
> https://lkml.org/lkml/2015/11/5/862) it's a good practice to add
> "model" property in .dts. Moreover as per ePAPR "model" property is
> required and should look like "manufacturer,model" so we
This test uses OFD locks which are supported only by 64-bit ABI.
Thus OFD locks must be used with flock64 structure for sure in this
test. It is necessary because on some 32-bit targets (e.g. 32-bit
uClibc) flock is not mapped to flock64 when _FILE_OFFSET_BITS is not
set to 64.
Signed-off-by:
On Tue, 2016-08-16 at 11:32 +, Eugeniy Paltsev wrote:
> On Mon, 2016-08-15 at 15:41 +0300, Andy Shevchenko wrote:
> > On Mon, 2016-08-15 at 11:10 +, Eugeniy Paltsev wrote:
> > Consider to review
> > http://www.spinics.net/lists/dmaengine/msg10682.html
> Looks good to me.
> Reviewed-by:
On Mon, 2016-08-15 at 15:41 +0300, Andy Shevchenko wrote:
> On Mon, 2016-08-15 at 11:10 +, Eugeniy Paltsev wrote:
> >
> > On Fri, 2016-08-12 at 17:08 +0300, Andy Shevchenko wrote:
> > >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > "nollp" parameter defines if DW DMAC channel supports
DW DMAC on ARC SDP became broken after df5c7386 ("dmaengine: dw: some Intel
devices has no memcpy support") and 30cb2639 ("dmaengine: dw: don't override
platform data with autocfg") commits.
* After df5c7386 commit "DMA_MEMCPY" capability option doesn't get set
correctly in platform driver
