In message <[email protected]>, =?ISO-8859-1?Q?=22Ing=2E_Daniel_Rozsny=F3=22?= writes:
> > Even if we can't find a device that is extremely user friendly, we should > > at least > > use something with a socket. Then we always have a device swap available, > > both > > as a last resort for IP addresses and for firmware updates. > > > > So, have I missed any possible methods? Or pros/cons? > > Why you need a byte addressable device for that? A standard SD card > suffices for both firmware (kernel+initrd) and user settings. There is > no need to execute directly from NOR flash. Well, James wrote: } No, firmware needs to be on the other type of flash memory (NOR) that } can address individual bytes like SRAM. Flash cards (NAND) can only } address blocks of data. It certainly makes sense that firmware (at least the initial part) needs to be on a byte addressable device. I am assuming that this applies to all the BIOS stuff including our fake video card? For the ethervideo box, we would need enough byte addressable code to read from a block device. Most of the code could be on the block device. _______________________________________________ Open-hardware-ethervideo mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-hardware-ethervideo
