On Fri, Feb 17, 2006 at 11:12:16AM -0600, Noah yan wrote: > On 2/17/06, Matt Sealey <matt at genesi-usa.com> wrote: > > > > > > Answers: > > > > 1) load-base, auto-boot? works. What's real-mode? :) > > > > read-mode set the address as physical one, not the virtual address. but > seems this env is not much used.
we run with mmu off in the firmware, so this is not really needed. > 2) telnet not yet but disk and tftp is okay (dhcp broken in 1.2, specify > > the ip etc. manually - devices are "eth" and "geth") > > > > that is enough as long as tftp is good. Yep. > 3) you need 1.3 to use usb mass storage devices > > > > Sven? These guys should have new firmwares.. > > > The user interface should be enough. but the main concern is there are so > many methods (words in firmware terms) and properties that a firmware client > program will call. solaris promif (usr/src/psm/promif) calls the client > handler to request the properties or just call the word. the code in promif > assmue that the firmware is compliant with IEEE1275 core, ppc and chrp > binding. so how much does the smartfirmware implement those standard? they They should be conformant, anything that fails is a bug that i will fix, please mail any such failure to the firmware support email address : firmware-support at pegasosppc.com > are enough for grub2 and linux which call firmware client handler booting > up, but it seems the solaris promif implements (and need?) most of the > standard, much more than needed as in grub2 and linux. It should work, but there is a little bug in the client read/seek interface i am working on, will provide you a firmware snapshot as soon as it i fix this, ok ? Friendly, Sven Luther
