2022-07-08 19:17:49 |
Asmaa Mnebhi |
bug |
|
|
added bug |
2022-07-08 19:27:59 |
Asmaa Mnebhi |
description |
SRU Justification:
[Impact]
Support the I2C lock mechanism, otherwise there could be unexpected behavior when the i2c driver is accessed by several entities like the linux driver, ATF driver and UEFI driver.
[Fix]
* Support lock and unlock
* replace ioremap_nocache with ioremap
[Test Case]
* Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created
* check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course)
[Regression Potential]
Any of the test cases above could be impacted due to these changes. |
SRU Justification:
[Impact]
Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap since it is deprecated in later kernels.
[Fix]
* Support lock and unlock
* replace ioremap_nocache with ioremap
[Test Case]
* Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created
* check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course)
[Regression Potential]
Any of the test cases above could be impacted due to these changes. |
|
2022-07-19 21:00:44 |
Asmaa Mnebhi |
description |
SRU Justification:
[Impact]
Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Replace ioremap_cache with ioremap since it is deprecated in later kernels.
[Fix]
* Support lock and unlock
* replace ioremap_nocache with ioremap
[Test Case]
* Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created
* check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course)
[Regression Potential]
Any of the test cases above could be impacted due to these changes. |
SRU Justification:
[Impact]
Support the I2C lock mechanism, otherwise there could be unexpected behavior when an i2c bus is accessed by several entities like the linux driver, ATF driver and UEFI driver. Make sure to pick up the ATF/UEFI image to accompany this change
because at boot time ATF will ensure that the lock is released.
[Fix]
* Support lock and unlock
* replace ioremap_nocache with ioremap
[Test Case]
* Make sure the i2c-mlxbf.c driver is loaded and /dev/i2c-1 is created
* check that ipmitool from the BF->BMC and from the BMC->BF work (this only applies on boards with a BMC of course)
[Regression Potential]
Any of the test cases above could be impacted due to these changes.
Make sure you load the latest ATF/UEFI image to accompany this change. |
|
2022-08-11 15:08:30 |
Zachary Tahenakos |
linux-bluefield (Ubuntu): status |
New |
Fix Committed |
|
2022-08-23 08:21:28 |
Stefan Bader |
nominated for series |
|
Ubuntu Focal |
|
2022-08-23 08:21:28 |
Stefan Bader |
bug task added |
|
linux-bluefield (Ubuntu Focal) |
|
2022-08-23 08:21:36 |
Stefan Bader |
linux-bluefield (Ubuntu Focal): status |
New |
Fix Committed |
|
2022-08-23 08:21:40 |
Stefan Bader |
linux-bluefield (Ubuntu Focal): importance |
Undecided |
Medium |
|
2022-08-23 08:21:44 |
Stefan Bader |
linux-bluefield (Ubuntu): status |
Fix Committed |
Invalid |
|
2022-08-31 08:36:27 |
Launchpad Janitor |
linux-bluefield (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
2022-08-31 08:36:27 |
Launchpad Janitor |
cve linked |
|
2021-33061 |
|
2022-08-31 08:36:27 |
Launchpad Janitor |
cve linked |
|
2021-33656 |
|