Re: [PATCH] Intel Management Engine Interface

> Actually no TCP/IP is needed here. Basically the MEI driver writes and reads the
> messages to/from the firmware. When communicating in-band using LMS, TCP/IP
> terminates at LMS and the messages are copied using MEI driver.

Ah that's good to know. I suspect the SOAP interchange could be stripped
down a lot to make it reasonably simple; ideally with all strings just hardcoded
somewhere. Would much parsing be needed?

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] Intel Management Engine Interface
    • From: Anas Nashif <[email protected]>
  • Re: [PATCH] Intel Management Engine Interface
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] Intel Management Engine Interface
    • From: Anas Nashif <[email protected]>
  • Re: [PATCH] Intel Management Engine Interface
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] Intel Management Engine Interface
    • From: Anas Nashif <[email protected]>

• Prev by Date: Re: [PATCH] Intel Management Engine Interface
• Next by Date: [PATCH] parport : "dev->timeslice" is an unsigned long, not an int
• Previous by thread: Re: [PATCH] Intel Management Engine Interface
• Next by thread: Re: [PATCH] Intel Management Engine Interface
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]