On Mon, 3 Jun 2002 00:44, Oliver Neukum wrote: > Am Sonntag, 2. Juni 2002 01:16 schrieben Sie: > > On Sun, 2 Jun 2002 02:07, Oliver Neukum wrote: > > > The problem is that this cannot simply work, because a filesystem may > > > be mounted by nfs. > > > > How is this a problem? You simply need to bring the driver up before you > > remount the nfs filesystem. If you assume that your firmware is on that > > filesystem, then you couldn't have mounted it in the first place. > > > > What am I missing here? > > Paging. As soon as user space is running, dirty pages may be written out > And in order to run a user space firmware loader, user space must > be functional, or am I overlooking something? The software support option requires swap to store to, right? That had better be on a local disk, or it doesn't matter whether the firmware is in userspace or not. Realistically, swap over a network block device isn't a problem worth trying to solve.
> Thus as soon as you do something that allocates memory from user > space, you may deadlock IMHO. If you are going to get the firmware from disk (per your alternative suggestion), how is that going to help avoid the malloc? Brad -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
