From: Felipe Balbi <balbi@kernel.org>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-sunxi@googlegroups.com
Subject: Re: Mainlining Linux Sunxi SoC AW USB
Date: Sat, 24 Jul 2021 17:49:54 +0300 [thread overview]
Message-ID: <87zgub6a25.fsf@kernel.org> (raw)
In-Reply-To: <YPwYlvh4DqaUsPCF@pevik>
Hi,
Petr Vorel <petr.vorel@gmail.com> writes:
>> > [1] https://github.com/linux-sunxi/sunxi-livesuite/blob/master/awusb/awusb.c
>
>> Why is this even a driver at all, it looks like you can write a small
>> userspace program using libusb to do everything it does, right? What
>> exactly is this driver needed for?
>
> I'm sorry for not providing more info at the beginning. This is a driver for
> host computer (i.e. developers laptop) used by LiveSuit tool [2] to flash Images
> to the NAND of Allwinner devices. LiveSuit itself [3] is unfortunately provided
> only in binary form. The only open source code with GPL v2 license is awusb
> driver. Thus I thought I could ease my life with upstreaming at least the
> kernel driver. But maybe it's not a good idea. I'm using LiveSuit for flashing
> Allwinner A31, but it requires quite old distro due libqtgui4. Maybe sunxi folks
> use something newer nowadays, but I haven't found anything in their wiki.
looks like you could implement that entirely in userspace with libusb ;-)
--
balbi
prev parent reply other threads:[~2021-07-24 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 9:54 Mainlining Linux Sunxi SoC AW USB Petr Vorel
2021-07-24 10:29 ` Greg KH
2021-07-24 13:41 ` Petr Vorel
2021-07-24 14:17 ` Greg KH
2021-07-24 14:22 ` Petr Vorel
2021-07-24 14:45 ` [linux-sunxi] " Christopher Obbard
2021-07-24 14:54 ` Jernej Škrabec
2021-07-24 14:49 ` Felipe Balbi [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=87zgub6a25.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=petr.vorel@gmail.com \
/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).