Well, like gman suggested last September, is there anything blocking a binary release/patch file from the source at the point in the history where it was working properly?
Hi,
We do SQA test cases on each release and the test cases focus on landscape mode. So for using Jetpack release, we recommend use landscape mode for developing the use-cases. Portrait mode is not well tested and it is possible to have potential issues.
I see.
Anyway, for testing purposes, is there anything blocking a binary release/patch file from the source at the point in the history where it was working properly?
Hi,
We donāt have binary/patch for portrait mode. Landscape mode is the default mode for Jetpack 4 and 5 releases. Would like to suggest use landscape mode for developing your use-case.
So the history for this is just lost or something?
Hi,
The information may not be accurate. My apology that we donāt correctly update the status. We can observe the issue on Jetpack 4.6 and 4.6.1. Since it is portrait mode, we would suggest use landscape mode to avoid the issue.
Are there any plans to make sure this gets fixed as was previously announced?
Hi,
Currently we donāt have plan to enable portrait mode in default releases. Would like to suggest use landscape mode for further development.
On the device in question, rotation is needed to get landscape mode, hince the need to fix the bug. The screen is a portrait screen with a resolution of 720x1280, the idea is to rotate it to get 1280x720. So suggesting landscape mode is basically saying the only screens we support are ones that are primarily landscape, and not portrait screens. This seems pretty stupid for a company that makes video cards primarily, especially when we (Cobalt and I) only work on the software side of this project, and have no control over the hardware at all. This is a known bug that was reported 3 years ago, and your devs/moderators said would be fixed, and was fixed, and now you are telling us, that it wont be fixed, and never was, and we need to change the hardware we develop around. That is crap, and you know it. What is the point in reporting things, when all you guys seem to do is make the problems worse with every update, and dont even bother trying to fix the issues reported. What is the point in this support thread, if you dont even attempt to help. If we had the driver code as well, we would have fixed this issue ourselves, but we are stuck waiting on you to fix it. Here is a suggestion, if you guys are truly done with the t210, release the damn code for the GPU userspace stuff, so we can fix the issues ourselvesā¦ But being nvidia, I dont have high expectations on that ever happening, it isnt like you guys have ever been like lets share our driver code in the opensource world, so people can improve on itā¦
Hi,
Thanks for the suggestion. There are various use-cases and we would like to cover them as most as possible. But this may take some time and it is possible certain use-cases are not working well on L4T releases. We are trying to have improvement on each release.
On Jetpack 5 releases for Xavier and Orin series, we are focusing on landscape mode. We will evaluate portrait mode and see if we can have better support for it in the future.