From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: xHCI driver
Date: Sat, 26 Nov 2016 12:29:37 +0300 [thread overview]
Message-ID: <2832b6d2-cf7f-b8fe-340b-7dacb4b0dc98@gmail.com> (raw)
In-Reply-To: <CAEYzJUG9ExzfAqaRCh0RDqSD89t0iJ0YyKKcUB=dZX3kzDXBOQ@mail.gmail.com>
25.11.2016 15:43, Bjørn Forsman пишет:
> Hi GRUB developers,
>
> 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 :-)
>
What platforms do you target? Note that on most platforms grub relies on
firmware services to access devices, so those direct hardware access
drivers simply are not used.
> 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?
>
> Best regards,
> Bjørn Forsman
>
> [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.
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
next prev parent reply other threads:[~2016-11-26 9:29 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 [this message]
2016-11-28 8:48 ` Bjørn Forsman
2016-11-28 10:32 ` Andrei Borzenkov
2016-11-26 18:00 ` Paul Menzel
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=2832b6d2-cf7f-b8fe-340b-7dacb4b0dc98@gmail.com \
--to=arvidjaar@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).