Difference between revisions of "Minnowboard:IssueTracker"
(Add PCI IDs to Firmware issues.) |
(→UEFI Firmware Issues) |
||
Line 29: | Line 29: | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* 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. | #* 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. | ||
− | |||
# '''Firmware must detect SATA and MMC by default and enable EFIfb''' | # '''Firmware must detect SATA and MMC by default and enable EFIfb''' | ||
#* Priority: CRITICAL | #* Priority: CRITICAL | ||
Line 35: | Line 34: | ||
#* Reporter: koen | #* Reporter: koen | ||
#* 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. | #* 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. | ||
− | |||
# '''mPCIe not visible from OS''' | # '''mPCIe not visible from OS''' | ||
#* Priority: CRITICAL | #* Priority: CRITICAL | ||
#* Status: NEW | #* Status: NEW | ||
#* Reporter: danders | #* Reporter: danders | ||
− | |||
# '''Zero 0x0-0x1000 per compatibility documentation''' | # '''Zero 0x0-0x1000 per compatibility documentation''' | ||
#* Priority: CRITICAL | #* Priority: CRITICAL | ||
Line 46: | Line 43: | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* Firmware now zeroes the page. Linux now has improved heuristics to detect bogus data. | #* Firmware now zeroes the page. Linux now has improved heuristics to detect bogus data. | ||
− | |||
# '''GOP driver needs to set GPIO state appropriately based on LVDS_PRESENT signal''' | # '''GOP driver needs to set GPIO state appropriately based on LVDS_PRESENT signal''' | ||
#* Priority: CRITICAL | #* Priority: CRITICAL | ||
#* Status: ACCEPTED | #* Status: ACCEPTED | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
− | |||
# '''Set DMI_BOARD_NAME to “MinnowBoard” per our previous SMBIOS discussion''' | # '''Set DMI_BOARD_NAME to “MinnowBoard” per our previous SMBIOS discussion''' | ||
#* Priority: HIGH | #* Priority: HIGH | ||
− | #* Status: | + | #* Status: RESOLVED |
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* VENDOR strings will be "Circuitco" | #* VENDOR strings will be "Circuitco" | ||
#* Completed, pending next firmware release | #* Completed, pending next firmware release | ||
− | |||
# '''Random? Boot failures. One ends in “PROGRESS CODE: V2020004 I0” over serial''' | # '''Random? Boot failures. One ends in “PROGRESS CODE: V2020004 I0” over serial''' | ||
#* Priority: MEDIUM | #* Priority: MEDIUM | ||
Line 64: | Line 58: | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* Lee unable to reproduce | #* Lee unable to reproduce | ||
− | |||
# '''Board doesn't boot after poweroff, must cut/restore power''' | # '''Board doesn't boot after poweroff, must cut/restore power''' | ||
#* Priority: MEDIUM | #* Priority: MEDIUM | ||
#* Status: NEW | #* Status: NEW | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
− | |||
# '''Ensure the intel-hda pci device config data is populated, as well as the VERB table''' | # '''Ensure the intel-hda pci device config data is populated, as well as the VERB table''' | ||
#* Priority: MEDIUM | #* Priority: MEDIUM | ||
Line 75: | Line 67: | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* Audio device now works with MSI disabled. Need information from OS to determine why MSIs are being enabled. | #* Audio device now works with MSI disabled. Need information from OS to determine why MSIs are being enabled. | ||
− | |||
# '''Verify we are using ACPI 5.0, boot messages only confirm ACPI 2.0''' | # '''Verify we are using ACPI 5.0, boot messages only confirm ACPI 2.0''' | ||
#* Priority: MEDIUM | #* Priority: MEDIUM | ||
Line 81: | Line 72: | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* How do we tell which version of AML is passed to the OS? | #* How do we tell which version of AML is passed to the OS? | ||
− | |||
# '''USB keyboard prevents serial console from receiving input (no hub in use)''' | # '''USB keyboard prevents serial console from receiving input (no hub in use)''' | ||
#* Priority: MEDIUM | #* Priority: MEDIUM | ||
Line 87: | Line 77: | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
#* General USB 1.0 issues are known and being worked. | #* General USB 1.0 issues are known and being worked. | ||
− | |||
# '''I/O space for WDT uninitialized (can't use the E6xx watchdog)''' | # '''I/O space for WDT uninitialized (can't use the E6xx watchdog)''' | ||
#* Priority: LOW | #* Priority: LOW | ||
#* Status: ACCEPTED | #* Status: ACCEPTED | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
− | |||
# '''Linux boot message: Firmware Bug: ACPI: BIOS _OSI(Linux) query ignored''' | # '''Linux boot message: Firmware Bug: ACPI: BIOS _OSI(Linux) query ignored''' | ||
#* Priority: LOW | #* Priority: LOW | ||
#* Status: ACCEPTED | #* Status: ACCEPTED | ||
#* Reporter: dvhart | #* Reporter: dvhart | ||
− | |||
# '''Add SSDT describing the GPIO present on the board (pending input from ACPI teams)''' | # '''Add SSDT describing the GPIO present on the board (pending input from ACPI teams)''' | ||
#* Priority: LOW | #* Priority: LOW |
Revision as of 09:49, 10 May 2013
Contents
Linux Kernel Issues
- none listed currently
Yocto Project BSP Issues
- none listed currently
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
- Add PCI SIDs to all PCI devices
- Priority: CRITICAL
- Status: New
- Reporter: dvhart
- 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.
- Firmware must detect SATA and MMC by default and enable EFIfb
- Priority: CRITICAL
- Status: NEW
- Reporter: koen
- 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.
- mPCIe not visible from OS
- Priority: CRITICAL
- Status: NEW
- Reporter: danders
- Zero 0x0-0x1000 per compatibility documentation
- Priority: CRITICAL
- Status: RESOLVED
- Reporter: dvhart
- Firmware now zeroes the page. Linux now has improved heuristics to detect bogus data.
- GOP driver needs to set GPIO state appropriately based on LVDS_PRESENT signal
- Priority: CRITICAL
- Status: ACCEPTED
- Reporter: dvhart
- Set DMI_BOARD_NAME to “MinnowBoard” per our previous SMBIOS discussion
- Priority: HIGH
- Status: RESOLVED
- Reporter: dvhart
- VENDOR strings will be "Circuitco"
- Completed, pending next firmware release
- Random? Boot failures. One ends in “PROGRESS CODE: V2020004 I0” over serial
- Priority: MEDIUM
- Status: NEEDINFO
- Reporter: dvhart
- Lee unable to reproduce
- Board doesn't boot after poweroff, must cut/restore power
- Priority: MEDIUM
- Status: NEW
- Reporter: dvhart
- Ensure the intel-hda pci device config data is populated, as well as the VERB table
- Priority: MEDIUM
- Status: NEEDINFO
- Reporter: dvhart
- Audio device now works with MSI disabled. Need information from OS to determine why MSIs are being enabled.
- Verify we are using ACPI 5.0, boot messages only confirm ACPI 2.0
- Priority: MEDIUM
- Status: NEEDINFO
- Reporter: dvhart
- How do we tell which version of AML is passed to the OS?
- USB keyboard prevents serial console from receiving input (no hub in use)
- Priority: MEDIUM
- Status: ACCEPTED
- Reporter: dvhart
- General USB 1.0 issues are known and being worked.
- I/O space for WDT uninitialized (can't use the E6xx watchdog)
- Priority: LOW
- Status: ACCEPTED
- Reporter: dvhart
- Linux boot message: Firmware Bug: ACPI: BIOS _OSI(Linux) query ignored
- Priority: LOW
- Status: ACCEPTED
- Reporter: dvhart
- Add SSDT describing the GPIO present on the board (pending input from ACPI teams)
- Priority: LOW
- Status: NEEDINFO
- Reporter: dvhart
- 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.