rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Stappers <stappers@stappers.nl>
To: Andrej Shadura <andrew.shadura@collabora.co.uk>
Cc: rust-for-linux@vger.kernel.org
Subject: Porting drivers
Date: Fri, 16 Apr 2021 14:25:31 +0200	[thread overview]
Message-ID: <20210416122531.76z5e6mgkfxyqhgw@gpm.stappers.nl> (raw)


Previous-Subject: Re: [PATCH 09/13] Samples: Rust examples
In-Reply-To: <dcaca535-2df3-3224-82c3-1a49a2208f30@collabora.co.uk>

On Fri, Apr 16, 2021 at 01:46:03PM +0200, Andrej Shadura wrote:
> Hi,
> 
> On 14/04/2021 21:42, Miguel Ojeda wrote:
> > On Wed, Apr 14, 2021 at 9:34 PM Linus Torvalds wrote:
> >>
> >> Honestly, I'd like to see a real example. This is fine for testing,
> >> but I'd like to see something a bit more real, and a bit less special
> >> than the Android "binder" WIP that comes a few patches later.
> >>
> >> Would there be some kind of real driver or something that people could
> >> use as a example of a real piece of code that actually does something
> >> meaningful?
> > 
> > Yeah, we are planning to write a couple of drivers that talk to actual
> > hardware. Not sure which ones we will do, but we will have them
> > written.
> 
> I’m curious what’s the procedure and approach in general to adding new
> APIs? I was thinking of trying to port my driver but it needs USB HID
> and either LEDs or hwrandom (depending on which part I start porting
> first), so obviously it’s not doable right now, but I’m thinking about
> maybe helping with at least some of those.


My help will be keeping quiet,  avoiding making distractions.
I'm still learning to do so.  :-/


Regards
Geert Stappers
Updated the Subject and broke the mail thread.     :-)
-- 
Silence is hard to parse

                 reply	other threads:[~2021-04-16 12:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210416122531.76z5e6mgkfxyqhgw@gpm.stappers.nl \
    --to=stappers@stappers.nl \
    --cc=andrew.shadura@collabora.co.uk \
    --cc=rust-for-linux@vger.kernel.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).