>>> Even though it makes me wonder whether f_mass_storage isn't missing >>> something in its original code. >> >> I wondered about that too. The difference is that f_mass_storage uses >> the composite framework. How does composite handle disconnects and >> port resets? The framework might need to be modified to pass these >> events down to the function drivers in separate ways.
Chen Peter-B29397 <[email protected]> writes: > f_mass_storage does not have disconnect callback, and do noop at > FSG_STATE_DISCONNECT case. I can't find where f_mass_storage calls > fsg_lun_fsync_sub when disconnect occurs. Yep, that seems to be the issue. I'll try to take a look at it later this week to figure out what f_mass_storage should do. -- Best regards, _ _ .o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michał “mina86” Nazarewicz (o o) ooo +----<email/xmpp: [email protected]>--------------ooO--(_)--Ooo--
pgpdNoP9glIsc.pgp
Description: PGP signature
