mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Next step to enable DT support for at91sam9263ek?
Date: Mon, 10 Jul 2017 11:14:22 +0200	[thread overview]
Message-ID: <1499678062.2924.10.camel@pengutronix.de> (raw)
In-Reply-To: <20170707221759.GA29219@ravnborg.org>

Hi Sam,

Am Samstag, den 08.07.2017, 00:17 +0200 schrieb Sam Ravnborg:
> Hi all.
> 
> I have now spent some time trying to dive into how to enable DT
> support for at91sam9263ek - but so far with only limited success.
> I have copied the device tree from the kernel and included
> the tree in the build. This step was simple.
> 
> I also updated the ENTRY_FUNCTION to take a pointer to the ftd.
> Also simple.
> 
> There was a few build issues that I then had to fix.
> But when running the resulting barebox nothing was printed to
> the console.
> I ended up dropping following from the build:
> arch/arm/boards/at91sam9263ek/init.c
> arch/arm/mach-at91/at91sam9263.c
> arch/arm/mach-at91/at91sam9263_devices.c
> 
> Thein I got following output when booting:
> 
> barebox 2017.07.0-00082-g265d9e416-dirty #27 Sat Jul 8 00:00:54 CEST 2017
> 
> 
> Board: Atmel at91sam9263ek
> fset: 10000000
> Main crystal frequency not set, using approximate value
> AT91: Detected soc type: at91sam9263
> AT91: Detected soc subtype: Unknown
> comparing usart with usart
> Main crystal frequency not set, using approximate value
> comparing usart with usart
> Main crystal frequency not set, using approximate value
> gpio-at91 fffff200.gpio: AT91 gpio driver registered
> gpio-at91 fffff400.gpio: AT91 gpio driver registered
> gpio-at91 fffff600.gpio: AT91 gpio driver registered
> gpio-at91 fffff800.gpio: AT91 gpio driver registered
> gpio-at91 fffffa00.gpio: AT91 gpio driver registered
> pinctrl-at91 pinctrl.2: AT91 pinctrl registered
> comparing macb_clk with hclk
> comparing macb_clk with pclk
> macb fffbc000.ethernet: no macb_clk
> macb fffbc000.ethernet: probe failed: Invalid argument
> of_get_named_gpio_flags: cannot parse cd-gpios property: -2
> comparing mci_clk with mci_clk
> Main crystal frequency not set, using approximate value
> atmel_mci fff80000.mmc: version: 0x210
> atmel_mci fff80000.mmc: registered as fff80000.mmc
> malloc space: 0x23afad80 -> 0x23efad7f (size 4 MiB)
> environment load /dev/env0: No such file or directory
> Maybe you have to create the partition.
> running /env/bin/init...
> \e[?25h
> Hit any key to stop autoboot:    1
> 
> This does not look entirely correct...
> 
> Right now I am a bit stuck for what would be next step - any hints
> would be highly appreciated.

Probably a lot of the devices present on the AT91 boards have driver
with no proper DT support in Barebox, so you might need to extend some
of them.

Also if the boards have any specific board code, you need to convert
that to initcalls guarded by the board DT compatible.

HTH,
Lucas


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

      reply	other threads:[~2017-07-10  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 22:17 Sam Ravnborg
2017-07-10  9:14 ` Lucas Stach [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1499678062.2924.10.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox