grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: grub-devel@gnu.org
Cc: "Bjørn Forsman" <bjorn.forsman@gmail.com>
Subject: Re: xHCI driver
Date: Sat, 26 Nov 2016 19:00:48 +0100	[thread overview]
Message-ID: <1480183248.1150.36.camel@users.sourceforge.net> (raw)
In-Reply-To: <CAEYzJUG9ExzfAqaRCh0RDqSD89t0iJ0YyKKcUB=dZX3kzDXBOQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]

Dear Bjørn,


Am Freitag, den 25.11.2016, 13:43 +0100 schrieb Bjørn Forsman:

> My name is Bjørn Forsman, first time poster. I've been tasked to make
> an xHCI driver for GRUB at my $dayjob. The end goal is to have smart
> card (CCID) reader functionality. We already have a working CCID
> driver on top of EHCI. I have no prior experience with xHCI (nor EHCI
> for that matter), so this is quite the learning experience :-)
> 
> I looked in the GRUB mailing list archive and found a couple of old
> threads about xHCI[1], but it looks like there has never been an
> attempt at writing that driver.
> 
> Some questions:
> 
> * Is there interest in xHCI driver for GRUB? If so I can post patches
> when there is something that works (more or less).
> 
> * I see the iPXE project has an xHCI driver. Any thoughts on using
> that as a basis? I'm a bit unsure about the licensing, whether iPXE is
> GPLv2 *only* or "at your option, any later version". I guess if it's
> GPLv2+ it is compatible with GRUB's GPLv3+, or else not. Correct?

The project libpayload, which is used quite a lot in the coreboot
community, also provides a well tested xHCI driver [2], which you could
use, as it’s BSD licensed.


Thanks,

Paul


> [1]: The "xhci support?" thread from 2012 and "[PATCH]: xHCI/EHCI -
> Windows - BIOS bug interaction." from late 2013 which added a quirk
> for an Intel controller.

[2]: https://review.coreboot.org/cgit/coreboot.git/tree/payloads/libpay
load/drivers/usb

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      parent reply	other threads:[~2016-11-26 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 12:43 xHCI driver Bjørn Forsman
2016-11-25 21:39 ` Daniel Kiper
2016-11-28  8:37   ` Bjørn Forsman
2016-11-26  9:29 ` Andrei Borzenkov
2016-11-28  8:48   ` Bjørn Forsman
2016-11-28 10:32     ` Andrei Borzenkov
2016-11-26 18:00 ` Paul Menzel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1480183248.1150.36.camel@users.sourceforge.net \
    --to=paulepanter@users.sourceforge.net \
    --cc=bjorn.forsman@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).