rt on
> the baytrail part. */
> };
> pci {
> #address-cells = <3>;
> #size-cells = <2>;
> compatible = "simple-bus"; /* I had to change this from intel,cpi to
> simple-bus in order for 'dm tree' to show this node and the hsuart0 node/ *
Hi Tim,
On Wed, Oct 7, 2015 at 11:26 PM, Timothy Scott wrote:
> Bin,
>
> Thanks for the response. I've got things working with v2015.04, but it took
> some tweaking. Here's what I learned:
>
> 1) PCI is initialized AFTER the code was attempting to configure hsuart0.
>
t_console = <0>;
> > };
> >
> > chosen {
> > stdout-path = "/serial"; /* switching this to results in
> > continuous resets. Configuration as-is works fine but uses the PCU uart
> on
> > the baytrail part. */
> > };
> > pci {
> &g
/Articles/645455/
https://github.com/bonzini/qboot
q-boot is able to give a minimal booting time, with the help of
fw_cfg, by reading both the kernel and initrd image
from fw_cfg.
I guess ACPI support for both q-boot and qemu-x86 in u-boot can be
implemented on similar lines.
ACPI support
q-boot is able to give a minimal booting time, with the help of
fw_cfg, by reading both the kernel and initrd image
from fw_cfg.
I guess ACPI support for both q-boot and qemu-x86 in u-boot can be
implemented on similar lines.
Regards,
Saket Sinha
___
U
firmware for QEMU.
http://lwn.net/Articles/645455/
https://github.com/bonzini/qboot
q-boot is able to give a minimal booting time, with the help of
fw_cfg, by reading both the kernel and initrd image
from fw_cfg.
I guess ACPI support for both q-boot and qemu-x86 in u-boot can be
implemented
release, isn't it?
3. make # second make fails with message:
make[1]: Entering directory `/home/hua/git/u-boot/arch/x86/lib'
make[1]: *** No rule to make target `.depend', needed by `built-in.o'.
Stop.
make[1]: Leaving directory `/home/hua/git/u-boot/arch/x86/lib'
Strange again
toolchain
2. make coreboot-x86 # sucess for the first time
3. make # second make fails with message:
make[1]: Entering directory `/home/hua/git/u-boot/arch/x86/lib'
make[1]: *** No rule to make target `.depend', needed by `built-in.o'. Stop.
make[1]: Leaving directory `/home/hua/git/u-boot/arch/x86
-x86_config all instead.
3. make # second make fails with message:
make[1]: Entering directory `/home/hua/git/u-boot/arch/x86/lib'
make[1]: *** No rule to make target `.depend', needed by `built-in.o'. Stop.
make[1]: Leaving directory `/home/hua/git/u-boot/arch/x86/lib'
Strange again.
.depend
/hua/git/u-boot/arch/x86/lib'
make[1]: *** No rule to make target `.depend', needed by `built-in.o'. Stop.
make[1]: Leaving directory `/home/hua/git/u-boot/arch/x86/lib'
Strange again.
.depend files are not used any more.
(They were used in the old build system prior to Kbuild.)
Are you sure
:56:25 +1000
Subject: Re: u-boot for x86
From: graeme.r...@gmail.com
To: r_boulw...@hotmail.com
CC: u-boot@lists.denx.de
Hi Raleigh,
On Wed, Jun 22, 2011 at 12:44 PM, Raleigh Boulware
r_boulw...@hotmail.com wrote:
I am looking at the source code for the sc520 and can not figure out
which
Hi Raleigh,
On Wed, Jun 22, 2011 at 12:44 PM, Raleigh Boulware
r_boulw...@hotmail.com wrote:
I am looking at the source code for the sc520 and can not figure out which
board directory to look in. Which of the board plat form has the sc520?
The only board which currently builds for the sc520 is
Hi Rodulf,
On 04/05/11 22:37, Rudolf Marek wrote:
Hello all,
[snip]
- The build warnings and errors you incurred are probably fixed in
mainline (x86 is a bit of a forgotten cousin which gets broken when global
patches are made to Makefile, linker scripts etc). If you still have
Hello,
I was asked to post it here too.
I would like to announce that I was able to boot Linux using u-boot on AMD64
motherboard Asrock 939A785G. The development was done on QEMU.
How does it work?
Coreboot does the complete HW init including memory setup PCI etc. When
finishes
it loads
On 04/05/11 18:54, Rudolf Marek wrote:
Hello,
I was asked to post it here too.
I would like to announce that I was able to boot Linux using u-boot on AMD64
motherboard Asrock 939A785G. The development was done on QEMU.
Excellent - U-Boot on a new x86 board
How does it work
Hello all,
Excellent - U-Boot on a new x86 board
Yes and in general any supported coreboot board.
This is one of the ways I was thinking of getting U-Boot running on
mainstream PC boards. The other is to create U-Boot as a GRUB payload.
Either way, it's all about getting the SDRAM
Zvi wrote...
On my next project, the target is Core2Duo (AMPRO's COM840).
Is it a wise decision to use u-boot on this target ?
Probably not!
Ampro will already have invested a lot of time and effort in porting the
BIOS to that board and are giving you a device that works out of the box.
Hello,
I'm using u-boot on PPC405 (ML405) for about 3 years.
It is a great boot loader !
On my next project, the target is Core2Duo (AMPRO's COM840).
Is it a wise decision to use u-boot on this target ?
I prefare u-boot over grub or vxworks bootloader because it has many
features.
If I
On 19/02/11 11:04, Zvi Vered wrote:
Hello,
I'm using u-boot on PPC405 (ML405) for about 3 years.
It is a great boot loader !
On my next project, the target is Core2Duo (AMPRO's COM840).
Is it a wise decision to use u-boot on this target ?
I've had a quick look at the board on the
19 matches
Mail list logo