From: Jeremy Grant <jgrant@vml.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Working with OEMs
Date: Fri, 5 Feb 2010 13:28:59 -0600 [thread overview]
Message-ID: <C791CD9B.22735%jgrant@vml.com> (raw)
I am currently working on project that we are planning on using
openembedded. We will be using 6 ereader devices initially from 2
different manufactures. One of the manufactures already uses open
embedded the other is not. We are needing to explain to the other OEM
why they should be uses open embedded to build the images used on the
devices so that all devices are consistent and can pull from one feed
source for updates.
Here are a few of the requirements I have right now:
Must use qt-embedded 4.6.x
Would be nice if it can uses arora-e
I have a few question on what I should be doing.
Should I create my own distribution based on angstrom or just create
and image with preferred-versions for the ereaders and used angstrom as
the distro?
What suggestions does anyone have on working with the OEM that does not
uses OE already to help them see why using OE would be beneficial to
them? I find information on why developers and distribution
maintainers should uses OE but not much information on how an OEM could
create machine.conf to be used with OE or use OE. I may just have not
found the correct presentation or blog that has the information I am
looking for.
Thanks for any help you can give.
Jeremy Grant
VML | Lead Systems Administrator
2020 Baltimore, Kansas City, MO 64108
office: +1.816.218.1956
fax: +1.816.472.5234
mobile: +1.913.636.1112
email: [1]jgrant@vml.com
Before you print, please think about the environment.
Confidentiality Statement This transmission is confidential and
intended solely for the party to whom it is addressed. If the reader of
this email is not the intended recipient, you are hereby notified that
it may contain privileged, confidential and trade secret information,
and that any dissemination, distribution, copying or use of the
information in this transmission is strictly prohibited. If you have
received this transmission in error, please immediately notify the
sender at the email address above, and delete all copies of it from
your computer.
References
1. file://localhost/tmp/jgrant@vml.com
next reply other threads:[~2010-02-05 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 19:28 Jeremy Grant [this message]
2010-02-06 19:12 ` Working with OEMs Holger Hans Peter Freyther
2010-02-08 16:48 ` C Michael Sundius
2010-02-08 18:37 ` Philip Balister
2010-02-09 17:56 ` C Michael Sundius
2010-02-09 21:47 ` Michael Smith
2010-02-09 22:33 ` Peter Chubb
2010-02-09 23:23 ` C Michael Sundius
2010-02-09 23:01 ` C Michael Sundius
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=C791CD9B.22735%jgrant@vml.com \
--to=jgrant@vml.com \
--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.