Re: [PATCH 1/3] arm: imx6: move imx6_init_lowlevel to single initcall

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hmm, I have removed the imx6_init_lowlevel() from my (out-of-tree)
board.c file. Still I get this warning:

__request_region: 0x10000000:0x4fffffff conflicts with 0x10000000:0x4fffffff

Could this be related to your patchset?  In the log below, the text "
ahs2_postcore_init, after barebox_set_hostname()" is a printf()
directly before the return of that function.

Switch to console [cs0]
in ahs2_postcore_init
ahs2_postcore_init, after barebox_set_hostname()
detected i.MX6 Quad revision 1.2
Switch to console [cs0]
in ahs2_postcore_init
ahs2_postcore_init, after barebox_set_hostname()
detected i.MX6 Quad revision 1.2
__request_region: 0x10000000:0x4fffffff conflicts with 0x10000000:0x4fffffff
mdio_bus: miibus0: probed
m25p80 spiflash@00: n25q512 (65536 Kbytes)
imx-esdhc 2194000.usdhc: registered as 2194000.usdhc
imx-esdhc 219c000.usdhc: registered as 219c000.usdhc


When I remove

    memory {
      reg = <0x10000000 0x40000000>;
    };

from my DTS, then the error vanishes, but how could some other part in
barebox possible know how much memory my board has?

_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox




[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux