From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: PATCH: Use uImage make target for linux-omap1
Date: Sun, 05 Aug 2007 18:42:29 -0400 [thread overview]
Message-ID: <46B65255.1020101@balister.org> (raw)
In-Reply-To: <19c1b8a90708041839r9254f4bn53123d1d098bba0f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
I applied the patch locally, rebuilt my kernel, flashed into the OSK and
it ran fine. Basically, the patch fixes the kernel name to match the
image type (previously I called the uImage vmlinux) this causes
confusion with people who really understand all the kernel names.
Basically, this is one of the earliest contributions to OE and I am glad
it lasted this long :)
End result, the images should be compatible, and the filename in
deploy/images changes from vmlinux.... to uImage... The new name
accurately describes the image.
Philip
Khem Raj wrote:
> On 8/4/07, Luís Vitório Cargnini <lvcargnini@gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> openembedded is working for my OSK 5912 without this patch I dont felt
>> it is necessary.
>
> I would be happy if you could try this patch and see if it does not
> break anything for you.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2007-08-05 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 0:35 PATCH: Use uImage make target for linux-omap1 Khem Raj
2007-08-04 2:24 ` Luís Vitório Cargnini
2007-08-04 6:19 ` Koen Kooi
2007-08-04 11:57 ` Philip Balister
2007-08-04 19:00 ` Khem Raj
2007-08-04 21:56 ` Luís Vitório Cargnini
2007-08-05 1:39 ` Khem Raj
2007-08-05 22:42 ` Philip Balister [this message]
2007-08-06 3:33 ` Khem Raj
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=46B65255.1020101@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.