From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: AVR32 branch merged
Date: Fri, 25 Jan 2008 07:42:36 -0500 [thread overview]
Message-ID: <4799D93C.20200@balister.org> (raw)
In-Reply-To: <47998D68.2090607@student.utwente.nl>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
Koen Kooi wrote:
> PS: uboot doesn't like jffs2+lzo, so be carefull where you load you
> uImage from.
>
> [1] http://dominion.thruhere.net/koen/cms/fun-with-vendor-patches-part-2
There are some atmel guys posting patches to the u-boot list. I don't
follow AVR32 closely, so I can't comment on what they do.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
prev parent reply other threads:[~2008-01-25 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 17:36 AVR32 branch merged Koen Kooi
2008-01-24 23:14 ` Michael 'Mickey' Lauer
2008-01-25 0:18 ` Florian Boor
2008-01-25 1:05 ` task-base image issue! Neha agarwal
2008-01-25 1:50 ` Michael 'Mickey' Lauer
[not found] ` <005601c85ef5$ff21c1e0$e10b10ac@nagarwaldt>
2008-01-25 2:20 ` Michael 'Mickey' Lauer
2008-01-25 7:47 ` BSP ohviey1
2008-01-25 7:19 ` AVR32 branch merged Koen Kooi
2008-01-25 12:42 ` Philip Balister [this message]
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=4799D93C.20200@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.