From: <mailinglist@miromico.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Adding support for our
Date: Fri, 17 Oct 2008 23:22:38 +0200 [thread overview]
Message-ID: <449dbc2c021997d20314e77536d2f770@mail.nine.ch> (raw)
In-Reply-To: <48F8745B.2030001@gmx.net>
Hi,
>> 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. :)
Thanks.
>
>> 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.
Yes, I know. I have an ATNGW100 as well. The problem is, that the oe for
atngw100
fails. It does compile (console-image), but I can't boot. I get a segfault
in init (sysvinit).
>
>> 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.
Ok, I'll check that out...
Alex
next prev parent reply other threads:[~2008-10-17 21:22 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
2008-10-17 21:22 ` mailinglist [this message]
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=449dbc2c021997d20314e77536d2f770@mail.nine.ch \
--to=mailinglist@miromico.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox