On 8/9/18 4:02 AM, Konstantin Belousov wrote:
> On Thu, Aug 09, 2018 at 10:26:06AM +0100, Johannes Lundberg wrote:
>> On Thu, Aug 9, 2018 at 9:29 AM Konstantin Belousov
>> wrote:
>>
>>> On Thu, Aug 09, 2018 at 08:54:31AM +0100, Johannes Lundberg wrote:
Hi
So I believe the reason
On Thu, Aug 09, 2018 at 10:26:06AM +0100, Johannes Lundberg wrote:
> On Thu, Aug 9, 2018 at 9:29 AM Konstantin Belousov
> wrote:
>
> > On Thu, Aug 09, 2018 at 08:54:31AM +0100, Johannes Lundberg wrote:
> > > Hi
> > >
> > > So I believe the reason I'm not seeing and printf output in dmesg is that
On Thu, Aug 9, 2018 at 9:29 AM Konstantin Belousov
wrote:
> On Thu, Aug 09, 2018 at 08:54:31AM +0100, Johannes Lundberg wrote:
> > Hi
> >
> > So I believe the reason I'm not seeing and printf output in dmesg is that
> > it is too early in some functions.
> > For example
> > machdep.s
> >
On Thu, Aug 09, 2018 at 08:54:31AM +0100, Johannes Lundberg wrote:
> Hi
>
> So I believe the reason I'm not seeing and printf output in dmesg is that
> it is too early in some functions.
> For example
> machdep.s
> getmemsize()
> add_efi_map_entries()
> etc
>
> However, these functions do
Hi
So I believe the reason I'm not seeing and printf output in dmesg is that
it is too early in some functions.
For example
machdep.s
getmemsize()
add_efi_map_entries()
etc
However, these functions do contain debug printf statements so if they're
logging to somewhere, where/how can I see