Linaro / meta-qcom

OpenEmbedded/Yocto Project BSP layer for Qualcomm based platforms
MIT License
61 stars 70 forks source link

linux-yocto: add support for QCM6490 RB3 board #541

Closed adhudase closed 9 months ago

adhudase commented 9 months ago

Add necessary configuration and kernel changes to the linux-yocto recipe to enable support for Qualcomm QCM6490 RB3 board.

This enables boot to shell on QCM6490 RB3 board with initramfs.

lumag commented 9 months ago

For the patch-related comments. You don't have to fix issues that I pointed out for the patch contents. Please pass them to your kernel team. However please fix the patch formatting issues (tags, etc).

lumag commented 9 months ago
adhudase commented 9 months ago

Sorry, this seems getting dirty. Can we close this request and create new one? Thanks

adhudase commented 9 months ago

By subdirs, do you mean something like devicetree, bindings, drivers etc.? or something like - boards support, generic changes, temporary changes, debugging changes, etc. you mentioned earlier?

lumag commented 9 months ago

By subdirs, do you mean something like devicetree, bindings, drivers etc.? or something like - boards support, generic changes, temporary changes, debugging changes, etc. you mentioned earlier?

Yes. So that each group of patches is visually distinct.

adhudase commented 9 months ago

I've created these four subdirs - common-platform, idp, rb3gen2, generic-kernel-6.5

if this looks okay, I can push the patches.

lumag commented 9 months ago

generic-kernel-6.5

common-platform, idp, rb3gen2, generic-kernel-6.5

Well, generic-kernel-6.5 defintely doesn't look ok. Upgrading to 6.6 would cause unnecessary renames. I'd propose something simpler:

hashim-shiraz commented 9 months ago

Now that the series are sorted out, coud you pelase reorder into the sensible order:

  • generic-drivers
  • qcm6490-drivers
  • qcm6490-dtsi
  • qcm6490-board-dts
  • hacks

Can we have an alternate name for hacks which I guess would raise questions. How about workarounds (or any other name) ?

lumag commented 9 months ago

Can we have an alternate name for hacks which I guess would raise questions. How about workarounds (or any other name) ?

Sure, why not.