From: Tony Lindgren <tony@atomide.com>
To: Andrew de Quincey <adq_dvb@lidskialf.net>, ladis@linux-mips.org
Cc: linux-omap@vger.kernel.org
Subject: Re: Tracking N770 breakage
Date: Wed, 20 May 2009 08:19:07 -0700 [thread overview]
Message-ID: <20090520151907.GC8308@atomide.com> (raw)
In-Reply-To: <20090520061544.560957looc5zgav4@lidskialf.net>
* Andrew de Quincey <adq_dvb@lidskialf.net> [090519 22:15]:
> Quoting Tony Lindgren <tony@atomide.com>:
>
>> * Andrew de Quincey <adq_dvb@lidskialf.net> [090516 19:17]:
>>> Argh, my N770 seems to have just died; it has been behaving slightly
>>> oddly and now it simply won't turn on (black screen and no sign of life
>>> whatsoever).
>>>
>>> It is well out of warranty and frankly I don't see myself buying another
>>> one, so this effectively ends my hacking on it :(
>>
>> Bummer :(
>>
>> After a quick try, CONFIG_OMAP_RESET_CLOCKS was the first stopper, then
>> it could not mount the MMC root.
>
> Ahh excellent, that was why I posted my progress, in case it rang a bell
> with anyone! I think the touchpad driver may be broken as well BTW.
>
>> I think there was a patch posted for the omap1 MMC by Ladislav few months
>> ago that probably fixes it.
>
> Cool - I hope I may be back in the running soon (I was rather annoyed
> when I posted that message!); I've ordered a new battery in case its
> just that. A kind person has also offered me one thats broken in a
> different way that I can probably cobble together with the remains of
> mine if its something more critical that has died.
Good to hear, let's hope it just needs a new battery.
See also the n8x0 thread. If we get drivers/cbus to mainline, we
pretty much have everything we need for 770 in mainline too.
It would be nice to get the drivers/mmc/host/omap.c patch integrated
for 2.6.30 to make omap1 MMC work again. Ladislav, any news on that?
Regards,
Tony
next prev parent reply other threads:[~2009-05-20 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 13:06 Tracking N770 breakage Andrew de Quincey
2009-05-17 2:17 ` Andrew de Quincey
2009-05-19 23:15 ` Tony Lindgren
2009-05-20 5:15 ` Andrew de Quincey
2009-05-20 15:19 ` Tony Lindgren [this message]
2009-05-22 17:47 ` Andrew de Quincey
2009-05-22 18:33 ` Andrew de Quincey
2009-05-22 22:18 ` Andrew de Quincey
2009-05-23 1:39 ` Andrew de Quincey
2009-05-23 1:47 ` Tony Lindgren
2009-05-23 11:11 ` Andrew de Quincey
2009-05-23 11:30 ` Andrew de Quincey
2009-05-23 12:28 ` Andrew de Quincey
2009-05-23 13:25 ` Andrew de Quincey
2009-06-01 23:18 ` Tony Lindgren
2009-06-08 19:55 ` [patch] Convert cbus driver code to use platform APIs consistently Andrew de Quincey
2009-06-09 10:20 ` Tony Lindgren
2009-06-09 17:13 ` Andrew de Quincey
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=20090520151907.GC8308@atomide.com \
--to=tony@atomide.com \
--cc=adq_dvb@lidskialf.net \
--cc=ladis@linux-mips.org \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox