From: Roger Quadros <roger.quadros@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
ext Arnaud Ebalard <arno@natisbad.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Leukkunen Lauri (Nokia-D/Helsinki)" <lauri.leukkunen@nokia.com>,
"Palande Ameya (Nokia-D/Helsinki)" <ameya.palande@nokia.com>
Subject: Re: Upstream linux-omap kernel on Nokia N900?
Date: Tue, 20 Apr 2010 11:36:28 +0300 [thread overview]
Message-ID: <4BCD678C.6020407@nokia.com> (raw)
In-Reply-To: <20100419195156.GT5514@atomide.com>
ext Tony Lindgren wrote:
> * Roger Quadros <roger.quadros@nokia.com> [100419 05:06]:
>> Balbi Felipe (Nokia-D/Helsinki) wrote:
>>> Hi,
>>>
>>> On Mon, Apr 19, 2010 at 01:49:15PM +0200, ext Arnaud Ebalard wrote:
>>>> Nokia N900 is shipped to users with a 2.6.28 omap kernel. Many patches
>>>> for the hardware and various features have been pushed upstream by Nokia
>>>> developers and possibly others. Those are now available in current l-o
>>>> tree.
>>>>
>>>> Nonetheless, many drivers and various features are still missing
>>>> upstream. Simply put, one cannot expect to run a current l-o kernel on
>>>> the device (and expect to get a GUI and/or make call with the device).
>>> tell me about it :-p
>>>
>>> Thing is that it doesn't really depend only on Nokia to get those
>>> parts done. Well, we can get the kernel part done by just cleaning
>>> up and porting the 2.6.28 drivers to current mainline, but in case
>>> of e.g. SGX we still miss the xorg driver and I don't think
>>> that'll be released any time soon.
>>>
>>> Another problem is that the bootloader believes it can pass all
>>> the obsoleted OMAP TAGs to kernel and the 2.6.28 kernel depends on
>>> those, maybe that can be worked around. I don't know whether
>>> kernel simply drops invalid TAGs or not...
>> Yes kernel simply drops unrecognized TAGs and just prints a warning message.
>
> All the the custom tags should be replaced with platform_data.
>
> If something is needed for revision detection of the board,
> there is arm-linux common ATAG_REVISION.
>
> However, also Maemo userspace depends on some things set by the
> custom tags. As this is non-standard, we should not spend much
> effort on that. Instead we should concentrate on making N900
> work with any distro the standard Linux way.
>
> So I recommend using kexec patched Maemo kernel, then boot the
> new mainline kernel from Maemo kernel and mount root directly
> on the eMMC.
FYI. kexec-tools will be available in maemo.org repo soon and you can also
expect kexec patched kernel to be available.
Then we need a kexec helper utility that parses /proc/atags and feeds the
necessary stuff on Command line for the new kernel.
So the ATAG Hacks will be unnecessary.
cheers,
-roger
next prev parent reply other threads:[~2010-04-20 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 11:49 Upstream linux-omap kernel on Nokia N900? Arnaud Ebalard
2010-04-19 12:00 ` Felipe Balbi
2010-04-19 12:09 ` Roger Quadros
2010-04-19 19:51 ` Tony Lindgren
2010-04-20 8:36 ` Roger Quadros [this message]
2010-04-20 8:53 ` Ameya Palande
2010-04-20 9:20 ` Lauri Leukkunen
2010-04-19 12:23 ` Arnaud Ebalard
2010-04-19 12:29 ` Felipe Balbi
2010-04-19 12:36 ` Arnaud Ebalard
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=4BCD678C.6020407@nokia.com \
--to=roger.quadros@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=arno@natisbad.org \
--cc=felipe.balbi@nokia.com \
--cc=lauri.leukkunen@nokia.com \
--cc=linux-omap@vger.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