[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: xHCI driver
From: |
Paul Menzel |
Subject: |
Re: xHCI driver |
Date: |
Sat, 26 Nov 2016 19:00:48 +0100 |
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
signature.asc
Description: This is a digitally signed message part