On 2/19/24 10:49, Shantur Rathore wrote:
Hi Marek,
On Wed, Feb 14, 2024 at 9:55 AM Shantur Rathore wrote:
Additional testing of the changes introduced in commit 33e06dcbe57a "common:
usb-hub: Reset hub port before scanning") revealed that some USB 2.0 and 3.0
flash drives didn't work in
On 2024-02-19 19:24, Marek Vasut wrote:
On 2/14/24 10:54, Shantur Rathore wrote:
Additional testing of the changes introduced in commit 33e06dcbe57a
"common:
usb-hub: Reset hub port before scanning") revealed that some USB 2.0
and 3.0
flash drives didn't work in U-Boot on some Allwinner SoCs
On 2/14/24 10:54, Shantur Rathore wrote:
Additional testing of the changes introduced in commit 33e06dcbe57a "common:
usb-hub: Reset hub port before scanning") revealed that some USB 2.0 and 3.0
flash drives didn't work in U-Boot on some Allwinner SoCs that support USB
2.0 interfaces only. More
Hi Marek,
On Wed, Feb 14, 2024 at 9:55 AM Shantur Rathore wrote:
>
> Additional testing of the changes introduced in commit 33e06dcbe57a "common:
> usb-hub: Reset hub port before scanning") revealed that some USB 2.0 and 3.0
> flash drives didn't work in U-Boot on some Allwinner SoCs that
Additional testing of the changes introduced in commit 33e06dcbe57a "common:
usb-hub: Reset hub port before scanning") revealed that some USB 2.0 and 3.0
flash drives didn't work in U-Boot on some Allwinner SoCs that support USB
2.0 interfaces only. More precisely, some of the tested USB 2.0 and
5 matches
Mail list logo