On 11/28/2017 01:25 AM, Peter Robinson wrote:
On Tue, Nov 28, 2017 at 4:33 AM, Stewart Samuels <searider74@xxxxxxxxx> wrote:
Hello Andreas
Sorry it took me so long to get back. I have just tested kernel
4.15.0-0.rc0.git7.2.fc28.armv7hl and can confirm that indeed, USB 3 devices
are now recognized as is the onboard gigabit ethernet port. However, the
Good.
system still requires the "cpuidle.off=1" argument on the "append" line of
the extlinux.conf file to boot.
Why is this a problem?
It is not necessarily a problem IF it is understood that this is (or
will be) the normal intended behavior by the developers for getting this
device to boot. If this is the case, then it should be documented as
such so users knows they must add it.
However, IMHO, if the intended behavior is such that the system should
boot out-of-the-box without any user modification other than perhaps
installing the correct u-boot information and images, then either this
argument should be added via the install procedure(s) or it should be
added implicitly to the kernel. But as this argument is probably not
necessary for other ARM devices, the preference would be to add it via
the install procedure(s).
The other possibility is that the reason the argument needs to be
provided to begin with is because perhaps there is a bug or it avoids
some other issues that really need to be addressed, in which case, this
is only a temporary work-around. Again, IMHO if this is the case, then
the install procedure(s) should insert the argument until the issue(s)
are remedied, at which time the argument can then be removed.
Regards,
Stewart
On 11/21/2017 08:49 AM, Andreas Reschke wrote:
Am 15.11.2017 um 23:02 schrieb Stewart Samuels:
So, to follow up with my last transmission, I did indeed down load the
latest updates to both F26 & F27. The kernel I just tested on F27 is
4.13.12-200. It appears Andreas is correct in that USB 3 still does not
respond from what I can see.
Regards,
Stewart
On 11/15/2017 08:53 AM, Stewart Samuels wrote:
I was under the impression that the fix was going to be released into
kernel 4.15 based on this response from you Peter. And based on your
schedule, I was also under the impression that any of these fixes
likely would not go into earlier releases, so I haven't tested them.
As this was the last set of communications we have had regarding these
issues, I was not aware that you had actually pushed the upstream
patch. Now that I know you have, I will retest them by downloading
the latest updates to F27.
Hello together,
with the actuell kernel 4.15.0-0.rc0.git6.1.fc28.armv7hl it seems to work:
[root@odroidh1 ~]# lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153
Gigabit Ethernet Adapter
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA
Technology Corp.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@odroidh1 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 118G 0 disk
├─sda1 8:1 0 680M 0 part
└─sda2 8:2 0 6,1M 0 part
mmcblk1 179:0 0 14,9G 0 disk
├─mmcblk1p1 179:1 0 29M 0 part
├─mmcblk1p2 179:2 0 488M 0 part /boot
├─mmcblk1p3 179:3 0 488M 0 part [SWAP]
└─mmcblk1p4 179:4 0 14G 0 part /
[root@odroidh1 ~]#
Now the onboard network and the ssd is working on my Odroid HC1. Next
test is the Odroid Xu4.
Thanks to everybody who made work.
Andreas
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
