Hi, > You are thinking about keeping the tx API untouched and modify the key > install logic? > Just prevent the firmware to activate a key for Tx when it's installed > and notify the firmware by some means when the key can be used for Tx > and then switch everything to the new key? Something like that, yes. > I guess there is no practical way I can get access to the firmware code, > correct? There isn't, yeah. > For me it sounds harder than the optional flag extension I had > in mind for the new tx API. Much more of the TX path is actually wired into the hardware, rather than being software. I'm not sure how much of this (key selection) really is though. > So let's wait and see what you can turn up. Till then we have more than > enough other cards supporting Extended Key ID:-) Yeah. I'll take a look, but I can't promise right now to work on it high priority. johannes
