Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

regarding arm-coreboot-veyron #1

Open
hanetzer opened this issue Jan 18, 2018 · 2 comments
Open

regarding arm-coreboot-veyron #1

hanetzer opened this issue Jan 18, 2018 · 2 comments

Comments

@hanetzer
Copy link

I realize this isn't the sort of repo one opens issues on normally, since the main dev
goes on at savanna's repo, but since you're the dude doing the port I've been trying
to get ahold of you.

Is the code at http://git.savannah.gnu.org/cgit/grub.git, either master, arm_coreboot,
or phcoder/arm currently ready to be able to 'work' on veyron chromebooks? I've
managed to generate a grub payload for coreboot, and it works up to the grub> prompt,
but I can't do keyboard input (usb or cros_keyboard) and manually inserted ls
only show (cbfsroot) or the like.

I just want to know if I'm chasing a wild goose here or not. And if it is ready for 'normal'
use, could you assist me in getting a payload that works put together?

@hanetzer
Copy link
Author

for the record, debugging via commands placed in the embedded grub.cfg
shows that the default output terminal is gfxterm, and the input term is
cros_keyboard, so it must not be working quite right.

@hntrdglss
Copy link

hntrdglss commented Sep 24, 2019

Hey @hanetzer! I have found myself in a similar situation and wonder if you were able to make any progress.

I built Coreboot and GRUB, and successfully flashed them onto my veyron-fievel device, a Chromebox-style variant. Since, as a Chromebox, it lacks an integrated keyboard, I removed this line, which inits the cros_keyboard, to prevent any trouble down the road. (I also removed the subsequent line, grub_pl050_init(), because I don't have a PS/2 device attached. From my research, I think this must have been included for the arm-coreboot-vexpress compilation.)

I generated the ELF by adding this to Makefile.am:

if COND_arm_coreboot
FS_PAYLOAD_MODULES ?= $(shell cat grub-core/fs.lst)
default_payload.elf: grub-mkstandalone grub-mkimage FORCE
	test -f $@ && rm $@ || true
	pkgdatadir=. ./grub-mkstandalone --grub-mkimage=./grub-mkimage -O arm-coreboot-veyron -o $@ --modules='ehci usb_keyboard usbms part_msdos ext2 fat part_gpt usbserial_usbdebug cbfs' --install-modules='ls linux search configfile normal memrw minicmd lsmmap halt reboot hexdump regexp test serial gzio echo help syslinuxcfg $(FS_PAYLOAD_MODULES) password_pbkdf2 $(EXTRA_PAYLOAD_MODULES)' --fonts= --themes= --locales= --dtb=fievel.dtb -d grub-core /boot/grub/grub.cfg=$(srcdir)/coreboot.cfg
endif

I also added to the top of my coreboot.cfg:

insmod ehci
insmod usb_keyboard
terminal_input usb_keyboard

I'm able to get to a grub> prompt, but unfortunately no keyboard I have tried is able to input anything. Any words of wisdom you have to pass along would be greatly appreciated! (Or perhaps @phcoder, if you happen to be checking this repository these days. Thanks for your work to make this happen!)

phcoder pushed a commit that referenced this issue Aug 14, 2023
Currently bootstrap complains in the following way when
patching gnulib files:

  patching file argp-help.c
  Hunk #1 succeeded at 52 (offset 1 line).
  Hunk #2 succeeded at 1548 (offset 115 lines).
  patching file mbswidth.c
  patching file mbswidth.h
  Hunk #1 succeeded at 40 (offset -5 lines).

Let's fix it by amending line numbers in the patch.

Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
Reviewed-by: Alec Brown <alec.r.brown@oracle.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants