Le 21/11/2018 à 17:10, Frédéric Parrenin a écrit :
Le 21/11/2018 à 17:03, mario.limoncie...@dell.com a écrit :
Sent from Workspace ONE Boxer
On Nov 21, 2018 09:51, Frédéric Parrenin
wrote:
>
>
> [EXTERNAL EMAIL]
>
>
> Le 21/11/2018 à 15:19, Frédéric Parrenin a écrit :
> >
> > Le 21/11/20
On Mi, 2018-11-21 at 16:50 +0100, Frédéric Parrenin wrote:
>
> which over rides the Mac on the dock. So, the answer is, "it's not an
> issue if the dock supports it, as the laptop BIOS is what is determining
> if it is supported".
>
> So what is the truth?
For pass thru you must meet multiple
Le 22/11/2018 à 11:22, Oliver Neukum a écrit :
On Mi, 2018-11-21 at 16:50 +0100, Frédéric Parrenin wrote:
which over rides the Mac on the dock. So, the answer is, "it's not an
issue if the dock supports it, as the laptop BIOS is what is determining
if it is supported".
So what is the truth?
On 11/21/18 5:12 PM, Florian Zumbiehl wrote:
I have two pl2303 based adapters which behave the same:
ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303]
ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
What is the output of usb-devices for those?
T: Bus=01 Lev=02
writes:
> On Nov 22, 2018 03:41, Frédéric Parrenin
> wrote:
>>
>> A guy answered on the amazon page that he has Mac pass-through working
>> on windows 10 with this exact same dock station.
>> So it really seems to be a linux-only problem.
>
> Well thanks for checking further. This is quite surpr
On Do, 2018-11-22 at 12:06 +0100, Frédéric Parrenin wrote:
> Le 22/11/2018 à 11:22, Oliver Neukum a écrit :
> > On Mi, 2018-11-21 at 16:50 +0100, Frédéric Parrenin wrote:
> > > which over rides the Mac on the dock. So, the answer is, "it's not an
> > > issue if the dock supports it, as the
Improve baud-rate generation by using rounding-to-closest instead of
truncation in divisor calculation.
Results have been verified by logic analyzer on an FT232RT (232BM) chip.
The following table shows the wanted baud rate, the baud rate obtained
with the old method (truncation), with the new me
Hi,
> T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=0557 ProdID=2008 Rev=03.00
> S: Manufacturer=Prolific Technology Inc.
> S: Product=USB-Serial Controller D
> C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
From: JackyChou
For now, pause to add PID 0x7843 in the driver.
Simplify the processes of some functions.
Such modifications will not affect the old devices and will make
the addition of new product (0x7843) more flexible in the future.
Signed-off-by: JackyChou
---
drivers/usb/serial/mos784
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-4.20-rc4
for you to fetch changes up to 63529eaa6164ef7ab4b90
Hi,
Ran Wang writes:
> Hello Felipe,
>
> We’ve found on some Layerscape platforms which integrating DWC3
which platform is that? Is it supported upstream? Which kernel version
are you using?
> USB3.0 DRD controller, VBUS glitch happened and caused some USB drives
what do you mean by glitch?
The pull request you sent on Thu, 22 Nov 2018 09:45:39 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-4.20-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4cd731953d620b7e4e999a90d13db58b88c5e95b
Thank you!
--
Deet-doot-dot, I am a
From: Igor Russkikh
Date: Wed, 21 Nov 2018 10:13:37 +
> + if (padding_size != 0)
> + skb_put(skb, padding_size);
I think you want to use skb_put_zero() here rather than leaving it
uninitialized. I know it's padding, but if for some reason this leaks
onto the wire or elsewher
From: Igor Russkikh
Date: Wed, 21 Nov 2018 10:13:39 +
> + desc_hdr = *(u64 *)skb_tail_pointer(skb);
> + le64_to_cpus(&desc_hdr);
This is:
desc_hdr = le64_to_cpup(skb_tail_pointer(skb));
> + /* Get the first RX packet descriptor */
> + pkt_desc = (u64 *)(skb->data +
From: Igor Russkikh
Date: Wed, 21 Nov 2018 10:13:42 +
> +static void aqc111_rx_checksum(struct sk_buff *skb, u64 *pkt_desc)
> +{
...
> + /* checksum error bit is set */
> + if (*pkt_desc & AQ_RX_PD_L4_ERR || *pkt_desc & AQ_RX_PD_L3_ERR)
> + return;
...
> @@ -661,6 +698,7
From: Igor Russkikh
Date: Wed, 21 Nov 2018 10:13:48 +
> @@ -832,6 +832,10 @@ static struct sk_buff *aqc111_tx_fixup(struct usbnet
> *dev, struct sk_buff *skb,
> /*Length of actual data*/
> tx_desc |= skb->len & AQ_TX_DESC_LEN_MASK;
>
> + /* TSO MSS */
> + tx_desc |= ((u
Hi Greg,
> On Oct 31, 2018, at 1:52 PM, Kai-Heng Feng
> wrote:
>
> USB Bluetooth controller QCA ROME (0cf3:e007) sometimes stops working
> after S3:
> [ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin
> [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)
Hi,
> On Nov 7, 2018, at 1:34 AM, Kai-Heng Feng wrote:
>
> The QCA Rome USB Bluetooth controller has several issues once LPM gets
> enabled:
> - Fails to get enumerated in coldboot. [1]
> - Drains more power (~ 0.2W) when the system is in S5. [2]
> - Disappears after a warmboot. [2]
>
> The iss
Hi Ulf,
> On Nov 8, 2018, at 8:17 PM, Oleksandr Natalenko
> wrote:
>
>> This is based on Ulf's work [1] [2].
>> This patch series can keep rtsx_usb suspended, to save ~0.5W on Intel
>> platforms and ~1.5W on AMD platforms.
>> [1] https://patchwork.kernel.org/patch/10440583/
>> [2] https://patch
Hello Felipe,
Felipe Balbi wrote:
> Hi,
>
> Ran Wang writes:
> > Hello Felipe,
> >
> > We’ve found on some Layerscape platforms which integrating DWC3
>
> which platform is that? Is it supported upstream? Which kernel version are
> you using?
We reproduced this issue on board LS1043ARDB with
Hi Tony,
On 17/11/18 7:07 PM, Tony Lindgren wrote:
> I noticed that phy_pm_runtime_get_sync() and phy_pm_runtime_put() are not
> currently doing anything for phy-mapphone-mdm6600, only the sysfs interface
> for works for "auto" and "on".
>
> This is because of the shared GPIO pins between mdm6600
21 matches
Mail list logo
