Dear Marek Vasut,
In message <201206221444.46242.ma...@denx.de> you wrote:
>
> I think we're missing each others point. So, lemme put it this way:
>
> We have CPU X, which uses sequence of commands, sequence A.
> We have CPU Y, which uses sequence of commands, sequence B.
>
> We want make targe
Dear Wolfgang Denk,
> Dear Marek Vasut,
>
> In message <201205231422.17293.ma...@denx.de> you wrote:
> > > What would be wrong if all boards would use the same
> > > "u-boot.bin.sdcard" target name?
> >
> > That such file (u-boot.bin.sdcard) would be generated by a different tool
> > for each di
Dear Marek Vasut,
In message <201205231422.17293.ma...@denx.de> you wrote:
>
> > What would be wrong if all boards would use the same "u-boot.bin.sdcard"
> > target name?
>
> That such file (u-boot.bin.sdcard) would be generated by a different tool for
> each different board, unlike u-boot.bin
Dear Wolfgang Denk,
> Dear Marek Vasut,
>
> In message <201205231334.53948.ma...@denx.de> you wrote:
> > > > Maybe add some switch statement based on CONFIG_MX28 or another
> > > > within the target?
> > >
> > > I can't parse this sentence - and I don't understand why you think
> > > any specifi
Dear Marek Vasut,
In message <201205231334.53948.ma...@denx.de> you wrote:
>
> > > Maybe add some switch statement based on CONFIG_MX28 or another within
> > > the target?
> >
> > I can't parse this sentence - and I don't understand why you think
> > any specific name would be needed or useful.
Dear Wolfgang Denk,
> Dear Marek Vasut,
>
> In message <201205231144.04272.ma...@denx.de> you wrote:
> > > Because there'd then be no way to tell apart u-boot.bin.sd for another
> > > target but mx28.
> >
> > Maybe add some switch statement based on CONFIG_MX28 or another within
> > the target?
Dear Marek Vasut,
In message <201205231144.04272.ma...@denx.de> you wrote:
>
> > Because there'd then be no way to tell apart u-boot.bin.sd for another
> > target but mx28.
>
> Maybe add some switch statement based on CONFIG_MX28 or another within the
> target?
I can't parse this sentence - an
Dear Marek Vasut,
In message <201205231127.51935.ma...@denx.de> you wrote:
>
> Because there'd then be no way to tell apart u-boot.bin.sd for another target
> but mx28.
So what? We also use "u-boot.bin" for all targets. What's the
difference?
> > Would it not be useful to automatically build
Dear Wolfgang Denk,
> > Dear Marek Vasut,
> >
> > In message <1337729574-30475-1-git-send-email-ma...@denx.de> you wrote:
> > > These targets allow for easy invocation of mxstool, for generating
> > > the u-boot images bootable in mx28 CPU.
> >
> > Thanks.
> >
> > > +$(obj)u-boot.mx28.sd: $(ob
Dear Wolfgang Denk,
> Dear Marek Vasut,
>
> In message <1337729574-30475-1-git-send-email-ma...@denx.de> you wrote:
> > These targets allow for easy invocation of mxstool, for generating
> > the u-boot images bootable in mx28 CPU.
>
> Thanks.
>
> > +$(obj)u-boot.mx28.sd: $(obj)u-boot.sb
> > +
Dear Marek Vasut,
In message <1337729574-30475-1-git-send-email-ma...@denx.de> you wrote:
> These targets allow for easy invocation of mxstool, for generating
> the u-boot images bootable in mx28 CPU.
Thanks.
> +$(obj)u-boot.mx28.sd: $(obj)u-boot.sb
> + $(obj)tools/mxsboot sd $(obj)
These targets allow for easy invocation of mxstool, for generating
the u-boot images bootable in mx28 CPU.
Signed-off-by: Marek Vasut
Cc: Wolfgang Denk
Cc: Stefano Babic
Cc: Fabio Estevam
CC: Albert Aribaud
---
Makefile |6 ++
doc/README.mx28_common | 39 +
12 matches
Mail list logo
