On Tue, Jan 10, 2023 at 5:29 PM Bobby Eshleman wrote:
>
>
>
> On Mon, Jan 9, 2023 at 4:28 PM Alistair Francis wrote:
>>
>> On Tue, Jan 10, 2023 at 1:47 AM Oleksii Kurochko
>> wrote:
>> >
>> > The patch introduces a basic stuff of early_printk functionality
>> > which will be enough to print 'hel
On Mon, Jan 9, 2023 at 4:28 PM Alistair Francis
wrote:
> On Tue, Jan 10, 2023 at 1:47 AM Oleksii Kurochko
> wrote:
> >
> > The patch introduces a basic stuff of early_printk functionality
> > which will be enough to print 'hello from C environment".
> > early_printk() function was changed in com
On Tue, Jan 10, 2023 at 1:47 AM Oleksii Kurochko
wrote:
>
> The patch introduces a basic stuff of early_printk functionality
> which will be enough to print 'hello from C environment".
> early_printk() function was changed in comparison with original as
> common isn't being built now so there is n
On 09.01.2023 16:46, Oleksii Kurochko wrote:
> --- a/xen/arch/riscv/Kconfig.debug
> +++ b/xen/arch/riscv/Kconfig.debug
> @@ -0,0 +1,7 @@
> +config EARLY_PRINTK
> +bool "Enable early printk config"
Nit: Stray "config" in the prompt text.
Jan
Hi,
On 09/01/2023 15:46, Oleksii Kurochko wrote:
The patch introduces a basic stuff of early_printk functionality
which will be enough to print 'hello from C environment".
early_printk() function was changed in comparison with original as
common isn't being built now so there is no vscnprintf.
The patch introduces a basic stuff of early_printk functionality
which will be enough to print 'hello from C environment".
early_printk() function was changed in comparison with original as
common isn't being built now so there is no vscnprintf.
Because printk() relies on a serial driver (like the
