From: Grammostola Rosea <rosea.grammostola@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Debian Developers <debian-devel@lists.debian.org>,
linux-rt-users@vger.kernel.org, 521893@bugs.debian.org
Subject: Re: realtime kernel for Debian
Date: Thu, 04 Jun 2009 11:28:57 +0200 [thread overview]
Message-ID: <4A2793D9.308@gmail.com> (raw)
In-Reply-To: <20090513093517.GA11278@pengutronix.de>
Uwe Kleine-König wrote:
> Hi,
>
>
>>>> I was wondering about how far are we with implementing a RT kernel in
>>>> Debian... Some progress here? Would be nice.
>>>>
>>>>
>>> The patch I created that "fits" on Debian's vanilla kernel creates
>>> conflicts on the sources with the Debian patches.
>>> I hope to be able to clean that up by minimizing the -rt series (e.g.
>>> the first broken out patch consists usually of various bits from the
>>> -tip tree that are (AFAIK) not all needed.)
>>>
>>> So just have some more patience.
>>>
>>>
>>>
>> How are things going? Just interest...
>>
> Hhhm, well, I spottet a problem. The thing is that linux-rt does many
> deep changes in the kernel and I won't be able to support the harder
> problems. And upstream probably won't help because the Debian rt-kernel
> isn't a vanilla rt-kernel. Moreover even the broken out rt-patch isn't
> nicely sorted (e.g. bisectable, some patches undo changes of other
> patches earier in the series etc. pp), so I fear the Debian kernel team
> isn't filled with enthusiasm when asked to add an rt variant.
>
> I already thought about packaging debian-kernel + rt for Debian and
> vanilla-kernel + rt for a non-Debian package repository such that it's
> easy for bug reporters to try out a vanilla kernel. But that still needs
> more work.
>
> I currently investigate how the Debian kernel packages are created. Any
> help is welcome. Probably the first step will be to create a vanilla-rt
> package, but that wont be accepted to go into Debian main.
>
>
Just trying to keep thinks a bit alive here ;)
How are things going Uwe?
Kind regards,
\r
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-04 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903242311.10783.nescivi@gmail.com>
[not found] ` <alpine.DEB.2.00.0903250812230.17709@wr-linux02>
[not found] ` <49CA1781.3050603@gmail.com>
[not found] ` <20090325131713.GH15865@ltw.loris.tv>
[not found] ` <49CDFB4D.7070908@gmail.com>
[not found] ` <f1357b430903280615u215182fan2e62581394174603@mail.gmail.com>
[not found] ` <alpine.DEB.2.00.0903282331360.22173@wr-linux02>
[not found] ` <49CF50D3.1080000@gmail.com>
2009-03-29 18:28 ` realtime kernel for Debian Grammostola Rosea
2009-03-29 18:55 ` Uwe Kleine-König
2009-03-29 19:01 ` Grammostola Rosea
2009-03-29 19:56 ` Uwe Kleine-König
2009-03-30 8:22 ` Alexander Reichle-Schmehl
2009-03-30 15:13 ` Uwe Kleine-König
[not found] ` <49DF05B6.6000603@gmail.com>
[not found] ` <20090413195356.GA13942@pengutronix.de>
[not found] ` <4A09CEBC.70207@gmail.com>
2009-05-13 9:35 ` Uwe Kleine-König
2009-06-04 9:28 ` Grammostola Rosea [this message]
2009-10-02 20:20 ` Uwe Kleine-König
2009-10-02 21:04 ` rosea grammostola
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=4A2793D9.308@gmail.com \
--to=rosea.grammostola@gmail.com \
--cc=521893@bugs.debian.org \
--cc=debian-devel@lists.debian.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.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).