OE4T / meta-tegra

BSP layer for NVIDIA Jetson platforms, based on L4T
MIT License
407 stars 224 forks source link

Plans to support L4T 31.0.1 #106

Closed BassemMohsen closed 5 years ago

BassemMohsen commented 6 years ago

Hello Matt

Do you have any plans/roadmaps to support the new release for L4T 31.0.1? TBH, I'm more interested in some new kernel features to use AppArmor.

Also, If you want. I might be able to help some Pull Requests for that

madisongh commented 6 years ago

I've started looking at 31.0.1 and will probably use it to start putting together the metadata for Xavier support (my Xavier is due to arrive today). I probably won't pull any 31.0.1-based recipes into any of the main branches unless there is a long delay until L4T 32 comes out (which should support both Xavier and TX2, and will have the kernel sources in git, rather than just a tarball).

Even though 31 looks like it would actually support both Xavier and TX2, NVIDIA is only advertising support for Xavier with that version, so I'd be careful about trying to use it for anything else.

BassemMohsen commented 6 years ago

my Xavier is due to arrive today

well, Congratulations ;)

Even though 31 looks like it would actually support both Xavier and TX2

I tried yesterday their pre-built rootfs from L4T 31 on the TX2 and worked nicely so far. so, I think 31 is already supporting TX2.

Anyway, Thanks for sharing your plans :+1:

madisongh commented 5 years ago

Support for L4T 31.0.1/JetPack 4.1 Developer Preview is available on the wip-thud-l4t-31.0.1 branch. There are still a couple of outstanding issues, but basic support is there for both Xavier and TX2. NVIDIA still says that TX2 isn't actually supported with 31.0.1, so be careful.

mwcoop commented 5 years ago

Does this build core-image-sato? My first attempts with image definitions from sumo is failing with many missing dependencies including wireless-tools, libxext, various X11 items, and several meta-tegra items. I imagine thud made a few changes that are messing me up. Any key points would be great.

madisongh commented 5 years ago

Yes, both core-image-sato and core-image-weston. I just tested builds against the latest OE-Core thud changes that went in a couple of days ago and found a couple of minor issues in meta-tegra (now fixed), but nothing major.

mwcoop commented 5 years ago

Any chance you can provide sample bblayers and local config files?

On Jan 10, 2019, at 4:32 AM, Matt Madison notifications@github.com wrote:

Yes, both core-image-sato and core-image-weston. I just tested builds against the latest OE-Core thud changes that went in a couple of days ago and found a couple of minor issues in meta-tegra (now fixed), but nothing major.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/madisongh/meta-tegra/issues/106#issuecomment-453080251, or mute the thread https://github.com/notifications/unsubscribe-auth/AUXTFSIgATHXpywrnUi5S5neK23RALCaks5vBzLIgaJpZM4WtyWt.

madisongh commented 5 years ago

My test distro setup is here. I haven't updated the thud-l4t-r31.1.0 branch there for a couple of weeks, but you can also just use the thud branch and in your workspace:

Then just source the setup-env script at the top level to create a build directory and populate it with the necessary config files, update conf/local.conf to set MACHINE to what you want, and you should be able to build either of those images. Be warned that the builds (for TX1, TX2, or Xavier) could take a while because I add some packages that pull in opencv. You can tweak the bbappends I have for core-image-weston and packagegroup-core-x11-sato to trim some of those out (in particular, tegra-mmapi-samples) to cut down on build times.

madisongh commented 5 years ago

I have just updated the thud-l4t-r31.1.0 branch in the test distro to bring all the layers up to date.

mwcoop commented 5 years ago

Looking at the test-distro project, I'm just curious what image types you are working with. In my particular case, I basically want to build a complete image with all Tegra tools, samples, development headers/docs, etc. What image types get me close to this. For example, do any images include the VisionWorks samples? It looks like core-image-weston may get close to what I want. Is that correct.

madisongh commented 5 years ago

I work with core-image-weston and core-image-sato.