From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM CONFIG_OF_CONTROL status
Date: Wed, 27 Jun 2012 06:58:39 -0700 [thread overview]
Message-ID: <CAPnjgZ28xWA34-c1ReiDp6xnPD2pBVOaUL33UfmY_heA422S1w@mail.gmail.com> (raw)
In-Reply-To: <4FEAD263.2020707@monstr.eu>
Hi,
On Wed, Jun 27, 2012 at 2:29 AM, Michal Simek <monstr@monstr.eu> wrote:
> Hi,
>
> can you please update me about current state of CONFIG_OF_CONTROL for ARM?
> Are there any other archs/boards which will use this option?
>
Or any other git repo out of mainline u-boot?
>
Exynos is in progress - development is happening in the Chromium tree and
being upstreamed in chunks (although no fdt patches have been sent yet).
>
> Has someone tried to look for devices based on compatible property?
> I see that in usb driver it is based on aliases which is not the best
> solution.
>
U-Boot doesn't yet have a device model which would allow this in the
general case. For now, drivers look for their own compatible nodes. This
works well enough until we have a device model.
There are other limitations also - for example USB supports only a single
controller type working at one time (a restriction we may need to look at
to support USB2 and USB3 together). So even if two USB drivers decided that
they both found compatible nodes, only one of them could operate. So for
now aliases provide just an ordering, nothing else.
Regards,
Simon
>
> Thanks,
> Michal
>
> --
> Michal Simek, Ing. (M.Eng)
> w: www.monstr.eu p: +42-0-721842854
> Maintainer of Linux kernel 2.6 Microblaze Linux -
> http://www.monstr.eu/fdt/
> Microblaze U-BOOT custodian
>
next prev parent reply other threads:[~2012-06-27 13:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 9:29 [U-Boot] ARM CONFIG_OF_CONTROL status Michal Simek
2012-06-27 13:58 ` Simon Glass [this message]
2012-06-27 14:35 ` Michal Simek
2012-06-28 1:10 ` Simon Glass
2012-06-28 5:50 ` Michal Simek
2012-06-28 5:57 ` Simon Glass
2012-06-28 6:49 ` Michal Simek
2012-06-29 2:32 ` Simon Glass
2012-06-29 8:18 ` Michal Simek
2012-06-29 20:22 ` Stephan Linz
2012-07-02 5:43 ` Michal Simek
2012-07-03 19:21 ` Simon Glass
2012-07-03 20:22 ` Stephan Linz
2012-07-04 1:48 ` Simon Glass
2012-07-04 6:13 ` Michal Simek
2012-07-04 6:24 ` Michal Simek
2012-07-04 20:27 ` Stephan Linz
2012-07-09 7:58 ` Michal Simek
2012-07-03 19:38 ` Stephan Linz
2012-07-03 19:05 ` Simon Glass
2012-07-04 6:02 ` Michal Simek
2012-07-05 15:34 ` Stephen Warren
2012-07-09 7:59 ` Michal Simek
2012-07-03 9:21 ` Michal Simek
2012-07-03 19:07 ` Simon Glass
2012-07-04 5:46 ` Michal Simek
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=CAPnjgZ28xWA34-c1ReiDp6xnPD2pBVOaUL33UfmY_heA422S1w@mail.gmail.com \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.