|
From: Seiji M. <sei...@gm...> - 2008-12-04 10:41:39
|
Hi Ross, On Tue, Dec 2, 2008 at 10:44 PM, Ross Philipson <Ros...@ci...> wrote: > Yeah, I saw the same thing when I was trying to get it to work. I forced > it to load and saw the status check fail in the debugger. I think I > tried working around issue at the time by ignoring the status but > something failed downstream and I couldn't use the iTPM even though the > driver loaded and ready. Did you actually try sending it work to do - > you may find it still doesn't work? Anyway it was a while ago so I don't > remember all the details. I can take the ownership of iTPM, but don't run testsuite. I have take a look the tpm_tis code a bit more. "default time out" values should be set before call request_locality() in tpm_tis_init function. This is the reason why first modprobe with force=1 is fail. regards, Seiji |