just don't remember if i've applied it :)
but, it seems like i haven't seen no more "Eagle0" :)
matthieu castet wrote:
matthieu castet wrote:
Frederick Ros wrote:
Quoting matthieu castet <[EMAIL PROTECTED]>:
Frederick Ros wrote:
Well there are no user for the module so why hotplug or another things
could not unload the modules ?
Yes .. but it leads to inconsistency between non-hotplugged machine
and hotplug
enabled ones ... For the former we know that the module is not
unloaded and
therefore we could have some static (common to all instance of a modem)
information whereas on hotplug-enabled we can't take it for granted ...
What happen if I reboot and the modem have already the firmware...
Yep .. This is a point : in this case the moem is seen as a
post-firmware (i.e
that is what happened in my box even when it was off, as USB ports
were still
pwered on ..) .. We have no clue in this case to get the firmware
level ...
except for explicitely checking the product id ...
I found some time to finalized my patch with driver info.
It is quite ugly, because i don't to touch much code but :
- eu_instance_t should be allocated in probe and we pass 'ins' to
eu_init_*
- the use of CASE_PREFIRM, CASE_POSTFIRM and all macro comaring id
should be replaced.
So what about this patch ?
_______________________________________________
Eagleusb-dev mailing list
[email protected]
https://mail.gna.org/listinfo/eagleusb-dev
