From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
Felix Fietkau <nbd@nbd.name>,
Doug Anderson <dianders@chromium.org>,
Minas Harutyunyan <hminas@synopsys.com>,
USB list <linux-usb@vger.kernel.org>
Subject: [BUG] mt76x0u: Probing issues on Raspberry Pi 3 B+
Date: Mon, 11 Feb 2019 18:33:16 +0100 [thread overview]
Message-ID: <20190211173315.GE6292@redhat.com> (raw)
On Mon, Feb 11, 2019 at 10:12:57AM -0500, Alan Stern wrote:
> On Mon, 11 Feb 2019, Lorenzo Bianconi wrote:
>
> > Here it is a different issue respect to the AMD IOMMU one, dwc2 host driver
> > does not implement SG I/O so probing fails. I guess it is still useful to
> > implement a 'legacy' mode that enable mt76 on host controllers that do not implement
> > SG I/O (rpi is a very common device so it will be cool to have mt76 working on
> > it). Moreover we are not removing functionalities, user experience will remain
> > the same
>
> Has anyone considered adding SG support to dwc2? It shouldn't be very
> difficult. The corresponding change for ehci-hcd required adding no
> more than about 30 lines of code.
That would be cool. Perhaps somebody with dwc2 hardware could do this.
However in mt76x02u we possibly would like to support other usb host
drivers with sg_tablesize = 0 . I would like to clarify what is correct
to do with such drivers.
Is ok to pass buffer via urb->sg with urb->num_sgs = 1 ? Or maybe
urb->num_sgs should be 0 to pass buffer via urb->sg on such drivers ?
Or maybe non of above is correct and the only option that will work
in 100% is pass buffer via urb->transfer_buffer ?
Stanislaw
next reply other threads:[~2019-02-11 17:33 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:33 Stanislaw Gruszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-03 21:16 [BUG] mt76x0u: Probing issues on Raspberry Pi 3 B+ Stefan Wahren
2019-02-20 16:36 Lorenzo Bianconi
2019-02-20 16:32 Stanislaw Gruszka
2019-02-20 16:22 Lorenzo Bianconi
2019-02-20 16:14 Stanislaw Gruszka
2019-02-20 15:25 Alan Stern
2019-02-20 13:22 Lorenzo Bianconi
2019-02-20 13:00 Stanislaw Gruszka
2019-02-20 10:20 Stanislaw Gruszka
2019-02-19 17:02 Stefan Wahren
2019-02-19 15:40 Alan Stern
2019-02-19 12:19 Felix Fietkau
2019-02-19 12:11 Felix Fietkau
2019-02-19 10:59 Stanislaw Gruszka
2019-02-19 10:42 Stanislaw Gruszka
2019-02-18 22:19 Stefan Wahren
2019-02-18 18:52 Felix Fietkau
2019-02-18 15:03 Stanislaw Gruszka
2019-02-18 14:47 Stanislaw Gruszka
2019-02-18 14:43 Felix Fietkau
2019-02-18 14:25 Lorenzo Bianconi
2019-02-18 13:52 Stanislaw Gruszka
2019-02-16 19:17 Stefan Wahren
2019-02-16 14:07 Stanislaw Gruszka
2019-02-16 11:05 Stefan Wahren
2019-02-15 7:12 Stanislaw Gruszka
2019-02-14 9:54 Stanislaw Gruszka
2019-02-14 9:48 Stefan Wahren
2019-02-14 9:25 Stanislaw Gruszka
2019-02-14 6:49 Stefan Wahren
2019-02-13 7:05 Stefan Wahren
2019-02-12 15:27 Alan Stern
2019-02-12 13:15 Stanislaw Gruszka
2019-02-12 11:58 Lorenzo Bianconi
2019-02-12 9:30 Stanislaw Gruszka
2019-02-12 0:06 Lorenzo Bianconi
2019-02-11 17:49 Alan Stern
2019-02-11 17:22 Stanislaw Gruszka
2019-02-11 15:57 Lorenzo Bianconi
2019-02-11 15:27 Stefan Wahren
2019-02-11 15:12 Alan Stern
2019-02-11 15:10 Lorenzo Bianconi
2019-02-11 14:04 Stefan Wahren
2019-02-11 11:06 Lorenzo Bianconi
2019-02-11 10:33 Stefan Wahren
2019-02-11 10:04 Lorenzo Bianconi
2019-02-11 7:44 Stanislaw Gruszka
2019-02-10 17:39 Lorenzo Bianconi
2019-02-10 10:22 Lorenzo Bianconi
2019-02-10 9:41 Stanislaw Gruszka
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=20190211173315.GE6292@redhat.com \
--to=sgruszka@redhat.com \
--cc=dianders@chromium.org \
--cc=hminas@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=stefan.wahren@i2se.com \
--cc=stern@rowland.harvard.edu \
/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).