Am 09.08.2013 16:52, schrieb Alan Stern:
On Fri, 9 Aug 2013, Oleksij Rempel wrote:
What about a "get firmware version" sort of thing? There really should
be a way for the driver to tell whether the firmware has already been
updated.
I was not able to find good direct way to check firmware version. If i
would add some new command then i will get option like: if responding FW
is updated; if not, then dead or old.
How about overwriting iProduct field? Let say, if iProduct == ath9k_htc,
then firmware is updated? Is it more or less acceptable method? I need
to ask this because it is really new for me.
Changing the iProduct string descriptor would work, because the
descriptors_changed() routine doesn't compare the old value of that
string with the new value. (On the other hand, it does compare the
iSerialNumber strings.)
Just to make sure. You mean, i should avoid changing iSerialNumber
because host will initiate usb reset and this device will probably not
survive it?
Is there any way to read the firmware back from the device? Then you
could check directly.
No, this device is a SoC with usb client interface based on FUSB200 core
(If i'm correct, same core as on carl9170 devices). We can't read memory
unless FW provide this service.
At power on, this device will boot from external or internal ROM and
load minimal FW. Without it, USB wont work.
If i read FW code correctly, it should be responsible for suspend and reset.
I do not have documentation, so created doc[1] based on code. From what
is see, i assume that we can reset usb from FW. There is at least two
methods:
- reset complete USB core. It looks for me like brute force, since we
will need completely reconfigure usb core.
- use TEST registers? ZM_TEST_OFFSET or ZM_PHY_TEST_SELECT_OFFSET - i
didn't played with it. So it is just assumption.
- other regs?
[1] https://github.com/qca/open-ath9k-htc-firmware/wiki/usb-regs
--
Regards,
Oleksij
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
