From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2a00:1450:4864:20::42a; helo=mail-wr1-x42a.google.com; envelope-from=brad@sensel.com; receiver=edk2-devel@lists.01.org Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 6761B211BD5F8 for ; Tue, 29 Jan 2019 13:54:48 -0800 (PST) Received: by mail-wr1-x42a.google.com with SMTP id t27so23811979wra.6 for ; Tue, 29 Jan 2019 13:54:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sensel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=XqTMmkH0hrETYERjwR17prAsq1ueo/w/z54A26TYQqU=; b=f9VVx6vfB3Y37dNRFvwunYjmNIjCbmG882sQsgv8OBaQYynf65TQ8QafpBGDnpTGGo /1ws1znukJadr2h+oFBOrx3owsIYCHWXZ8P03rgQplWjg9e79cRUz2Aw8I2Xaxoa1VTg 56IlzVBX+7yc5gGvD5fTbg94e/FMjZdeGIWfteofem9Hp1Mfzc5KBQsqj7XWvFtOXUp0 AuQW5JdzBoE/wifZdcENebKDOSq/2z00FAaa6Q7Vm62UOXzuOOIH0CnRWWUVTcbbt2rw ul4yE9QAr6XdC8TTuhQZNLzGchb90y0hUJzAs0EhGo+mA8SKuXxsuB8v4Cy1qqTcMFSQ vk3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=XqTMmkH0hrETYERjwR17prAsq1ueo/w/z54A26TYQqU=; b=Q2IZvK/Tp5RInq2iTXV6g2mhB9OEHV79u8y5mY5VLcdEck1kES8FPxx4abkTYvfOmI aixDWLdEFwj5RYzMehbjs0M0GmCxTdBRSA+mxQHB+hlMarajoMjQUAEANwRwYDG8erM/ Ycn+UYDr09k3DSiFJ87PNFPq5UgSU92n9dZt2rPm8CwmUectex23wj7003Fjc86lXvE2 p4xZ2/ZdBUwQmsZsVfJ0AQzM+MaJRuixix64A0gMtxDXSw1ZughrKTG16BS2abY7baIh 1yGM3eAIaCeKFTdQfDvrF0idkX/7xvdUrD8+LbxV5pOtoantaFHr8gaZX7yNBmqmFx96 8u4w== X-Gm-Message-State: AJcUukdwzkenP85721M1h6yR5FLQwgYzY9HklOtxtp57Flw6m6KgS2Jj dHnYKVGFmI9stk2WwGkEeIqT3Q7/7Gf0vDzQTaMNIYuhNpA= X-Google-Smtp-Source: ALg8bN4NuFIgjTcilyPd4VP/HOv8FE+8aWfLUutuG2FOy0WdqyUT1U0M790gw4eFfWkEpHr9Yyi0Cz5nuYNr1v2TvOk= X-Received: by 2002:adf:ba8e:: with SMTP id p14mr26881819wrg.230.1548798886593; Tue, 29 Jan 2019 13:54:46 -0800 (PST) MIME-Version: 1.0 From: Brad Bozarth Date: Tue, 29 Jan 2019 16:54:35 -0500 Message-ID: To: edk2-devel@lists.01.org X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Peripheral FW capsule delivery? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2019 21:54:48 -0000 Content-Type: text/plain; charset="UTF-8" Hi! I am implementing firmware for a touchpad that will be going into a laptop, connected via i2c. We would like to take advantage of the UEFI firmware capsule delivery method for firmware updates if possible. I am struggling to find out how to do this. In particular, I'd like to know whether there is a "standard" delivery mechanism we can take advantage of and communicate with from the firmware side over i2c, or if we need to write UEFI driver code of some sort to pass the update down. We'd love to leverage a standard pipe that dumps an update over i2c if possible and implement what we need to on the firmware side. We are supplying our touchpad to the laptop OEM and they are distant and have their own software teams, so if we need to write UEFI code, it complicates matters! This is the page that I'd love to read, if it were filled out :) https://github.com/mdkinney/edk2/wiki/Capsule-Based-Device-Firmware-Update Thank you! Brad