Displaying 6 results from an estimated 6 matches for "conmfiguration".
Did you mean:
configuration
2020 Mar 02
3
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...n isn't elegant nor foolproof, but is the best we can do at
> the moment and works with existing virtio-iommu implementations. It also
> enables an IOMMU for lightweight hypervisors that do not rely on
> firmware methods for booting.
I appreciate the enablement on x86, but putting the conmfiguration into
mmio-space isn't really something I want to see upstream. What is the
problem with defining an ACPI table instead? This would also make things
work on AARCH64 UEFI machines.
Regards,
Joerg
2020 Mar 02
3
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...n isn't elegant nor foolproof, but is the best we can do at
> the moment and works with existing virtio-iommu implementations. It also
> enables an IOMMU for lightweight hypervisors that do not rely on
> firmware methods for booting.
I appreciate the enablement on x86, but putting the conmfiguration into
mmio-space isn't really something I want to see upstream. What is the
problem with defining an ACPI table instead? This would also make things
work on AARCH64 UEFI machines.
Regards,
Joerg
2012 Jun 27
1
[LLVMdev] How to make a cross compiler for xilinx microblaze
conmfigure does not accept mblaze nor mblaze-elf as target.
checking target system type... Invalid configuration `mblaze': machine
`mblaze' not recognized
configure: error: /bin/bash ../../spare/llvm/autoconf/config.sub mblaze
failed
However with microblaze it proceeds fine. But when i try to use clang i get:
clang: error: 'microblaze-unknown-none': unable to pass LLVM bit-code
2012 Jun 26
0
[LLVMdev] How to make a cross compiler for xilinx microblaze
Hi Fivos,
LLVM refers to the target as "mblaze" for -target.
-Jim
On Jun 26, 2012, at 8:42 AM, Fivos <fivosz at gmail.com> wrote:
> Hello,
>
> i am trying to create a LLVM stack to cross compile c code targeting the
> xilinx microblaze.
>
> I built LLVM configured with target=microblaze however cland doesn't
> like it. When i try to emit llvm code
2020 Mar 03
0
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...r foolproof, but is the best we can do at
>> the moment and works with existing virtio-iommu implementations. It also
>> enables an IOMMU for lightweight hypervisors that do not rely on
>> firmware methods for booting.
>
> I appreciate the enablement on x86, but putting the conmfiguration into
> mmio-space isn't really something I want to see upstream. What is the
> problem with defining an ACPI table instead? This would also make things
> work on AARCH64 UEFI machines.
Michael has pushed this solution (putting the "configuration in the PCI
config space"), I t...
2012 Jun 26
3
[LLVMdev] How to make a cross compiler for xilinx microblaze
Hello,
i am trying to create a LLVM stack to cross compile c code targeting the
xilinx microblaze.
I built LLVM configured with target=microblaze however cland doesn't
like it. When i try to emit llvm code i get the following
error: unknown target triple 'microblaze-unknown-none', please use
-triple or -arch
How should i configure my LLVM stack and then how should i run the tools