All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Linz <linz@li-pro.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM CONFIG_OF_CONTROL status
Date: Wed, 04 Jul 2012 22:27:05 +0200	[thread overview]
Message-ID: <1341433625.2722.27.camel@keto> (raw)
In-Reply-To: <4FF3E194.4000801@monstr.eu>

Am Mittwoch, den 04.07.2012, 08:24 +0200 schrieb Michal Simek: 
> On 07/03/2012 10:22 PM, Stephan Linz wrote:
> > Am Dienstag, den 03.07.2012, 12:21 -0700 schrieb Simon Glass:
> >> Hi,
> >>
> >> On Sun, Jul 1, 2012 at 10:43 PM, Michal Simek<monstr@monstr.eu>  wrote:
> >>
> >>> 2012/6/29 Stephan Linz<linz@li-pro.net>:
> >>>> Am Freitag, den 29.06.2012, 10:18 +0200 schrieb Michal Simek:
> >>>>> On 06/29/2012 04:32 AM, Simon Glass wrote:
> >>>>>> Hi,
> >>>>>>
> >>>>>> --snip--
> >>>>>
> >>>>> 
> >>>
> >>
> >> Well there is no inherent problem with having multiple include files,
> >> except that it is hard to support with the old dtc when there are in
> >> different subdirs.
> >>
> >> As a workaround, how about putting the include files in the
> >> board/vendor/dts subdir as well for now?
> >
> > Hi,
> >
> > good idea -- but they cannot be used directly. The substitution variable
> > ARCH_CPU_DTS is already reserved for dtsi in arch/cpu. The Microblaze
> > architecture needs a board specific dts onyl. That's why I think the new
> > substitution variable BOARD_DTS can be a option to solve the CPP problem
> > today and handle the dtc -i in the future.
> >
> > BOARD_DTS can point to anything below board/vendor and perhaps with a
> > new configuration option similar to CONFIG_DEFAULT_DEVICE_TREE the
> > substitution could be affected with freely selectable file name instead
> > of DEVICE_TREE only.
> 
> 
> ok.
> 
> Stephan: go ahead and create proper patch with empty dts/dtsi files.

Hi Michal,

see my patch set, that I've already submitted. The patches are based on
your patch set from last week. I've create a bundle on patchwork:

http://patchwork.ozlabs.org/bundle/rexut/microblaze-fdt/

Further you will need a QnD hack to avoid a compilation error due to
type conflicts (I've not explored here, not yet):

In file included from key_matrix.c:28:
include/malloc.h:364: error: conflicting types for 'memset'
include/linux/string.h:71: error: previous declaration of 'memset' was
here
include/malloc.h:365: error: conflicting types for 'memcpy'
include/linux/string.h:74: error: previous declaration of 'memcpy' was
here


Here is the QnD hack:


diff --git a/drivers/input/Makefile b/drivers/input/Makefile
index 5c831b2..5efeeb3 100644
--- a/drivers/input/Makefile
+++ b/drivers/input/Makefile
@@ -32,7 +32,7 @@ COBJS-y += keyboard.o pc_keyb.o
COBJS-$(CONFIG_PS2MULT) += ps2mult.o ps2ser.o
endif
COBJS-y += input.o
-COBJS-$(CONFIG_OF_CONTROL) += key_matrix.o
+#COBJS-$(CONFIG_OF_CONTROL) += key_matrix.o

COBJS  := $(COBJS-y)
SRCS   := $(COBJS:.o=.c)




br,
Stephan

  reply	other threads:[~2012-07-04 20:27 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
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 [this message]
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=1341433625.2722.27.camel@keto \
    --to=linz@li-pro.net \
    --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.