Hi
During the call you mentioned that SBBR had some defined values for console.
I can only find that the _HID="ARMH0011" identifies a SBSA com port but I
don't find any standard object path that would point to the UART to use.
let's assume:
Device (COM0)
{
Name (_HID, "ARMH0011") // _HID: Hardware ID
Name (_UID, Zero) // _UID: Unique ID
Name (_CRS, ResourceTemplate () // _CRS: Current Resource
Settings
{
Memory32Fixed (ReadWrite,
0x09000000, // Address Base
0x00001000, // Address Length
)
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive,
,, )
{
0x00000021,
}
})
Name (_ADR, 0x09000000) // _ADR: Address
}
Device (COM1)
{
Name (_HID, "ARMH0011") // _HID: Hardware ID
Name (_UID, One) // _UID: Unique ID
Name (_CRS, ResourceTemplate () // _CRS: Current Resource
Settings
{
Memory32Fixed (ReadWrite,
0x09002000, // Address Base
0x00001000, // Address Length
)
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive,
,, )
{
0x00000022,
}
})
Name (_ADR, 0x09002000) // _ADR: Address
}
Which port to use as a console?
by definition we could say that \_SB_.COM0 is the port to use.
Or we could define \_SB_.SOUT as a reference object to any of the defined
UARTs.
Cheers
FF
On Mon, 18 Jan 2021 at 16:32, Grant Likely <[email protected]> wrote:
>
>
> On 17/01/2021 15:01, François Ozog wrote:
> > Hi Grant
> >
> > I’d like EBBR to specify a solution to identify the default serial
> > console out of existing optional indications.
>
> Hi Francois,
>
> This is a good topic. EBBR starts from the assumption that whether ACPI
> or DT is used for the system description, the data will follow the
> requirements of the technology. For ACPI I don't think we need to add
> any language, but it would be worthwhile to require stdout-path is
> specified in the DT. Do you want to propose some language?
>
> > On DT systems , we shall state that /chosen/stdout-path must point to a
> > valid path.
> >
> > On ACPI, we may get the info form \_SB_.COM0 @ DSDT or specify we will
> > get the info from SPCR table. >
> > Regardless of the method , this is required to just boot and do not have
> > to care about clumsy command lines with early_console or console
> parameters.
>
> Agree. Mucking with the commandline should not be required.
>
>
> > I like this topic be added to the agenda ?
>
> yes. Can you also add an issue to track this topic please?
>
> g.
>
> > Le sam. 16 janv. 2021 à 13:59, Grant Likely <[email protected]
> > <mailto:[email protected]>> a écrit :
> >
> > Hi all,
> >
> > Next EBBR meeting is ON for Monday, 18 Jan 2021 at 16:00 GMT. I think
> > there is quite a backlog of items to discuss. Here's what I've got
> for
> > the agenda so far:
> >
> > * Update on specific required protocols
> > * https://github.com/ARM-software/ebbr/issues/60
> > <https://github.com/ARM-software/ebbr/issues/60>
> > * https://github.com/ARM-software/ebbr/issues/61
> > <https://github.com/ARM-software/ebbr/issues/61>
> > * https://github.com/ARM-software/ebbr/issues/64
> > <https://github.com/ARM-software/ebbr/issues/64>
> > * Firmware update requirements
> > * https://github.com/ARM-software/ebbr/issues/69
> > <https://github.com/ARM-software/ebbr/issues/69>
> > * DT fixup protocol proposal
> > * https://github.com/U-Boot-EFI/EFI_DT_FIXUP_PROTOCOL
> > <https://github.com/U-Boot-EFI/EFI_DT_FIXUP_PROTOCOL>
> > * https://github.com/ARM-software/ebbr/issues/68
> > <https://github.com/ARM-software/ebbr/issues/68>
> > * Other business
> >
> > If you would like to discuss anything else, please reply to this
> email.
> >
> > Dial in details are here:
> >
> > ---
> >
> > Grant Likely is inviting you to a scheduled Zoom meeting.
> >
> >
> >
> > Topic: EBBR Biweekly
> >
> > Time: 18 Jan 2021, 16:00-17:00 GMT
> >
> >
> > Join Zoom Meeting
> >
> >
> https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09
> > <
> https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09>
> >
> >
> >
> > Meeting ID: 920 8136 5511
> >
> > Passcode: 490324
> >
> > One tap mobile
> >
> > +14086380968,,92081365511#,,,,*490324# US (San Jose)
> >
> > +16465189805,,92081365511#,,,,*490324# US (New York)
> >
> >
> >
> > Dial by your location
> >
> > +1 408 638 0968 US (San Jose)
> >
> > +1 646 518 9805 US (New York)
> >
> > +1 346 248 7799 US (Houston)
> >
> > Meeting ID: 920 8136 5511
> >
> > Passcode: 490324
> >
> > Find your local number: https://armltd.zoom.us/u/aelJgr9ZAW
> > <https://armltd.zoom.us/u/aelJgr9ZAW>
> >
> >
> > _______________________________________________
> > boot-architecture mailing list
> > [email protected]
> > <mailto:[email protected]>
> > https://lists.linaro.org/mailman/listinfo/boot-architecture
> > <https://lists.linaro.org/mailman/listinfo/boot-architecture>
> >
> > --
> >
> > François-Frédéric Ozog | /Director Linaro Edge & Fog Computing Group/
> > T: +33.67221.6485
> > [email protected] <mailto:[email protected]>
> | Skype: ffozog
> >
> >
>
--
François-Frédéric Ozog | *Director Linaro Edge & Fog Computing Group*
T: +33.67221.6485
[email protected] | Skype: ffozog
_______________________________________________
boot-architecture mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/boot-architecture
