public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 3/3] ARM: OMAP: Add menelaus chip info for N800
Date: Mon, 11 Jun 2007 06:31:22 -0700	[thread overview]
Message-ID: <20070611133121.GL16039@atomide.com> (raw)
In-Reply-To: <5d5443650706062229w3c65145ekee52f30dfc2d014e@mail.gmail.com>

* Trilok Soni <soni.trilok@gmail.com> [070606 22:29]:
> On 6/7/07, Carlos Aguiar <carlos.aguiar@indt.org.br> wrote:
>> ext Trilok Soni wrote:
>> > On 6/5/07, Carlos Aguiar <carlos.aguiar@indt.org.br> wrote:
>> >> ext Trilok Soni wrote:
>> >> > Let me know if anybody tested this patch on N800. Thanx.
>> >> >
>> >> > ---Trilok Soni
>> >> >
>> >> > On 5/26/07, Trilok Soni <soni.trilok@gmail.com> wrote:
>> >> >> n800 changes are compile tested only. Please test.
>> >> >>
>> >> >> --
>> >> >> --Trilok Soni
>> >> >>
>> >> >>
>> >> > _______________________________________________
>> >> > Linux-omap-open-source mailing list
>> >> > Linux-omap-open-source@linux.omap.com
>> >> > http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>> >> >
>> >> Hi Tony and Trilok,
>> >>
>> >> I've tested the patches
>> >> 0001-ARM-OMAP-Use-new-style-I2C-driver-for-Menelaus-chip.patch
>> >> 
>> (http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010100.html)
>> >>
>> >> and 0003-ARM-OMAP-Add-menelaus-chip-info-for-N800.patch
>> >> 
>> (http://linux.omap.com/pipermail/linux-omap-open-source/2007-May/010102.html)
>> >>
>> >>
>> >> by applying it together over MMC multislot support patches series for
>> >> N800 and looks fine (both slots with MMC, SD and SDHC cards).
>> >>
>> >> To test it, I'm using linux-omap tree, on commit
>> >> 9a0fba3f2ca8e58a1465d6c3c18f9f334d054304). Today I'll test with most
>> >> updated tree.
>> >>
>> >
>> > Thanx for the testing. Please share the result once you test it with
>> > latest tree.
>> >
>> Hi folks,
>>
>> Well, testing with most update linux-omap tree, I'm having some warnings
>> compilations (with or without patches series applied):
>>
>> WARNING: arch/arm/mach-omap2/built-in.o(.data+0x674): Section mismatch:
>> reference to .init.text:omap2_clk_disable_unused (between
>> 'omap2_clk_functions' and 'onchip_clks')
>> WARNING: arch/arm/vfp/built-in.o(.data+0x0): Section mismatch: reference
>> to .init.text:vfp_testing_entry (between 'vfp_vector' and
>> 'vfp_notifier_block')
>> WARNING: arch/arm/plat-omap/built-in.o(.data+0x95c): Section mismatch:
>> reference to .init.text:omap_timer_init (between 'omap_timer' and
>> 'omap_32k_timer_irq'
>
> These warnings are already discussed on mailing list. Better to ignore
> it for now.
>
>>
>> and when starting the device I get the following message:
>>
>> ...
>> Starting MAEMO AF Desktop
>> matchbox-wm: can't open display! check your DISPLAY variable.
>> DSME: process '/usr/bin/matchbox-window-manager -theme default
>> -use_titlebar yes -use_desktop_mode plain -use_lowlight no -use_cursor
>> yes -use_dialog_mode s1DSME: process '/usr/bin/matchbox-window-manager
>> -theme default -use_titlebar yes -use_desktop_mode plain -use_lowlight
>> no -use_cursor yes -use_dialog_mode sd and restarted with pid 1646
>> Segmentation fault
>> ...
>>
>> And then not starting the graphical environment. :(
>>
>> Anyway, by enabling debugging messages, the MMC looks fine.
>>
>
> Thanx. Tony, please push menelaus related patches from me and David.

Yeah I will.

Tony

      reply	other threads:[~2007-06-11 13:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26  8:29 [PATCH 3/3] ARM: OMAP: Add menelaus chip info for N800 Trilok Soni
2007-06-05 11:29 ` Trilok Soni
2007-06-05 14:41   ` Carlos Aguiar
2007-06-06  7:34     ` Trilok Soni
2007-06-06 19:47       ` Carlos Aguiar
2007-06-07  5:29         ` Trilok Soni
2007-06-11 13:31           ` Tony Lindgren [this message]

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=20070611133121.GL16039@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=soni.trilok@gmail.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