Status of 'electron752-rpi3-4.8-optee' branch? about build HOT 11 CLOSED

@igoropaniuk , you never got anywhere with this branch? You opened an issue with RPi3 kernel developers, but there is not fix yet? (FIQ/IRQ issue?)

from build.

hi @msa2,
I've already spent quite a lot of time on trying to fix this, but still without any success. There is an issue in enumeration of usb root host by dwc2, that's why networking doesn't work (smsc95xx USB 2.0 Ethernet)

More details here raspberrypi/linux#1779

BTW, we've already discussed usage of 32bit linux kernel by default in our rpi3 setup (as ARM64 isn't officially supported for RaspberryPi) as a possible way to avoid facing such issues (and that are not somehow directly related to OP-TEE).

@jbech-linaro, right, no any updates since our last discussion. I think it will be better if I delete this branch for now to avoid any confusion in future.

from build.

I think it will be better if I delete this branch for now to avoid any confusion in future.

I agree, let's remove it. @jforissier , would you mind? I.e, delete the rpi3-4.8-optee branch in our kernel git?

from build.

I see a branch called electron752-rpi3-4.8-optee, is that the one? https://github.com/linaro-swg/linux/tree/electron752-rpi3-4.8-optee

from build.

Yes, that is the one. Now it feels like I'm a bit lazy here. I could have just deleted it myself, that would save you some time :)

from build.

@jbech-linaro np :) the branch is gone now.

from build.

Hi, I saw a cross reference to this topic. It's too bad you guys deleted the branch!

Anyway, I did some testing today and network boot is working just fine with the dwc_otg usb driver on the pi3 in arm64. The only trick I had to do was force nfs version 3 in the command line file. The default seems to be version 2 and it doesn't appear to be working correctly. I don't think this is RPI specific.

Anyway, here is the cmdline.txt that I used:
coherent_pool=4M console=tty1 root=/dev/nfs ro nfsroot=192.168.1.100:/srv/pi9,vers=3 ip=192.168.1.35

from build.

Just fyi if the maintainers are interested in bringing back the branch and nobody else has a backup, deleted branches can be revived by contacting [email protected].

from build.

Hi @Electron752,
Anyway, I've forked this branch before you've backported dwc_otg to 4.8 kernel

BTW, have you ever faced usb root host enumeration issues with backported dwc_otg on 4.8 kernel I've described in raspberrypi/linux#1779?

@msa2
Could you please post here the whole boot output from rpi3 dmesg or try to check if there is any mention of smsc95xx before an attempt of mounting rootfs via NFS? I looks like something like this:

[   155.149657] smsc95xx v1.0.4
[   155.149657] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:7c:97:f6

from build.

@igoropaniuk

No, I never saw issues quite like that. Usually, it either works or it doesn't. Not the random behavior you described.

I can only think of two things that could be causing that:

1. You are missing the RPI power management driver. I think the downstream source changed to this back around October or so. If you are missing it or missing the device tree nodes, the usb won't be powered correctly but you may sometimes see it work just because the firmware powered it for awhile to use the USB for booting.
2. You simply have a board with some loose connections and need to buy a new RPI.

When I forgot to have the vers=3 in the cmdline.txt, It would indeed detect the smsc95xx just fine. It would just fail after trying to mount the root filesystem several times. I'm thinking ver 2 doesn't work with 64 bit period and it isn't RPI specific.

from build.

I'm closing the ticket, either because it has already been answered or that it is no longer relevant or it could be lack of response from the author. Having that said, feel free to re-open the ticket if you have more to add to the ticket.

Also, we're about to step up the 4.14 kernel pretty soon, please see:
#269
OP-TEE/manifest#119
OP-TEE/optee_os#2394

from build.