On 12/9/22 4:18 PM, Sapp, Randolph wrote:
On Wed, Dec 7 2022 at 12:48:00 PM -0600, Andrew Davis <[email protected]> wrote:
Since the UM driver now RDEPENDS on the KM, could we also drop this
last line everywhere?

Nope, we still need the one preferred provider line to indicate that rogue 
graphics are present. Now this could be replaced by a rogue-graphics machine 
feature instead if that's preferable, but something will need to signal the 
mesa switch.


New machine feature sounds like the better route since it changes the content 
of a package.
Using PREFERRED_PROVIDER for that doesn't seem right.

On Wed, Dec 7 2022 at 12:48:00 PM -0600, Andrew Davis <[email protected]> wrote:
Bash? Are we sure we need that?

Yes. The System V init script still needs it. Now could we look at removing 
that init script? Sure, so long as the device probe still works. What is 
actually taking care of that right now? It's not udev is it?


The module/device probe is automatic now. At least for SGX that script exists 
only
to run the single command "pvrsrvctl --start --no-module" which loads some 
microcode.
We can have yocto build that service for us to run the command, IIRC it will 
make
it into a systemd or sysv service for us based on what kinda distro we are 
building.

On Wed, Dec 7 2022 at 12:48:00 PM -0600, Andrew Davis <[email protected]> wrote:
"ldflags already-stripped" should be the only skips we still need.

Dev-so is required because of some of the symbolic links that are shipped. I'm 
fine dropping arch unless that breaks something.



Ah, think that is /usr/lib/dri/pvr_dri.so, odd name, but yeah that skip can
stay then. Lets try to drop "arch" at least.

Andrew
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15478): 
https://lists.yoctoproject.org/g/meta-ti/message/15478
Mute This Topic: https://lists.yoctoproject.org/mt/95498459/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to