> From: Mike Detwiler [mailto:j.michael.detwi...@gmail.com]
> Sent: Friday, June 10, 2011 4:34 AM
> 
> On Thu, May 12, 2011 at 6:12 PM, Mike Detwiler <j.michael.detwi...@gmail.com> 
> wrote:
> > On Thu, May 12, 2011 at 12:49 PM, Cihula, Joseph
> > <joseph.cih...@intel.com> wrote:
> >>> From: Mike Detwiler [mailto:j.michael.detwi...@gmail.com]
> >>> Sent: Thursday, May 12, 2011 3:31 AM
> >>>
> >>> On Thu, May 12, 2011 at 12:41 AM, Cihula, Joseph 
> >>> <joseph.cih...@intel.com> wrote:
> >>> >> From: Mike Detwiler [mailto:j.michael.detwi...@gmail.com]
> >>> >> Sent: Wednesday, May 11, 2011 6:22 PM
> >>> >>
> >>> >> Hi, just wondering if anyone had any thought on this.
> >>> >
> >>> > Tboot does not have EFI support.  In addition to what it would
> >>> > need to do with regards to
> >>> getting the memory map and ACPI tables, it would also need to fill
> >>> in the OsSinitData.EfiRsdtPtr with the correct value (and this being 0 is 
> >>> what is generating
> the SINIT error).
> >>>
> >>> Thanks for the response, Joe. Does this imply that the current i5/i7
> >>> SINIT ACM available from sourceforge has all the bits necessary for
> >>> EFI, and as soon as tboot support is added everything should work?
> >>
> >> Correct (again, patches welcome ;-).
> >
> > We're definitely looking into that and will let you know if we get
> > something working.
> 
> We're using 64-bit EFI/grub2. Is there anything that would prevent TXT and 
> tboot from functioning
> properly if we were to successfully port tboot from 32-bit to 64-bit?

Not that I'm aware of.

Joe

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
tboot-devel mailing list
tboot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tboot-devel

Reply via email to