lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa686aa40803171622j2183369ei7b384ada72d329d6@mail.gmail.com>
Date:	Mon, 17 Mar 2008 17:22:30 -0600
From:	"Grant Likely" <grant.likely@...retlab.ca>
To:	"Paul Gortmaker" <paul.gortmaker@...driver.com>
Cc:	"Adrian Bunk" <bunk@...nel.org>,
	"Kumar Gala" <galak@...nel.crashing.org>,
	"Paul Mackerras" <paulus@...ba.org>, linuxppc-dev@...abs.org,
	linux-kernel@...r.kernel.org
Subject: Re: powerpc: cuImage.* creation error

On Mon, Mar 17, 2008 at 4:46 PM, Paul Gortmaker
<paul.gortmaker@...driver.com> wrote:
> In message: Re: powerpc: cuImage.* creation error
>
>
> on 17/03/2008 Grant Likely wrote:
>
>  > On Mon, Mar 17, 2008 at 2:07 PM, Paul Gortmaker
>  > <paul.gortmaker@...driver.com> wrote:
>  > > In message: powerpc: cuImage.* creation error
>  > >
>  > >  @@ -253,8 +253,8 @@ image-$(CONFIG_TQM8540)                     += cuImage.tqm8540
>  > >   image-$(CONFIG_TQM8541)                        += cuImage.tqm8541
>  > >   image-$(CONFIG_TQM8555)                        += cuImage.tqm8555
>  > >   image-$(CONFIG_TQM8560)                        += cuImage.tqm8560
>  > >  -image-$(CONFIG_SBC8548)                        += cuImage.tqm8548
>  > >  -image-$(CONFIG_SBC8560)                        += cuImage.tqm8560
>  > >  +image-$(CONFIG_SBC8548)                        += cuImage.sbc8548
>  > >  +image-$(CONFIG_SBC8560)                        += cuImage.sbc8560
>  >
>  > No, the suffix in the cuImage targets has a 1:1 relationship with dts
>  > files in arch/powerpc/boot/dts/.  If a file doesn't exist there, then
>  > the target cannot be built.
>
>  You should have both the sbc8548.dts and the sbc8560.dts in your tree.
>  They have been in there for several weeks now.

Heh; oops.  I looked but somehow missed them.  I guess I didn't look
hard enough.

Yes, this looks like the right solution.

>  Author: Paul Gortmaker <paul.gortmaker@...driver.com>
>  Date:   Mon Mar 17 18:33:52 2008 -0400
>
>     wrapper: Add entries for tqm8540 and sbc85xx
>
>     The wrapper script didn't have entries for the TQM8540 board and the
>     SBC8548 or SBC8560 boards.  I've assumed that the TQM8540 console is
>     8250 based and not CPM based by looking at its defconfig.  There was
>     also a trailing * on the TQM8555 entry that I removed too.
>
>
>     Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
Acked-by: Grant Likely <grant.likely@...retlab.ca>

Cheers,
g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ