[Treble-Enabled Device Guides, News, & Discussion] tripLr:
Umm, no

Trebel forces standards of communication between drivers and operating system., And where the drivers are located in which partition,

And supports boot a, boot b, so if the update to boot b failed, boot a is fallback so theoretically it will be much harder to brick your device.

So let's assume a simple USB hardware driver in the side of your phone.

You plug in a USB Power and data cable to your phone.

An electric signal is sent on a wire to a chip.

The chip sends a code to the hardware interrupt

The kernel is constantly looking for things to do and scanning in order, driver a, driver b driver c, etc, and applying rules ( programming ) if x then n

Now a piece of code is constantly listening for a change in a hardware interrupt. ( Hardware driver )

The hardware driver sends a ( hey look at this ) to the cpu, the cpu reads the code ( what do I do if I see ”look at this")

And executes ( so that )

Let's say in the binary code

Qualcomm driver says OnUsbPlugIn send WakeUpBit to CPU hardware address 123abc

But

Samsung says ( hey let's run a security check before we do that ) hardware address 123ab1

But handset manufacturer xomami says ( we don't care, but let's send an update to some Chinese server that this device was hot plugged ) 123ab2

But now Verizon, AT+T , and TMobile all use the 3 different above , and compile a superduperCrapola driver for every different country they sell their handset.

Same chipset , many multiple different drivers

But now with Trebel, Google says no matter who makes the crap

OnUsbPlugIn must send 123abc to location TrebelOnUSBPlugin or You won't get our operating system and updates.

Forced standards ( free tools from Google to make your crapware drivers compliant )

So as an example..

So driver USBx.nougat just has to be pointed to Trebel.USB

I haven't coded this deep since Pascal, but the principal is the same

I think Google has a virtual Android Device , and there is a Trebel certification process.

So somewhere in the process ...

Qualcomm or whoever must release some basic hardware drivers source code or standards on it's IO specifications?

Also I saw a comment about partitions not being possible

You can partition any memory thing with any partition. Even virtual.

So yes it is possible to install Trebel partitions on my Note4 Verizon. It will be a brick, but it Can be done.

This boils down to

If Trebel has universal driver interfaces

So any ASOP ROM can run on any Trebel Device...

Could there ( not is ) be a universal Bootloader?

If the driver partition is separate

And the rexovery partition is separate

And the kernel and ROM are separate

Then we need to backbuild a universal Trebel to any device

Is a

Bootloader

And driver code

Now TWRP is as close to a universal recovery partition as we can get

It has a small operating system, ( probably Linux based ) and drivers built in.

The boot loader in any phone must provide some basic functions. It too must have some basic operating system as well. It will most likely be an EEPROM

On power up read hardware location x to y IN EEPROM

Copy x to y to PHYSICAL RAM memory location a to b

Excecute instruction is a to b

If no hardware interrupt load kernel and ROM

If hardware interrupt load recovery partition into memory and excute

If USB plug in display battery icon

If download display Android download screen

If bootloader lock bit set, deny write access

So all the Bootloaders do the same functions

These are all based on a physical program residing on a selectively flashable memory somewhere

Same as the BIOS on a Intel board.

Oh well I'm beat

Think more later