From: Pavel Machek <pavel@ucw.cz>
To: Theodore Ts'o <tytso@mit.edu>, walter harms <wharms@bfs.de>,
Aung <aung.aungkyawsoe@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: need company for kernel upgrade
Date: Tue, 28 May 2019 12:58:53 +0200 [thread overview]
Message-ID: <20190528105853.GA21111@amd> (raw)
In-Reply-To: <20190524050116.GI2532@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Fri 2019-05-24 01:01:16, Theodore Ts'o wrote:
> On Thu, May 23, 2019 at 09:29:11AM +0200, walter harms wrote:
> >
> > No,
> > the company i am working for has a custom build arm-board.
> > We bought the kernel from the assembler but found it has
> > some problems that need fixing.
> > Basically we want to improve the linux-kernel so it can run
> > native on our boards.
> >
> > >> Hi developers,
> > >> i am in search of a company that can help upgrading
> > >> a running linux-kernel on custom hardware.
> > >> Est. time 10 days.
>
> Have you tried contacting Linutronix (https://linutronix.de) or
> Collabora (https://collabora.com)?
>
> Both have EU offices --- well Collabora does for now, until Brexit
> happens. :-)
www.denx.de is another option.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-05-28 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5CE53BA9.4070906@bfs.de>
[not found] ` <CABC7EG8NiiPycthdfb7Ng3MsxTvmmxk_LjcosM8ZD1F0CnuDFw@mail.gmail.com>
2019-05-23 7:29 ` need company for kernel upgrade walter harms
2019-05-24 5:01 ` Theodore Ts'o
2019-05-28 10:58 ` Pavel Machek [this message]
2019-05-28 19:35 ` Enrico Weigelt, metux IT consult
2019-05-29 8:04 ` walter harms
2019-05-29 12:31 ` Enrico Weigelt, metux IT consult
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=20190528105853.GA21111@amd \
--to=pavel@ucw.cz \
--cc=aung.aungkyawsoe@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wharms@bfs.de \
/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;
as well as URLs for NNTP newsgroup(s).