From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] v4.19.50-cip3-rt2
Date: Wed, 24 Jul 2019 13:53:06 +0200 [thread overview]
Message-ID: <20190724115306.GA26706@amd> (raw)
In-Reply-To: <CAEss1EKQ_6SWV+Z5aOCkdrtDGGXOhN_ASfDs6Zf1UcjJm5mX0w@mail.gmail.com>
Hi!
> I finally was able to make the viable .config... For the previous
> rt-kernel for BBB.
>
> root at beaglebone:~# uname -a
> Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
> GMT 2019 armv7l GNU/Linux
>
> It was very tough and rough... But I have it! Now I need to abandon
> this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190724/6b99cda7/attachment-0001.sig>
next prev parent reply other threads:[~2019-07-24 11:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 12:40 [cip-dev] [ANNOUNCE] v4.19.50-cip3-rt2 Pavel Machek
2019-07-23 13:53 ` Jan Kiszka
2019-07-23 21:06 ` Pavel Machek
2019-07-24 3:45 ` Zoran S
2019-07-24 11:53 ` Pavel Machek [this message]
2019-07-24 13:00 ` Zoran S
2019-07-24 16:06 ` Zoran S
2019-07-25 0:22 ` daniel.sangorrin at toshiba.co.jp
2019-07-25 6:44 ` Zoran S
2019-07-26 21:05 ` Pavel Machek
2019-07-27 2:19 ` Zoran S
2019-07-23 21:12 ` [cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24 Pavel Machek
2019-07-25 8:50 ` Daniel Wagner
2019-07-25 9:06 ` Jan Kiszka
2019-07-25 9:12 ` Daniel Wagner
2019-07-25 11:42 ` Ralf Ramsauer
2019-07-26 17:27 ` Daniel Wagner
2019-07-29 10:23 ` Daniel Wagner
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=20190724115306.GA26706@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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.