From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Adding support for our
Date: Fri, 17 Oct 2008 13:17:47 +0200 [thread overview]
Message-ID: <48F8745B.2030001@gmx.net> (raw)
In-Reply-To: <48F825DE.90104@miromico.ch>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
Hi Alexm
Alex Raimondi schrieb:
> We have a new AVR32 based embedded linux board (www.miromico.com/hammerhead), which is available now.
That is a nice little board you have there. I personally like the AVR32
architecture. Atmel also has the better policy when it comes to
specifications. So I really like to see more AVR32 being used. :)
> We would like to use OpenEmbedded as our major build system to allow our customers to build their u-boot,
> kernel and rootfs.
Great stuff. OE already supports the ATNGW100 (have one here) and the
AT32STK1000. If your board can boot with the same linux 2.6.24 (or with
patches to that) it will be quite easy to support your device.
> Of course we would like to contribute to oe, as well.
Very nice!
> Is there such a thing as a board maintainer in oe? If yes, how can we become one?
We have a "MAINTAINERS" file. If you are a contributor you can add
information about the machines you are maintaining. This mainly means
that people will ask you when stuff breaks. In theory it should also
mean that people will ask you *first* if things are changed in OE that
affect your device but AFAIK we have no strict policies regarding this.
> We allready adapted a few bb files to get oe building our u-boot and kernel. Should we push out these changes?
> How?
Open a bug report.
> We have two developers working at this project. Our board is AVR32 based.
So, if oe is our major build system we would have to take care that
avr32 allway builds.
This means testing, fixing, extending support. I hope this would be
benefit enough to endure our newbie questions
while we are getting known with the build system.
OE has a very steep learning curve but when you managed it you will
benefit very much from its great flexibility.
Thanks for supporting our project!
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-10-17 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 5:42 Adding support for our Alex Raimondi
2008-10-17 11:17 ` Robert Schuster [this message]
2008-10-17 21:22 ` mailinglist
2008-10-24 9:47 ` Robert Schuster
2008-10-17 11:19 ` Cliff Brake
2008-10-18 21:37 ` Leon Woestenberg
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=48F8745B.2030001@gmx.net \
--to=thebohemian@gmx.net \
--cc=openembedded-devel@lists.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.