Re: AM335x, early printk

2013-08-20 Thread Afzal Mohammed
Hi Sebastian,

On Tuesday 20 August 2013 03:02 PM, Lokesh Vutla wrote:

>> Yes. I do not see the decompress messages but I have an early console
>> later on. Unfortunately it stops now right at the serial core:
>>
>> |pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
>> |Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

> I guess you are missing the following series from Rajendra. 
> 
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg92515.html

I think Lokesh's suggestion is more likely to help your case than mine.

Regards
Afzal

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: AM335x, early printk

2013-08-20 Thread Lokesh Vutla
Hi Sebastian,

On Monday 19 August 2013 06:07 PM, Sebastian Andrzej Siewior wrote:
> On 08/19/2013 02:27 PM, Jean Pihet wrote:
>> Hi!
> 
> Hi Jean,
> 
>> You need to add 'earlyprintk' in the kernel command line, given (I
>> suppose) by U-Boot.
> 
> Ah, good hint.
> 
>>
>> I hope this helps!
> 
> Yes. I do not see the decompress messages but I have an early console
> later on. Unfortunately it stops now right at the serial core:
> 
> |pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
> |Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
I guess you are missing the following series from Rajendra. 

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg92515.html

Thanks and regards,
Lokesh
> 
>>
>> Jean
> 
> Sebastian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: AM335x, early printk

2013-08-19 Thread Afzal Mohammed
Hi Sebastian,

On Monday 19 August 2013 06:07 PM, Sebastian Andrzej Siewior wrote:

> Yes. I do not see the decompress messages but I have an early console
> later on. Unfortunately it stops now right at the serial core:
> 
> |pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
> |Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

I vaguely remember facing a similar issue on it's yet to be born sibling
while trying to woke it up in the womb, see if placing dtb at a
different location helps (probably so that images won't get corrupted)

Regards
Afzal
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: AM335x, early printk

2013-08-19 Thread Sebastian Andrzej Siewior
On 08/19/2013 02:27 PM, Jean Pihet wrote:
> Hi!

Hi Jean,

> You need to add 'earlyprintk' in the kernel command line, given (I
> suppose) by U-Boot.

Ah, good hint.

> 
> I hope this helps!

Yes. I do not see the decompress messages but I have an early console
later on. Unfortunately it stops now right at the serial core:

|pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
|Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

> 
> Jean

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: AM335x, early printk

2013-08-19 Thread Jean Pihet
Hi!

You need to add 'earlyprintk' in the kernel command line, given (I
suppose) by U-Boot.

I hope this helps!

Jean

On Mon, Aug 19, 2013 at 1:21 PM, Sebastian Andrzej Siewior
 wrote:
> Hi,
>
> I activated:
> [*] Kernel low-level debugging functions
>  Kernel low-level debugging port (Kernel low-level debugging
>   messages via OMAP2PLUS UART)
>  Low-level debug console UART (AM33XX UART1)
> [*] Early printk
>
> and booted my am335x-evm.
> I haven't seen any "early" output in the decompressor or during the
> kernel boot. I believe that all I saw is just regular ttyO0 output.
> I saw also:
> |44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
> |console [ttyO0] enabled
> and I would also except the bootconsole (if any) to be deactivated here.
>
> What am I missing?
>
> Sebastian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


AM335x, early printk

2013-08-19 Thread Sebastian Andrzej Siewior
Hi,

I activated:
[*] Kernel low-level debugging functions
 Kernel low-level debugging port (Kernel low-level debugging
  messages via OMAP2PLUS UART)
 Low-level debug console UART (AM33XX UART1)
[*] Early printk

and booted my am335x-evm.
I haven't seen any "early" output in the decompressor or during the
kernel boot. I believe that all I saw is just regular ttyO0 output.
I saw also:
|44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
|console [ttyO0] enabled
and I would also except the bootconsole (if any) to be deactivated here.

What am I missing?

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html