I agree with you, you are right in everything you wrote! It is annoying to see
theoretic numbers and not the actual numbers the hardware implementing the
specification can support but something else is in my mind
too...N�r��yb�X��ǧv�^�){.n�+{��^n�r���z���h�&�� �G���h�(�階�ݢ
From: Adrian Bocaniciu
> Sent: 30 September 2017 09:18
> On Fri, 29 Sep 2017 09:06:16 +
> David Laight wrote:
>
> > > The correct names used in the new specification for the 4 speeds that can
> > > be supported by a USB 3
> > > interface are: .
> >
> > I think I'd add the speed itself as wel
Commit dfebb5f43a78 ("usb: chipidea: Add support for Tegra20/30/114/124")
added UDC support for Tegra but with UDC support enabled, is was found
that Tegra30, Tegra114 and Tegra124 would hang on entry to suspend.
The hang occurred during the suspend of the USB PHY when the Tegra PHY
driver attempt
On 29.09.2017 14:07, Jeffy Chen wrote:
KASAN reported use-after-free bug when xhci host controller died:
[ 176.952537] BUG: KASAN: use-after-free in
xhci_handle_command_timeout+0x68/0x224
[ 176.960846] Write of size 4 at addr ffc0cbb01608 by task kworker/3:3/1680
...
[ 177.180644] Freed b
On Mon, Oct 02, 2017 at 12:22:53PM +0100, Jon Hunter wrote:
> Commit dfebb5f43a78 ("usb: chipidea: Add support for Tegra20/30/114/124")
> added UDC support for Tegra but with UDC support enabled, is was found
> that Tegra30, Tegra114 and Tegra124 would hang on entry to suspend.
>
> The hang occurr
On Sun, 2017-10-01 at 22:32 +0200, Martin Blumenstingl wrote:
> Hello Greg, Hello Mathias,
>
> On Mon, Sep 18, 2017 at 10:49 AM, Greg KH wrote:
> > On Sun, Sep 17, 2017 at 10:51:31PM +0200, Martin Blumenstingl wrote:
> > > Hello Mathias, Hello Greg,
> > >
> > > On Sun, Sep 3, 2017 at 11:38 PM, M
On Mon, Oct 02, 2017 at 02:35:08PM +0200, Jerome Brunet wrote:
> On Sun, 2017-10-01 at 22:32 +0200, Martin Blumenstingl wrote:
> > Hello Greg, Hello Mathias,
> >
> > On Mon, Sep 18, 2017 at 10:49 AM, Greg KH
> > wrote:
> > > On Sun, Sep 17, 2017 at 10:51:31PM +0200, Martin Blumenstingl wrote:
>
+Cc: Greg, Felipe and Takashi. I hope they would point you to a right direction.
On Sun, Oct 1, 2017 at 9:07 PM, Владимир Мартьянов wrote:
> Hello!
>
> I just bought MIDI keyboard WORLDE MINI (looks like full chinese clone
> af Arturia Minilab with the same vid:pid) and it won't work in Linux.
>
On Sun, Oct 1, 2017 at 10:30 PM, Jérémy Lefaure
wrote:
> Using the ARRAY_SIZE macro improves the readability of the code. Also,
> it is not always useful to use a variable to store this constant
> calculated at compile time.
>
> + {&gainctrl_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev
Andy Shevchenko writes:
> +Cc: Greg, Felipe and Takashi. I hope they would point you to a right
> direction.
>
> On Sun, Oct 1, 2017 at 9:07 PM, Владимир Мартьянов
> wrote:
>> Hello!
>>
>> I just bought MIDI keyboard WORLDE MINI (looks like full chinese clone
>> af Arturia Minilab with the sam
Jérémy Lefaure writes:
> Using the ARRAY_SIZE macro improves the readability of the code. Also,
> it is not always useful to use a variable to store this constant
> calculated at compile time.
>
> Found with Coccinelle with the following semantic patch:
> @r depends on (org || report)@
> type T;
On Mon, 2 Oct 2017, Felipe Balbi wrote:
> >> Should the Linux kernel concern about such buggy devices? If it
> >> should, what's the best way to bypass the problem?
>
> well, just apply the quirk to your device:
>
> modified drivers/usb/core/quirks.c
> @@ -41,6 +41,10 @@ static const struct us
On 09/30/2017 07:18 PM, Ben Hutchings wrote:
> usbip_host_driver.h now depends on several additional headers, which
> need to be installed along with it.
>
> Fixes: 021aed845303 ("staging: usbip: userspace: migrate usbip_host_driver
> ...")
> Fixes: 3391ba0e2792 ("usbip: tools: Extract generic co
On Fri, 2017-09-22 at 22:18 +0200, Bjørn Mork wrote:
> The driver will forward errors to userspace after turning most of
> them
> into -EIO. But all status codes are not equal. The -EPIPE (stall) in
> particular can be seen more as a result of normal USB signaling than
> an actual error. The state
On 02.10.2017 14:22, Jon Hunter wrote:
> Commit dfebb5f43a78 ("usb: chipidea: Add support for Tegra20/30/114/124")
> added UDC support for Tegra but with UDC support enabled, is was found
> that Tegra30, Tegra114 and Tegra124 would hang on entry to suspend.
>
> The hang occurred during the suspend
Em Sun, 1 Oct 2017 20:52:20 -0400
Jérémy Lefaure escreveu:
> Anyway, I can tell to each maintainer that they can apply the patches
> they're concerned about and next time I may send individual patches.
In the case of media, we'll handle it as if they were individual ones.
Thanks,
Mauro
--
To un
On Sun, Oct 1, 2017 at 10:39 PM, David Miller wrote:
> From: Grant Grundler
> Date: Thu, 28 Sep 2017 11:35:00 -0700
>
>> This linksys dongle by default comes up in cdc_ether mode.
>> This patch allows r8152 to claim the device:
>>Bus 002 Device 002: ID 13b1:0041 Linksys
>>
>> Signed-off-by: G
Oh, I didn't know about quirks.c. Your code solved the problem, thank you!
2017-10-02 16:09 GMT+03:00 Felipe Balbi :
> Andy Shevchenko writes:
>
>> +Cc: Greg, Felipe and Takashi. I hope they would point you to a right
>> direction.
>>
>> On Sun, Oct 1, 2017 at 9:07 PM, Владимир Мартьянов
>> wr
On Mon, Oct 02, 2017 at 07:35:54AM +0200, Greg KH wrote:
> On Sun, Oct 01, 2017 at 08:52:20PM -0400, Jérémy Lefaure wrote:
> > On Mon, 2 Oct 2017 09:01:31 +1100
> > "Tobin C. Harding" wrote:
> >
> > > > In order to reduce the size of the To: and Cc: lines, each patch of the
> > > > series is sent
Hello,
I am currently working on a custom Armada 385-based board running
kernel 4.9.52. I have a USB 2.0 LTE modem connected to USB 3.0, and
the modem sometimes crashes due to various internal (on the modem)
reasons. The board supports restarting the USB-ports using GPIOs, and
at random points whe
Bringing in Josh on this, because the merge commit gets fingered
because it seems to be an interaction between the new code from the
merge and the ORC unwinder changes. It's probably some almost trivial
code difference that just causes some code generation to change.
And because Josh wasn't implic
On Mon, Oct 02, 2017 at 01:09:31PM -0700, Linus Torvalds wrote:
> Bringing in Josh on this, because the merge commit gets fingered
> because it seems to be an interaction between the new code from the
> merge and the ORC unwinder changes. It's probably some almost trivial
> code difference that jus
On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote:
> Fengguang, assuming it's reliably recreatable, any chance you could
> recreate with the following patch?
Sorry, here's a version which actually compiles.
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
On Mon, Oct 2, 2017 at 2:26 PM, Josh Poimboeuf wrote:
>
> The bisect is pointing to a commit which is almost 5 months old, so this
> is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
> enough to realize it's dumping misaligned stack addresses:
Ahh, I didn't pick up on that "es
From: Aleksander Morgado
Date: Wed, 27 Sep 2017 23:31:03 +0200
> I'm not sure if binding this logic to a specific vid:pid (1410:9030)
> would be more appropriate here, or if it's ok to just bind
> class/subclass/protocol (as in the activesync case). Let me know
> what you think.
I don't have en
Hi Greg,
On Mon, Oct 2, 2017 at 2:44 PM, Greg KH wrote:
> On Mon, Oct 02, 2017 at 02:35:08PM +0200, Jerome Brunet wrote:
>> On Sun, 2017-10-01 at 22:32 +0200, Martin Blumenstingl wrote:
>> > Hello Greg, Hello Mathias,
>> >
>> > On Mon, Sep 18, 2017 at 10:49 AM, Greg KH
>> > wrote:
>> > > On Sun
> All of the character devices is not working properly with low level I/O.
>
> The details are
>> taken care by the driver. Am I correct in understanding that this is
>> not a way to do it with UVC, i.e. the sequence of steps is different
>> (open, some different steps, close) ?
>
> yes. you need t
On Mon, Oct 02, 2017 at 02:58:08PM -0700, Linus Torvalds wrote:
> On Mon, Oct 2, 2017 at 2:26 PM, Josh Poimboeuf wrote:
> >
> > The bisect is pointing to a commit which is almost 5 months old, so this
> > is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
> > enough to realize i
On Mon, 2 Oct 2017 15:22:24 -0400
bfie...@fieldses.org (J. Bruce Fields) wrote:
> Mainly I'd just like to know which you're asking for. Do you want me to
> apply this, or to ACK it so someone else can? If it's sent as a series
> I tend to assume the latter.
>
> But in this case I'm assuming it'
On Mon, 02 Oct 2017 16:46:29 +0300
Kalle Valo wrote:
> We have a tree for wireless so usually it's better to submit wireless
> changes on their own but here I assume Dave will apply this to his tree.
> If not, please resubmit the wireless part in a separate patch.
Ok, I note that.
I'll wait Dave
On Mon, 2 Oct 2017 16:07:36 +0300
Andy Shevchenko wrote:
> > + {&gainctrl_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev0), 26,
> > 192,
> > +32},
>
> For all such cases I would rather put on one line disregard checkpatch
> warning for better readability.
I agree that it woul
On Fri, Sep 29, 2017 at 8:01 AM, Chanwoo Choi wrote:
> The extcon has two type of extcon devices as following.
> - 'extcon provider deivce' adds new extcon device and detect the
>state/properties of external connector. Also, it notifies the
>state/properties to the extcon consumer device.
Hi Josh,
On Mon, Oct 02, 2017 at 04:31:09PM -0500, Josh Poimboeuf wrote:
On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote:
Fengguang, assuming it's reliably recreatable, any chance you could
recreate with the following patch?
Sure, I'll try your patch on v4.14-rc3 since it looks
33 matches
Mail list logo
