linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Pavel Machek <pavel@ucw.cz>, Theodore Ts'o <tytso@mit.edu>,
	Aung <aung.aungkyawsoe@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: need company for kernel upgrade
Date: Wed, 29 May 2019 10:04:52 +0200	[thread overview]
Message-ID: <5CEE3D24.8000700@bfs.de> (raw)
In-Reply-To: <585d6508-ace2-02d8-95ca-8e437d7cec05@metux.net>



Am 28.05.2019 21:35, schrieb Enrico Weigelt, metux IT consult:
> On 28.05.19 12:58, Pavel Machek wrote:
> 
> Hi,
> 
>> 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.
> 
> basic rule: don't use vendor kernels for production, unless you
> *really* *really* have to.

we have custom hardware, so this was needed. But we used std. parts
with existing drivers, so the upcomming problems were hidden in details.
Of cause we tested the hardware but you can find only obvious problems.

> 
> HW vendors usually don't have the capacities to offer any decent
> kernel support. there're only few exceptions (eg. phytec) that have
> their own kernel hackers and actively participate in upstreaming.

We have noticed that also, *active* is a big point.

> 
>>>> 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.
> 
> continuing the list w/ my own company --> info@metux.net
> 
> by the way: should we create a separate list for commercial topics ?
> 

I used linux-arm and it worked surprisingly well (not all mails went truh the list)
but it look very silent and i was unsure if they were still alive. A big win
for everyone would be a FAQ/Lessons-learned something you can take to check a contract.
the customer will know what to expect and the contractor will know what to offer.

Having something a list of minimum requirements like that FAQ would improve the stand of
the hardware developed to support linux. Not everyone has a big budget or need to
produce in millions like the raspi guys did, and even they have sometimes troubles.

note: that will not solve every proble but even a starting point would be good.

re,
 wh

  reply	other threads:[~2019-05-29  8:05 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
2019-05-28 19:35         ` Enrico Weigelt, metux IT consult
2019-05-29  8:04           ` walter harms [this message]
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=5CEE3D24.8000700@bfs.de \
    --to=wharms@bfs.de \
    --cc=aung.aungkyawsoe@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=pavel@ucw.cz \
    --cc=tytso@mit.edu \
    /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).