Minnowboard:IssueTracker

Linux Kernel Issues

 * none listed currently

Yocto Project BSP Issues

 * 1) No way to resume from suspend
 * 2) * Priority: HIGH
 * 3) * Status: ACCEPTED
 * 4) * Reporter: dvhart
 * 5) * It isn't clear yet how this should work. There are only a few wake lines available on the board. I'm not sure if the PWR or RST buttons should cause a wake. Something to try is WOL, USB wake, and the E6XX resume well GPIOs SUS[...].
 * 6) Audio mixer controls are inconsistent
 * 7) * Priority: MEDIUM
 * 8) * Status: ACCEPTED
 * 9) * Reporter: dvhart
 * 10) * On one boot alsamixer reports Headphones and Front, on subsequent boots things like Master, PCM, the digital switches and more appear. I suspect something is still not quite right with the VERB presented from firmware, but more investigation is required.

Angstrom Image Issues

 * none listed currently

MinnowBoard X3 Issues

 * none listed currently

Testing Lure Issues

 * none listed currently

Training Lure Issues

 * none listed currently

UEFI Firmware Issues

 * 1) Add PCI SIDs to all PCI devices
 * 2) * Priority: CRITICAL
 * 3) * Status: New
 * 4) * Reporter: dvhart
 * 5) * dvhart: To properly identify the PCI devices as being on the MinnowBoard, we need to specify this in the PCI Subsystem IDs (SVID,SID). We are working on getting the IDs acquired, but we can use temporary ones for developing the drivers while we wait for the IDs to materialize.
 * 6) Firmware must detect SATA and MMC by default and enable EFIfb
 * 7) * Priority: CRITICAL
 * 8) * Status: NEW
 * 9) * Reporter: koen
 * 10) * dvhart: From past experience, this should work like this: On first boot the firmware scans SATA, MMC, and USB (in that order) and automatically boot the standard EFI payload (EFI/BOOT/BOOTIA32.EFI). I think that path changes in the spec for fixed media like SSDs. On the subsequent boot, it will attempt to boot only that path. If that fails, I believe it drops to the shell, you run the commands to get your payload ready, then "exit", select from the options to boot, and that choice should be selected on the next boot. Lee please comment.
 * 11) mPCIe not visible from OS
 * 12) * Priority: CRITICAL
 * 13) * Status: NEW
 * 14) * Reporter: danders
 * 15) GOP driver needs to set GPIO state appropriately based on LVDS_PRESENT signal
 * 16) * Priority: CRITICAL
 * 17) * Status: ACCEPTED
 * 18) * Reporter: dvhart
 * 19) Add EFI VAR for EG20TEthernetAddr0
 * 20) * Priority: HIGH
 * 21) * Status: ACCEPTED
 * 22) * Reporter: dvhart
 * 23) Random? Boot failures. One ends in “PROGRESS CODE: V2020004 I0” over serial
 * 24) * Priority: MEDIUM
 * 25) * Status: NEEDINFO
 * 26) * Reporter: dvhart
 * 27) * Lee unable to reproduce
 * 28) Board doesn't boot after poweroff, must cut/restore power
 * 29) * Priority: MEDIUM
 * 30) * Status: NEW
 * 31) * Reporter: dvhart
 * 32) Ensure the intel-hda pci device config data is populated, as well as the VERB table
 * 33) * Priority: MEDIUM
 * 34) * Status: NEEDINFO
 * 35) * Reporter: dvhart
 * 36) * Audio device now works with MSI disabled. Need information from OS to determine why MSIs are being enabled.
 * 37) Verify we are using ACPI 5.0, boot messages only confirm ACPI 2.0
 * 38) * Priority: MEDIUM
 * 39) * Status: NEEDINFO
 * 40) * Reporter: dvhart
 * 41) * How do we tell which version of AML is passed to the OS?
 * 42) USB keyboard prevents serial console from receiving input (no hub in use)
 * 43) * Priority: MEDIUM
 * 44) * Status: ACCEPTED
 * 45) * Reporter: dvhart
 * 46) * General USB 1.0 issues are known and being worked.
 * 47) I/O space for WDT uninitialized (can't use the E6xx watchdog)
 * 48) * Priority: LOW
 * 49) * Status: ACCEPTED
 * 50) * Reporter: dvhart
 * 51) Linux boot message: Firmware Bug: ACPI: BIOS _OSI(Linux) query ignored
 * 52) * Priority: LOW
 * 53) * Status: ACCEPTED
 * 54) * Reporter: dvhart
 * 55) Add SSDT describing the GPIO present on the board (pending input from ACPI teams)
 * 56) * Priority: LOW
 * 57) * Status: NEEDINFO
 * 58) * Reporter: dvhart
 * 59) * Not going to happen before release. Maybe not at all. The existing drivers don't work this way and duplicating them for Minnow doesn't really make sense.
 * 60) USB keyboard not detected on reboot from Angstrom image
 * 61) * Priority: Medium
 * 62) * Status: NEW
 * 63) * Reporter: dvhart
 * 64) * When rebooting from Angstrom ($ reboot) if there is no autoboot target setup, the firmware will drop to the shell, but the USB keyboard isn't detected. Using the serial console works and the keyboard and mouse both work once booted back up into Angstrom.

RESOLVED

 * 1) Set DMI_BOARD_NAME to “MinnowBoard” per our previous SMBIOS discussion
 * 2) * Priority: HIGH
 * 3) * Status: RESOLVED
 * 4) * Reporter: dvhart
 * 5) * VENDOR strings will be "Circuitco"
 * 6) * Completed, pending next firmware release
 * 7) Zero 0x0-0x1000 per compatibility documentation
 * 8) * Priority: CRITICAL
 * 9) * Status: RESOLVED
 * 10) * Reporter: dvhart
 * 11) * Firmware now zeroes the page. Linux now has improved heuristics to detect bogus data.