> > It's my understanding that while folk can do things like that with > > 8051-based chips like EZ-USB FX/FX2, they usually do it with > > bank switching. So that if the firmware isn't in ROM, they'd > > need a boot loader that knows how to populate each of the > > various banks of memory. > > Bank switching is only possible if you have an external ram with banks to > be switched
Given you're talking about firmware, I think alternate I2C ROMS can be used too. But again you're talking design options, and the issue of interest is how many widely used designs take each approach. > > Seems to me that anything outside of a simple load-at-init > > model, for a flat address space in the device, is a special > > case already. > > So IMHO the current list of special cases (either not simple load-at-init > or due to resume/VM issues) is already at least: > - usb/storage (swapping to usb-disk) Other than the fact that this needs to be made safer, and that (like swapping over NFS) it can't ever be as safe as swapping to a non-removable drive, what do you mean? > - usb/serial, if boot loader required That's a load-at-init case. Even for a two stage loader. > - all usb-ethernet bridges (swapping over NFS) Kaweth needs load-at-init firmware, others (now in the Linux kernel anyway) don't. ... so I don't see _any_ special cases there - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
