From: walter harms <wharms@bfs.de>
To: Aung <aung.aungkyawsoe@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: need company for kernel upgrade
Date: Thu, 23 May 2019 09:29:11 +0200 [thread overview]
Message-ID: <5CE64BC7.4010803@bfs.de> (raw)
In-Reply-To: <CABC7EG8NiiPycthdfb7Ng3MsxTvmmxk_LjcosM8ZD1F0CnuDFw@mail.gmail.com>
Am 23.05.2019 00:31, schrieb Aung:
> Hello
>
> I thought you build a kernel, then using SCP or dd to overwite uImage
> file to replace
> the previous kernel image into the file system, then reboot it. Or are
> you trying to
> upgrade without rebooting? Cheers!
>
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.
re,
wh
> Sincerely
>
> Aung
>
> On 5/22/19, walter harms <wharms@bfs.de> wrote:
>> the list was silent but NTL.
>>
>> Hi developers,
>> i am in search of a company that can help upgrading
>> a running linux-kernel on custom hardware.
>> Est. time 10 days.
>>
>>
>> The problems are already identified, we are aiming
>> the get the current vanilla linux kernel on the system.
>>
>>
>> re,
>> wh
>>
>> _______________________________________________
>> linux-arm mailing list
>> linux-arm@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm
>>
next parent reply other threads:[~2019-05-23 7:29 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 ` walter harms [this message]
2019-05-24 5:01 ` need company for kernel upgrade 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
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=5CE64BC7.4010803@bfs.de \
--to=wharms@bfs.de \
--cc=aung.aungkyawsoe@gmail.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).