On Mon Aug 25, 2014 at 14:22:57 +0200, Martin Schröder wrote:
Am 21.08.2014 um 23:03 schrieb Adam Lackorzynski:
I have some still hacky code on my disk which I think handles this. I
have to check and clean this up to commit it.
sounds promising! Even a dirty patch would help me a lot.
Ack,
Hi Adam,
Am 21.08.2014 um 23:03 schrieb Adam Lackorzynski:
I have some still hacky code on my disk which I think handles this. I
have to check and clean this up to commit it.
sounds promising! Even a dirty patch would help me a lot.
Best regards,
Martin
Hi Adam,
Am 19.08.2014 um 00:13 schrieb Adam Lackorzynski:
I am using the imx28-evk.dts where I replaced the model and compatible
line by what I found in simple.dts.
Ok, that's one thing to do. Does Linux say that it uses a DT? Like:
[0.00] Machine model: L4Linux (DT)
Yes it does:
Hi Adam,
I tracked the problem down to l4linux/arch/l4/kernel/arch-arm/setup.c:
In static customize_machine(void) either machine_desc-init_machine() is
called and the static/generic platform devices are added (and the DT
disregarded). If init_machine is not set the DT is parsed instead by
Am 13.08.2014 um 22:40 schrieb Adam Lackorzynski:
So it worked before using DTBs? Some config/setting issue?
Yes, both network of my imx28 worked withou DTB. I is some config issue:
After searching a while, I am sure that the Device Tree is not used in
my configuration at all. As I wrote
On Mon Aug 18, 2014 at 19:38:54 +0200, Martin Schröder wrote:
Am 13.08.2014 um 22:40 schrieb Adam Lackorzynski:
So it worked before using DTBs? Some config/setting issue?
Yes, both network of my imx28 worked withou DTB. I is some config issue:
After searching a while, I am sure that
On Tue Aug 12, 2014 at 19:54:37 +0200, Martin Schröder wrote:
Hi Adam,
Am 11.08.2014 um 23:41 schrieb Adam Lackorzynski:
So l4x_load_dtb(main.c) is fine, but then something else in setup_arch goes
wrong. The dtb s stolen from some other linux build, so maybe the dtb is
wrong.
Hmm, you
Hi Adam,
Am 11.08.2014 um 23:41 schrieb Adam Lackorzynski:
So l4x_load_dtb(main.c) is fine, but then something else in setup_arch goes
wrong. The dtb s stolen from some other linux build, so maybe the dtb is
wrong.
Hmm, you need to tune the DT a bit I think. Did you take out the GIC,
timer
Hi Adam,
Am 05.08.2014 um 22:44 schrieb Adam Lackorzynski:
Appending the DTB won't work with L4Linux. However, you can just use
l4x_dtb=rom/your.dtb on the cmdline.
it does not work for me. With a provided dtb it stops here:
l4linux | l4x_register_pointer_section: addr = 0200 size =
Hi Martin,
On Mon Aug 11, 2014 at 19:13:51 +0200, Martin Schröder wrote:
Am 05.08.2014 um 22:44 schrieb Adam Lackorzynski:
Appending the DTB won't work with L4Linux. However, you can just use
l4x_dtb=rom/your.dtb on the cmdline.
it does not work for me. With a provided dtb it stops here:
On my board I want to add support for GPIO. The relevant drivers rely on
the pinctrl configuration stored in a Device Tree Blob.
So I exposed the memory regions and IRQs to the l4linux task, enabled
CONFIG_ARM_APPEND_DTB=y, CONFIG_ARM_DTB_COMPAT=y, CONFIG_USE_OF=y,
compiled the dts (from a
11 matches
Mail list logo