♟ br

Enable ARM PL330 DMA engine and Cadence Quad SPI flash controller on

Add driver for Cadence Quad SPI Flash Controller found on

In D15089#318912, @kib wrote:

Ok.

Where is the dereference of the vm object reference owned by the OSD ?

release object reference obtained by osd(9)

don't take additional reference to object. We already taking one in pmc_mmap_single()

reference the object
use destroy_dev, not destroy_dev_sched

Use:

osd(9)
CPU_FOREACH macro
make_dev_s instead of make_dev
mtx_lock around map->obj dereferencing

check return value for pmc_vm_initialize(md);

Set correct float abi (float abi double) for hard-float build, so

In D10039#318482, @brooks wrote:

@br is this change sensible or should I abandon it?

In D14353#306252, @jhb wrote:

Hmmm. This is kind of related to my desire to start inlining atomics on x86, etc. I think I want a new macro to help us distinguish building a "generic" module vs a module tied to a kernel. Simply not defining KLD_MODULE when building modules tied to a kernel doesn't work (I've tried), and I haven't yet decided how I wanted to proceed after that failed. I think I a new macro for the case of a generic module is probably more useful as most places will want to check that instead of KLD_MODULE that wish to differentiate the two. I'd like to see what @kib thinks about maybe adding a new macro for "generic" modules and using that to fix this instead.

Import Intel Processor Trace library.

add qspi flash driver

Convert atse(4) driver for Altera Triple-Speed Ethernet MegaCore to use

Add beripic1, msgdma and softdma instances.

Add driver for Altera SoftDMA® device.

Add driver for Altera modular Scatter-Gather DMA engine (mSGDMA).

Add driver for ARM PrimeCell PL330 DMA engine.

Don't include sys/bus_dma.h directly, use machine/bus.h instead.

Add SMP support for BERI CPU.

Tune xDMA interface slightly:

Add ld emulation types for hard-float mipses.

In D14353#306252, @jhb wrote:

Hmmm. This is kind of related to my desire to start inlining atomics on x86, etc. I think I want a new macro to help us distinguish building a "generic" module vs a module tied to a kernel. Simply not defining KLD_MODULE when building modules tied to a kernel doesn't work (I've tried), and I haven't yet decided how I wanted to proceed after that failed. I think I a new macro for the case of a generic module is probably more useful as most places will want to check that instead of KLD_MODULE that wish to differentiate the two. I'd like to see what @kib thinks about maybe adding a new macro for "generic" modules and using that to fix this instead.

Enable Qualcomm Debug Subsystem (QDSS) block on MSM8916 SoC.

Add support for the Coresight technology from ARM Ltd.

Regenerate patch (opencsd committed to HEAD)

Add new shared library -- libopencsd.

Import OpenCSD -- an ARM CoreSight(tm) Trace Decode Library.

Tag OpenCSD revision.

Import OpenCSD -- an ARM CoreSight Trace Decode library.

br (Ruslan Bukin)
User

Projects

User Details

Recent Activity
View All

Fri, May 25

Tue, May 15

Tue, May 1

Apr 23 2018

Apr 20 2018

Apr 19 2018

Apr 18 2018

Apr 17 2018

Apr 16 2018

Apr 13 2018

Apr 12 2018

Apr 10 2018

Apr 6 2018

Apr 5 2018

Apr 4 2018

br (Ruslan Bukin)User