| Summary: | Minnowboard UEFI Firmware 1.0 Documentation is confusing | ||
|---|---|---|---|
| Product: | [Hardware Platforms] MinnowBoard MAX Firmware | Reporter: | Bill Mills <wmills> |
| Component: | minnowboard-uefi-firmware | Assignee: | chao zhang <chao.b.zhang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | scott.a.garman, sjolley.yp.pm, warthog9, wmills |
| Version: | unspecified | ||
| Target Milestone: | Production Release | ||
| Hardware: | MinnowBoard | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Bill Mills
2014-05-09 20:50:37 UTC
For network boot, do you mean PXE boot? Yes, the release notes refer to this as "Ethernet (PXE)", "PXE IPV4" and "PXE IPV6". What I mean is any boot that uses BOOTP or DHCP + TFTP to get Grub and kernel etc. Most x86 users refer to this as PXE even if none of the PXE specific protocols are being used. The PXE specific protocols are: 1) a BIOS specific set of runtime services that are not used in UEFI. 2) DHCP extensions that allows the boot server to be distint from the DHCP server [many common installations do not seperate the DHCP and Boot servers.] 3) DHCP extensions that better identify the end equipment to the DHCP or Boot server. I wrote this mostly as input so the MinnowMax release notes could be better. Please update Minnow firmware to V1.10. PXE boot with IPv4/v6 stack is verfied OK Please update Minnow firmware to V1.10. PXE boot with IPv4/v6 stack is verfied OK MinnowBoard v1 has reached new feature EOL, FW development is done as are new hardware features. If you feel EXCEEDINGLY strongly about an issue please re-open it for discussion but be aware that we are recommending individuals migrate to the MAX platform. |