From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Dave Young <dyoung@redhat.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Pavel Machek" <pavel@ucw.cz>,
"Sebastian Reichel" <sre@kernel.org>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Tony Lindgren" <tony@atomide.com>, "Nishanth Menon" <nm@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux 4.2-rc1 broken Nokia N900
Date: Fri, 24 Jul 2015 11:30:51 +0300 [thread overview]
Message-ID: <55B1F7BB.9020102@gmail.com> (raw)
In-Reply-To: <20150724081809.GB22852@dhcp-128-11.nay.redhat.com>
On 24.07.2015 11:18, Dave Young wrote:
> Pali, could you tell how do you test mainline kernel on n900?
>
> I used to use n900 as a usb dbgp gadget with a backport patch to
> 2.6.28 so that I can get early debug kernel message from my laptop.
>
> I tried mainline previously with Fedora arm, text mode works but
> no graphics. Is there a way to use maemo UI with mainline kernel?
>
> Thanks
> Dave
>
http://talk.maemo.org/showpost.php?p=1459970&postcount=142
This is the last (almost) upstream kernel I tried, unfortunately
recently I am very short on spare time, so cannot confirm for 4.x
kernels, but in theory those should work as well.
The kernel tree was on gitorious, but it is down now(I have a local
copy). However, all of the needed patches should be on
https://github.com/pali/linux-n900.
Ivo
next prev parent reply other threads:[~2015-07-24 8:30 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 12:05 linux 4.2-rc1 broken Nokia N900 Pali Rohár
2015-07-13 6:44 ` Tony Lindgren
2015-07-13 8:09 ` Sebastian Reichel
2015-07-13 17:03 ` Michael Welling
2015-07-13 17:09 ` Pali Rohár
2015-07-13 17:56 ` Michael Welling
2015-07-13 20:28 ` Michael Welling
2015-07-13 20:34 ` Pali Rohár
2015-07-13 21:52 ` Michael Welling
2015-07-13 22:02 ` Pali Rohár
2015-07-13 22:36 ` Michael Welling
2015-07-14 7:14 ` Pali Rohár
2015-07-14 7:45 ` Tony Lindgren
2015-07-14 16:33 ` Michael Welling
2015-07-14 20:01 ` Pavel Machek
2015-07-14 20:17 ` Michael Welling
2015-07-15 19:49 ` Pavel Machek
2015-07-15 20:10 ` Michael Welling
2015-07-21 7:31 ` Pavel Machek
2015-07-21 7:33 ` Pavel Machek
2015-07-21 8:04 ` Pali Rohár
2015-07-20 20:48 ` Michael Welling
2015-07-20 20:46 ` Michael Welling
2015-07-20 20:58 ` Pali Rohár
2015-07-21 9:34 ` Pavel Machek
2015-07-21 21:28 ` Michael Welling
2015-07-22 0:17 ` Michael Welling
2015-07-22 2:03 ` Sebastian Reichel
2015-07-22 5:13 ` Michael Welling
2015-07-22 7:27 ` Pali Rohár
2015-07-22 13:33 ` Sebastian Reichel
2015-07-22 14:27 ` Pali Rohár
2015-07-22 13:30 ` Pavel Machek
2015-07-25 8:55 ` Pali Rohár
2015-07-28 8:39 ` Pali Rohár
2015-07-28 12:26 ` Sebastian Reichel
2015-07-28 12:32 ` Pali Rohár
2015-07-13 11:10 ` Pali Rohár
2015-07-13 13:26 ` Tony Lindgren
2015-07-13 15:51 ` Sebastian Reichel
2015-07-13 16:05 ` Pali Rohár
2015-07-13 19:32 ` Sebastian Reichel
2015-07-14 0:18 ` Krzysztof Kozlowski
2015-07-24 8:18 ` Dave Young
2015-07-24 8:30 ` Ivaylo Dimitrov [this message]
2015-07-24 10:28 ` Dave Young
2015-07-24 10:53 ` Pali Rohár
2015-07-24 8:40 ` Pali Rohár
2015-07-24 10:33 ` Dave Young
2015-07-24 10:52 ` Pali Rohár
2015-07-24 15:50 ` Pali Rohár
2015-07-24 8:51 ` Pavel Machek
2015-07-24 10:39 ` Dave Young
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=55B1F7BB.9020102@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=dyoung@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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).