linux-sunxi.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>
Cc: linux-sunxi@lists.linux.dev, linux-sunxi@googlegroups.com
Subject: Re: Mainlining Linux Sunxi SoC AW USB
Date: Sat, 24 Jul 2021 18:46:24 +0200	[thread overview]
Message-ID: <YPxD4J3u2jo319JY@pevik> (raw)
In-Reply-To: <4183659.s5WrjGzUDR@jernej-laptop>

Hi Jernej,

[ Dropping Greg and linux-usb@vger.kernel.org ]

> Dne sobota, 24. julij 2021 ob 16:22:16 CEST je Petr Vorel napisal(a):
> > Hi Greg,

> > > On Sat, Jul 24, 2021 at 03:41:42PM +0200, Petr Vorel wrote:
> > > > > 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.> 
> > > Ah, that's not going to be good then.  Really, this doesn't seem to need
> > > to be a driver at all, and the ioctls are really strange so we would
> > > need to change them anyway before it could be merged.  But with no
> > > access to userspace code, that will be quite difficult, so I would push
> > > back on allwinner and have them work on resolving this.

> > Understand, it makes sense. Thanks for your time!

> > @Sunxi community: am I missing something? Using LiveSuit with old distro
> > chroot and Xephyr with out-of-tree module isn't fun :(.

> Community is mostly concerned with mainline kernel nowadays and thus with 
> standard tools. Few people still use vendor (BSP) kernel and most of those use 
> it without LiveSuit (like custom distro images).
Understand. LiveSuit is for me a way back to original firmware.

Kind regards,
Petr

> Now and then people ask about LiveSuit on IRC, but they usually get little 
> response.

> Best regards,
> Jernej

  reply	other threads:[~2021-07-24 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YPvjYIsu0G0HSu5I@pevik>
     [not found] ` <YPvrpUZ/VRc0eHvA@kroah.com>
2021-07-24 13:41   ` Mainlining Linux Sunxi SoC AW USB 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 16:27           ` Petr Vorel
2021-07-24 17:04             ` Andre Przywara
2021-07-25 23:31               ` Petr Vorel
2021-07-28 14:16               ` Maxime Ripard
2021-07-24 14:54         ` Jernej Škrabec
2021-07-24 16:46           ` Petr Vorel [this message]
2021-07-24 14:49     ` Felipe Balbi
2021-07-24 16:34       ` Petr Vorel

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=YPxD4J3u2jo319JY@pevik \
    --to=petr.vorel@gmail.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux-sunxi@lists.linux.dev \
    /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).