Yocto 2.0 rc1 poky: eac61f37e36099f74485dab398b57f3812826d17 image url: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.rc1/machines/mpc8315e-rdb/ in previous releases, eeprom can be found under root@mpc8315e-rdb:/sys/bus/i2c/devices/0-0050/eeprom in Yocto 2.0 rc1 build, this eeprom cannot be probed anymore.
What exactly are the implications of the reported issue? We are trying to determine the gravity of the issue and what is blocking.
(In reply to comment #1) > What exactly are the implications of the reported issue? We are trying to > determine the gravity of the issue and what is blocking. So far this doesn't block or affect any other features on this board. It's only that we have a test case to see if EEPROM is readable. https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=570
It appears the NEEDINFO has been answered.
seems that the issue still exists in YP 2.1_M2.rc1 master/3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c
This issue still exists on 2.1 M2 RC3 build. git rev: master/152914f2983c5d69001de1d46ce99547fa1e75fe
This has been fixed in the latest linux-yocto 4.4.
verified with yocto 2.1 M3 rc1 build