search for: dwc

...0.usb-2.2/input1 [ 9.898044] tegra-hda 3510000.hda: Adding to iommu group 6 [ 9.963273] input: jetson-tx2-hda HDMI/DP,pcm=3 as /devices/platform/3510000.hda/sound/card0/input6 [ 9.973149] input: jetson-tx2-hda HDMI/DP,pcm=7 as /devices/platform/3510000.hda/sound/card0/input7 [ 10.117602] dwc-eth-dwmac 2490000.ethernet: Adding to iommu group 7 [ 10.124019] dwc-eth-dwmac 2490000.ethernet: no reset control found [ 10.143356] dwc-eth-dwmac 2490000.ethernet: User ID: 0x10, Synopsys ID: 0x41 [ 10.150406] dwc-eth-dwmac 2490000.ethernet: DWMAC4/5 [ 10.155457] dwc-eth-dwmac 2490000.eth...

...with getting the datasets area built. Here is the output form my most recent compile: building package 'datasets' all.R is unchanged ../../../library/datasets/R/datasets is unchanged Error in dyn.load(file, DLLpath = DLLpath, ...) : unable to load shared library '/usr/stat/work/dwc/R/R-2.11.1/library/stats/libs/stats.so': ld.so.1: R: fatal: relocation error: file /usr/stat/work/dwc/R/R-2.11.1/library/stats/libs/stats.so: symbol __i_abs: referenced symbol not found Calls: <Anonymous> ... tryCatch -> tryCatchList -> tryCatchOne -> <Anonymous> Execu...

Hi to all. I'm experimenting with running a https://www.zotac.com/us/product/graphics_card/geforce%C2%AE-gt-710-1gb-pcie-x-1 card on an Nvidia Jetson TX2 arm64 device. Possible? Linux kernel aarch64 5.6.10. Because Nvidia did not list drivers for this architecture, I'm experimenting with a nouveau driver. The Jetson TX2 has a default driver for the host1x framebuffer for output from the

...re.c | 9 +++-- drivers/net/ethernet/hisilicon/hns/hns_dsaf_misc.c | 15 ++++---- drivers/pci/pci-acpi.c | 11 +++--- drivers/pci/pci-label.c | 4 +-- drivers/thermal/int340x_thermal/int3400_thermal.c | 8 ++--- drivers/usb/dwc3/dwc3-pci.c | 6 ++-- drivers/usb/host/xhci-pci.c | 9 +++-- drivers/usb/misc/ucsi.c | 2 +- drivers/usb/typec/typec_wcove.c | 4 +-- include/acpi/acpi_bus.h | 9 ++--- includ...

...lan to implement ARC target for lld[1]? it is a good testcase: flash them directly to the chip[2], or simulator[3]. 1. ARC target for lld https://github.com/llvm-mirror/lld/blob/master/ELF/Arch/ARC.cpp 2. ARC platforms https://embarc.org/platforms.html 3. https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain#using-nsim-simulator-to-run-bare-metal-arc-applications -- Regards, Leslie Zhai - https://reviews.llvm.org/p/xiangzhai/

...9 +++-- > drivers/net/ethernet/hisilicon/hns/hns_dsaf_misc.c | 15 ++++---- > drivers/pci/pci-acpi.c | 11 +++--- > drivers/pci/pci-label.c | 4 +-- > drivers/thermal/int340x_thermal/int3400_thermal.c | 8 ++--- > drivers/usb/dwc3/dwc3-pci.c | 6 ++-- > drivers/usb/host/xhci-pci.c | 9 +++-- > drivers/usb/misc/ucsi.c | 2 +- > drivers/usb/typec/typec_wcove.c | 4 +-- > include/acpi/acpi_bus.h...

...er Smith 写道: >>>> >>>> Hello Leslie, >>>> >>>> I think we are going to need to know a bit more about the ELF ABI for >>>> what looks like the ArcCompact before we can help you. >>> >>> https://github.com/foss-for-synopsys-dwc-arc-processors/arc-ABI-manual >>> >>> But I prefer to read bfd linker's source code about ARC instead: >>> 1. Specific e_flags >>> >>> https://github.com/foss-for-synopsys-dwc-arc-processors/binutils-gdb/blob/arc-2017.09/include/elf/arc.h >>&g...

Thanks to Thierry for finding this - applying index e14643615698..00eeaaffeae5 100644 --- a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c @@ -2369,7 +2369,7 @@ nv13b_chipset = { .imem = gk20a_instmem_new, .ltc = gp100_ltc_new, .mc = gp10b_mc_new, - .mmu = gf100_mmu_new, + .mmu = gp10b_mmu_new,

...t;> Hello Leslie, >>>>>> >>>>>> I think we are going to need to know a bit more about the ELF ABI for >>>>>> what looks like the ArcCompact before we can help you. >>>>> >>>>> https://github.com/foss-for-synopsys-dwc-arc-processors/arc-ABI-manual >>>>> >>>>> But I prefer to read bfd linker's source code about ARC instead: >>>>> 1. Specific e_flags >>>>> >>>>> >>>>> https://github.com/foss-for-synopsys-dwc-arc-processo...

...rivers/ntb/hw/ > amd epf idt intel mscc > > And similarly for the PCIe RC<->EP communication, this adds a generic endpoint > function driver and hence any SoC that supports configurable PCIe endpoint can > use virtio-vhost communication > > # ls drivers/pci/controller/dwc/*ep* > drivers/pci/controller/dwc/pcie-designware-ep.c > drivers/pci/controller/dwc/pcie-uniphier-ep.c > drivers/pci/controller/dwc/pci-layerscape-ep.c Thanks for those backgrounds. > >> >>> ? So there is no guest or host as in >>> virtualization but two ent...

...gt;>> >>> And similarly for the PCIe RC<->EP communication, this adds a generic endpoint >>> function driver and hence any SoC that supports configurable PCIe endpoint can >>> use virtio-vhost communication >>> >>> # ls drivers/pci/controller/dwc/*ep* >>> drivers/pci/controller/dwc/pcie-designware-ep.c >>> drivers/pci/controller/dwc/pcie-uniphier-ep.c >>> drivers/pci/controller/dwc/pci-layerscape-ep.c >> >> Thanks for those backgrounds. >> >> >>>>> ?? So there is no guest or...

...>>>>>>> function driver and hence any SoC that supports configurable >>>>>>>> PCIe endpoint can >>>>>>>> use virtio-vhost communication >>>>>>>> >>>>>>>> # ls drivers/pci/controller/dwc/*ep* >>>>>>>> drivers/pci/controller/dwc/pcie-designware-ep.c >>>>>>>> drivers/pci/controller/dwc/pcie-uniphier-ep.c >>>>>>>> drivers/pci/controller/dwc/pci-layerscape-ep.c >>>>>>> Thanks for those backgrou...

...ilarly for the PCIe RC<->EP communication, this adds a generic endpoint >>>>> function driver and hence any SoC that supports configurable PCIe endpoint can >>>>> use virtio-vhost communication >>>>> >>>>> # ls drivers/pci/controller/dwc/*ep* >>>>> drivers/pci/controller/dwc/pcie-designware-ep.c >>>>> drivers/pci/controller/dwc/pcie-uniphier-ep.c >>>>> drivers/pci/controller/dwc/pci-layerscape-ep.c >>>> Thanks for those backgrounds. >>>> >>>> >>&...

...lo.o -mmcu=XXX Basically yes, but we have not implemented the integrated assembler yet, so currently rely on an external ARC gnu toolchain. Plus, there are a wide variety of subtargets that are basically unsupported until we start adding configuration support. https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain >and do you plan to implement ARC target for lld[1]? it is a good >testcase: flash them directly to the chip[2], or simulator[3]. Supporting ARC in lld is a good question. It has not been on my personal short-list, but if you (or others) are interested in specific...

On Thu, Jul 02, 2020 at 01:51:21PM +0530, Kishon Vijay Abraham I wrote: > This series enhances Linux Vhost support to enable SoC-to-SoC > communication over MMIO. This series enables rpmsg communication between > two SoCs using both PCIe RC<->EP and HOST1-NTB-HOST2 > > 1) Modify vhost to use standard Linux driver model > 2) Add support in vring to access virtqueue over

On Thu, Jul 02, 2020 at 01:51:21PM +0530, Kishon Vijay Abraham I wrote: > This series enhances Linux Vhost support to enable SoC-to-SoC > communication over MMIO. This series enables rpmsg communication between > two SoCs using both PCIe RC<->EP and HOST1-NTB-HOST2 > > 1) Modify vhost to use standard Linux driver model > 2) Add support in vring to access virtqueue over

...>> function driver and hence any SoC that supports configurable > >>>>>>>> PCIe endpoint can > >>>>>>>> use virtio-vhost communication > >>>>>>>> > >>>>>>>> # ls drivers/pci/controller/dwc/*ep* > >>>>>>>> drivers/pci/controller/dwc/pcie-designware-ep.c > >>>>>>>> drivers/pci/controller/dwc/pcie-uniphier-ep.c > >>>>>>>> drivers/pci/controller/dwc/pci-layerscape-ep.c > >>>>>>> Tha...

...t control net: dsa: mt7530: explicitly request exclusive reset control net: ethernet: hisi_femac: explicitly request exclusive reset control net: ethernet: hix5hd2_gmac: explicitly request exclusive reset control net: stmmac: explicitly request exclusive reset control net: stmmac: dwc-qos: explicitly request exclusive reset control ath10k: explicitly request exclusive reset control nvmem: lpc18xx-eeprom: explicitly request exclusive reset control PCI: dwc: pcie-qcom: explicitly request exclusive reset control PCI: imx6: explicitly request exclusive reset control PCI: t...

...time, Xorg is actually starting... [ 16.862744] WARNING: CPU: 3 PID: 381 at drivers/gpu/drm/nouveau/nouveau_bo.c:280 nouveau_bo_new+0x450/0x4d0 [nouveau] [ 16.873333] Modules linked in: nouveau i2c_algo_bit ttm tegra_drm gpio_keys drm_kms_helper drm drm_panel_orientation_quirks(P) host1x dwmac_dwc_qos_eth stmmac_platform stmmac ptp pps_core syscopyarea sysfillrect sysimgblt fb_sys_fops [ 16.894001] CPU: 3 PID: 381 Comm: Xorg Tainted: P S 4.15.0-rc3-next-20171214-ARCH-AEDEN+ #3 [ 16.903546] Hardware name: NVIDIA Tegra186 P2771-0000 Development Board (DT) [ 16.910578] pstate: 60000005 (n...

...mt7530: explicitly request exclusive reset control > net: ethernet: hisi_femac: explicitly request exclusive reset control > net: ethernet: hix5hd2_gmac: explicitly request exclusive reset > control > net: stmmac: explicitly request exclusive reset control > net: stmmac: dwc-qos: explicitly request exclusive reset control > ath10k: explicitly request exclusive reset control > nvmem: lpc18xx-eeprom: explicitly request exclusive reset control > PCI: dwc: pcie-qcom: explicitly request exclusive reset control > PCI: imx6: explicitly request exclusive re...