Hi Experts,
The trick for changing from CONFIG_USB to CONFIG_USB_DISK did help to
compile but it doesn't seem to be correct fix and not helping at run time.
I have configured libpayload with CONFIG_USB support but that define is not
included in the filo/build/config.h. As a result I get debug
Hello Vipin,
Can you please suggest a solution and let me know why CONFIG_USB is removed
from my .config
The prefix for libpayload's configurations options changed to CONFIG_LP_,
lately. The last commit for FILO (60d45fc) tried to fix it, but seems to
have missed some options. So CONFIG_USB is
Hi Nico,
Thanks for the details. I somehow managed to build filo by defining
CONFIG_USB in build/config.h However having problems at run time. Logs are
below. Can you please suggest last known commit where USB was working good?
Currently it seems to be messed up. I have to boot Linux from USB
you can try to get filo to work, or you can work at John Lewis
excellent work on JELTKA and see if you would be better off using a
linux kernel instead.
My bias is towards JELTKA, personally.
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Hi Ron,
We have to reduce the boot time to minimum possible; hence the preference
is FILO/GRUB2.
Not sure the status of USB stuff in GRUB2 so trying hard to get FILO to
work.
On Sun, Oct 12, 2014 at 10:12 PM, ron minnich rminn...@gmail.com wrote:
you can try to get filo to work, or you can
On 12.10.2014 18:21, Vipin Gahlaut wrote:
Logs for the problem I am getting repeatedly at run time
change on port 1
fullspeed device
first get_descriptor(DT_DEV) failed
set_address failed
That's exactly what I observed on a kontron/986lcd-m (i945) with low-
speed devices connected to the
No. I am using qemu (version 2.1.2) with -usbdevice option. I run qemu with
following command
qemu-system-i386 -bios ./coreboot.rom -hda hda.img -usbdevice disk:usb.img
-nographic
On Sun, Oct 12, 2014 at 11:31 PM, Nico Huber nic...@gmx.de wrote:
On 12.10.2014 18:21, Vipin Gahlaut wrote:
Logs
reduce the boot time to the minimum possible -- what's that mean. Do
you have a number?
ARMs boot linux to usability in 800 ms. (number seen at FOSDEM in
2007). Is that fast enough?
SPI greatly increases time to boot, and the use of SPI may be more
important than the boot loader used.
Finally,
Here is the patch I used to fix build error.
diff --git a/drivers/usb.c b/drivers/usb.c
index 0da6efa..a959389 100644
--- a/drivers/usb.c
+++ b/drivers/usb.c
@@ -20,7 +20,7 @@
#include libpayload-config.h
/* Only use this code if libpayload is compiled with USB stack */
-#ifdef CONFIG_USB
9 matches
Mail list logo
