Home
last modified time | relevance | path

Searched hist:"683 b09d7837a71fb4c5dd53919c6afa4d800e60e" (Results 1 – 6 of 6) sorted by relevance

/rk3399_rockchip-uboot/board/coreboot/coreboot/
H A DKconfig683b09d7837a71fb4c5dd53919c6afa4d800e60e Wed Jun 03 01:20:04 UTC 2015 Bin Meng <bmeng.cn@gmail.com> x86: qemu: Create separate i440fx and q35 device trees

Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
/rk3399_rockchip-uboot/arch/x86/dts/
H A Dqemu-x86_i440fx.dts683b09d7837a71fb4c5dd53919c6afa4d800e60e Wed Jun 03 01:20:04 UTC 2015 Bin Meng <bmeng.cn@gmail.com> x86: qemu: Create separate i440fx and q35 device trees

Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
H A Dqemu-x86_q35.dts683b09d7837a71fb4c5dd53919c6afa4d800e60e Wed Jun 03 01:20:04 UTC 2015 Bin Meng <bmeng.cn@gmail.com> x86: qemu: Create separate i440fx and q35 device trees

Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
H A DMakefile683b09d7837a71fb4c5dd53919c6afa4d800e60e Wed Jun 03 01:20:04 UTC 2015 Bin Meng <bmeng.cn@gmail.com> x86: qemu: Create separate i440fx and q35 device trees

Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
/rk3399_rockchip-uboot/configs/
H A Dqemu-x86_defconfig683b09d7837a71fb4c5dd53919c6afa4d800e60e Wed Jun 03 01:20:04 UTC 2015 Bin Meng <bmeng.cn@gmail.com> x86: qemu: Create separate i440fx and q35 device trees

Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
/rk3399_rockchip-uboot/doc/
H A DREADME.x86683b09d7837a71fb4c5dd53919c6afa4d800e60e Wed Jun 03 01:20:04 UTC 2015 Bin Meng <bmeng.cn@gmail.com> x86: qemu: Create separate i440fx and q35 device trees

Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>