-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding revpi connect 4 support #1078
Conversation
Can one of the admins verify this patch? |
ff3d192
to
6f34e40
Compare
a7c27d8
to
883e7f7
Compare
@floion just spoke with Kenna last week. We will ship you the hardware (afaik to a partner in UK). If it will help I can reroute the shipment to you. Just let me know. |
Thanks @wickywaka we'll review it. |
layers/meta-balena-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bbappend
Outdated
Show resolved
Hide resolved
@floion I think this is ready for testing. Anyway we can get this merged quickly so that we can continue with testing our devices. |
52525b4
to
d6846c6
Compare
layers/meta-balena-raspberrypi/conf/machine/revpi-connect-4.conf
Outdated
Show resolved
Hide resolved
layers/meta-balena-raspberrypi/conf/machine/revpi-connect-4.conf
Outdated
Show resolved
Hide resolved
layers/meta-balena-raspberrypi/conf/machine/revpi-connect-4.conf
Outdated
Show resolved
Hide resolved
layers/meta-balena-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bbappend
Outdated
Show resolved
Hide resolved
layers/meta-balena-raspberrypi/recipes-kernel/linux-kunbus/linux-kunbus_%.bbappend
Outdated
Show resolved
Hide resolved
For now I will just try to create a working with changes proposed by @nbuchwitz and once we have a working image, then I will squash all the commits. @floion Why don't you guys squash the commits automatically from a PR (may be with a template message) so that all the PR is just one commit. That way the contributor does not have to do all the rebases manually and can focus on final result. |
518079d
to
2a50266
Compare
@nbuchwitz @floion ready for review again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So far I can check LGTM
@resin-jenkins test this please |
Some of the tests seems to be failing. Can you check the logs and see what is missing? |
@resin-jenkins test this please |
1 similar comment
@resin-jenkins test this please |
@wickywaka the failures are not related to this PR |
This adds supports for revpi-connect-4. These changes were done by looking at the PR for the revpi-connect-s. Changelog-entry: Added support for revpi-connect-4 device Signed-off-by: Waqar Rashid <[email protected]>
Head branch was pushed to by a user without write access
2a50266
to
2cfad44
Compare
@resin-jenkins test this please |
@resin-jenkins test this please |
@floion Can you see why are these tests failing? Is there a way for us to run these tests so that we can reduce the iteration time. |
@wickywaka looking into #1083. Once that is merged we can release this device type. The failure seem to be related to flaky network issues. The tests need to be ran on the automated test rig, so it would not help if you run the tests on your side. |
In this PR we are adding support for revpi-connect-4. This is very similar to what we did for the revpi-connect-s here #1016
@floion is there a way you can run the tests for this? This seems to be working on our devices but we are happy to fix issues that might arise during testing.
@nbuchwitz would be great if you can have a look at this.