Hi Daniel,
On Fri, 28 Mar 2014 21:35:37 +0100
Daniel Schwierzeck wrote:
> 2014-03-28 3:25 GMT+01:00 Masahiro Yamada :
> >>
> >> Those boards have linker errors, but I do not understand yet why. For
> >> example on ARM the linker complains about multiple definition of
> >> board_init() and board_
2014-03-28 3:25 GMT+01:00 Masahiro Yamada :
>>
>> Those boards have linker errors, but I do not understand yet why. For
>> example on ARM the linker complains about multiple definition of
>> board_init() and board_eth_init(). The solely difference is that there
>> are one or two additional intermed
Hi Daniel,
Sorry not to have followed up earlier. I was sick in bed.
On Mon, 24 Mar 2014 21:35:15 +0100
Daniel Schwierzeck wrote:
> 2014-03-24 7:35 GMT+01:00 Masahiro Yamada :
> >
> > Thanks for your effort. I think basicly we're going to the right direction.
> > But I am afraind more careful c
2014-03-24 7:35 GMT+01:00 Masahiro Yamada :
>
> Thanks for your effort. I think basicly we're going to the right direction.
> But I am afraind more careful check is necessary before posting the
> series.
>
>
> I did build test on your patches on kconfig-support branch.
> I noticed many boards would
Hi Daniel,
On Sat, 22 Mar 2014 18:14:23 +0100
Daniel Schwierzeck wrote:
> 2014-03-21 19:05 GMT+01:00 Tom Rini :
> > On Thu, Mar 20, 2014 at 02:17:07PM +0100, Daniel Schwierzeck wrote:
> >> 2014-03-20 1:11 GMT+01:00 Masahiro Yamada :
> >> >
> >> > [3]
> >> > How to select board directoy by using
2014-03-21 19:05 GMT+01:00 Tom Rini :
> On Thu, Mar 20, 2014 at 02:17:07PM +0100, Daniel Schwierzeck wrote:
>> 2014-03-20 1:11 GMT+01:00 Masahiro Yamada :
>> >
>> > [3]
>> > How to select board directoy by using boolean macros.
>> >
>> > If we try to emulate arch/arm/Makefile of Linux,
>> >
>> > bo
On Thu, Mar 20, 2014 at 02:17:07PM +0100, Daniel Schwierzeck wrote:
> 2014-03-20 1:11 GMT+01:00 Masahiro Yamada :
> >
> > Basicly I think it's a good idea, but I am afraid there are some
> > problems.
> >
> > [1]
> > First, in this case, how can we select the target board?
> >
> > Like this?
> >
>
On Thu, Mar 20, 2014 at 08:48:04AM +0900, Masahiro Yamada wrote:
> Hi Tom,
>
>
> > > In message
> > > you
> > > wrote:
> > > >
> > > > maybe we should import get_maintainers.pl from kernel and readd
> > > > MAINTAINERS in the according format. So we could easily maintain infos
> > > > about bo
2014-03-20 1:11 GMT+01:00 Masahiro Yamada :
>
> Basicly I think it's a good idea, but I am afraid there are some
> problems.
>
> [1]
> First, in this case, how can we select the target board?
>
> Like this?
>
> choice
> prompt "Board select"
> default BOARD_SANDBOX
>
> config BOARD_
Hi Daniel,
> agree. But at first we should introduce Kconfig files in all arch,
> CPU, SOC, SOC common, board vendor, board and driver directories where
> we put all CONFIG_SYS_ symbols. We also need to convert the current
> config options for CPU, SOC, vendor and board. For example:
>
> CONFIG_
Hi Tom,
> > In message
> > you
> > wrote:
> > >
> > > maybe we should import get_maintainers.pl from kernel and readd
> > > MAINTAINERS in the according format. So we could easily maintain infos
> > > about board maintainers, custodians, custodian trees and maintaining
> > > status per arch, C
Hi Tom,
> So, what this series is doing, roughly, is turning just the boards.cfg
> entry into a small Kconfig snippet, and saying we'll keep using
> include/configs/foo.h for most of the work. This is just the first step
> in moving away from include/configs/foo.h eventually, yes?
Yes, exactly.
On 03/18/2014 10:50 PM, Masahiro Yamada wrote:
> diff --git a/configs/beaver_defconfig b/configs/beaver_defconfig
> new file mode 100644
> index 000..fbf00f3
> --- /dev/null
> +++ b/configs/beaver_defconfig
> @@ -0,0 +1,10 @@
> +CONFIG_SPL=y
> +CONFIG_ARM=y
>
On Wed, Mar 19, 2014 at 03:20:49PM +0100, Wolfgang Denk wrote:
> Dear Daniel Schwierzeck,
>
> please do not full-quote. Thanks.
>
> In message
> you
> wrote:
> >
> > maybe we should import get_maintainers.pl from kernel and readd
> > MAINTAINERS in the according format. So we could easily mai
Dear Daniel Schwierzeck,
please do not full-quote. Thanks.
In message
you wrote:
>
> maybe we should import get_maintainers.pl from kernel and readd
> MAINTAINERS in the according format. So we could easily maintain infos
> about board maintainers, custodians, custodian trees and maintaining
>
On Mon, Mar 17, 2014 at 05:52:59PM +0900, Masahiro Yamada wrote:
> In Kconfig, we use "*_defconfig" files for board configuration.
>
> In Linux Kernel, they are located under arch/${ARCH}/configs/ directory.
> It works in Linux Kernel because ARCH is always given from the
> command line for cross
2014-03-19 11:51 GMT+01:00 Masahiro Yamada :
> Hi Wolfgang,
>
>
> On Wed, 19 Mar 2014 10:56:46 +0100
> Wolfgang Denk wrote:
>
>> Dear Masahiro,
>>
>> In message <20140319135026.7a64.aa925...@jp.panasonic.com> you wrote:
>> >
>> > > >>> +++ b/configs/beaver_defconfig
>> > > >>> @@ -0,0 +1,10 @@
>>
Hi Wolfgang,
On Wed, 19 Mar 2014 10:56:46 +0100
Wolfgang Denk wrote:
> Dear Masahiro,
>
> In message <20140319135026.7a64.aa925...@jp.panasonic.com> you wrote:
> >
> > > >>> +++ b/configs/beaver_defconfig
> > > >>> @@ -0,0 +1,10 @@
> > > >>> +CONFIG_SPL=y
> > > >>> +CONFIG_ARM=y
> > > >>> +CO
Dear Masahiro,
In message <20140319135026.7a64.aa925...@jp.panasonic.com> you wrote:
>
> > >>> +++ b/configs/beaver_defconfig
> > >>> @@ -0,0 +1,10 @@
> > >>> +CONFIG_SPL=y
> > >>> +CONFIG_ARM=y
> > >>> +CONFIG_SYS_CPU="armv7"
> > >>> +CONFIG_SOC_DIR=y
> > >>> +CONFIG_SYS_SOC="tegra30"
> > >>> +C
Hi Stephen,
> >>> diff --git a/configs/beaver_defconfig b/configs/beaver_defconfig
> >>> new file mode 100644
> >>> index 000..fbf00f3
> >>> --- /dev/null
> >>> +++ b/configs/beaver_defconfig
> >>> @@ -0,0 +1,10 @@
> >>> +CONFIG_SPL=y
> >>> +CONFIG_ARM=y
> >>> +CONFIG_SYS_CPU="armv7"
> >>> +C
On 03/18/2014 09:16 PM, Masahiro Yamada wrote:
> Hi Stephen,
>
>>> diff --git a/configs/beaver_defconfig b/configs/beaver_defconfig
>>> new file mode 100644
>>> index 000..fbf00f3
>>> --- /dev/null
>>> +++ b/configs/beaver_defconfig
>>> @@ -0,0 +1,10 @@
>>> +CONFIG_SPL=y
>>> +CONFIG_ARM=y
>>>
Hi Stephen,
> > diff --git a/configs/beaver_defconfig b/configs/beaver_defconfig
> > new file mode 100644
> > index 000..fbf00f3
> > --- /dev/null
> > +++ b/configs/beaver_defconfig
> > @@ -0,0 +1,10 @@
> > +CONFIG_SPL=y
> > +CONFIG_ARM=y
> > +CONFIG_SYS_CPU="armv7"
> > +CONFIG_SOC_DIR=y
> > +
On 03/17/2014 02:52 AM, Masahiro Yamada wrote:
> In Kconfig, we use "*_defconfig" files for board configuration.
>
> In Linux Kernel, they are located under arch/${ARCH}/configs/ directory.
> It works in Linux Kernel because ARCH is always given from the
> command line for cross compile.
>
> But
23 matches
Mail list logo
