From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: Getting new udev to run with 2.6.28
Date: Sat, 10 Jan 2015 18:39:20 +0100 [thread overview]
Message-ID: <20150110173920.GA31847@amd> (raw)
Hi!
N900 has real problems on 3.19, and 2.6.28 should be very well
debugged version. Getting it to compile on recent distribution was
fun, but I succeeded. Unfortunately, Debian 7's udev does not work
with 2.6.28...
Does anyone have kernel patches to enable modern udev?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
khilman@kernel.org, aaro.koskinen@iki.fi,
ivo.g.dimitrov.75@gmail.com, Greg KH <greg@kroah.com>
Subject: Getting new udev to run with 2.6.28
Date: Sat, 10 Jan 2015 18:39:20 +0100 [thread overview]
Message-ID: <20150110173920.GA31847@amd> (raw)
Hi!
N900 has real problems on 3.19, and 2.6.28 should be very well
debugged version. Getting it to compile on recent distribution was
fun, but I succeeded. Unfortunately, Debian 7's udev does not work
with 2.6.28...
Does anyone have kernel patches to enable modern udev?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2015-01-10 17:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 17:39 Pavel Machek [this message]
2015-01-10 17:39 ` Getting new udev to run with 2.6.28 Pavel Machek
2015-01-10 18:05 ` Greg KH
2015-01-10 18:05 ` Greg KH
2015-01-10 18:09 ` Pavel Machek
2015-01-10 18:09 ` Pavel Machek
2015-01-10 18:17 ` Greg KH
2015-01-10 18:17 ` Greg KH
2015-01-10 21:18 ` Al Viro
2015-01-10 21:18 ` Al Viro
2015-01-10 22:25 ` Martin Steigerwald
2015-01-10 22:25 ` Martin Steigerwald
2015-01-10 23:06 ` Al Viro
2015-01-10 23:06 ` Al Viro
2015-01-11 9:04 ` Martin Steigerwald
2015-01-11 9:04 ` Martin Steigerwald
2015-01-11 10:12 ` Pavel Machek
2015-01-11 10:12 ` Pavel Machek
2015-01-11 10:43 ` Richard Weinberger
2015-01-11 10:43 ` Richard Weinberger
2015-01-10 19:54 ` Sven Joachim
2015-01-10 19:54 ` Sven Joachim
2015-01-10 19:13 ` Aaro Koskinen
2015-01-10 19:13 ` Aaro Koskinen
2015-01-10 21:18 ` Al Viro
2015-01-10 21:18 ` Al Viro
2015-01-10 22:49 ` Pavel Machek
2015-01-10 22:49 ` Pavel Machek
2015-01-10 22:59 ` Aaro Koskinen
2015-01-10 22:59 ` Aaro Koskinen
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=20150110173920.GA31847@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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.