public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
	Dirk Behme <dirk.behme@googlemail.com>,
	Jonathan Herriott <herriojr@gmail.com>,
	linux-omap@vger.kernel.org
Subject: Re: Android on N810 File System Problem
Date: Wed, 30 Apr 2008 12:45:23 +0300	[thread overview]
Message-ID: <87fxt3y8uk.fsf@nokia.com> (raw)
In-Reply-To: <20080428233827.GE8449@atomide.com> (ext Tony Lindgren's message of "Mon\, 28 Apr 2008 16\:38\:28 -0700")

"ext Tony Lindgren" <tony@atomide.com> writes:

> * Felipe Balbi <me@felipebalbi.com> [080427 15:31]:
>> On Sun, Apr 27, 2008 at 12:43:19PM +0300, Kalle Valo wrote:
>> > "ext Felipe Balbi" <me@felipebalbi.com> writes:
>> > 
>> > > Current linux-omap's head has all the necessary pieces to get n810
>> > > working. Touchscreen, keypad, ambient light sensor, led, usb, everything
>> > > is there.
>> > 
>> > What about sound?
>> 
>> I'm sure it'll come from alsa-devel soon.
>
> I've merged Jarkko's asoc patch to linux-omap for testing. Have not
> gotten any sound out of it on my n810 though.. Maybe some alsamixer
> settings issue?
>
> Kalle, do you have any tips on getting WLAN to work on n8x0?

Unfortunately no. It's not a big task, but proprietary umac.ko is the
biggest problem. It needs to be recompiled.

> Don't know if there's anything new there to you, but I posted some
> info on getting things to work with current linux-omap kernel at:
>
> http://www.muru.com/linux/n8x0/

That's really handy, thanks.

-- 
Kalle Valo

  parent reply	other threads:[~2008-04-30  9:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6a56d69c0804241248w5e46efe8k757c9e5fb9e3ce22@mail.gmail.com>
2008-04-25  5:42 ` Android on N810 File System Problem Dirk Behme
2008-04-25 18:36   ` Felipe Balbi
2008-04-25 18:31     ` Igor Stoppa
2008-04-25 18:52       ` Felipe Balbi
2008-04-25 18:47         ` Igor Stoppa
2008-04-25 23:29           ` Felipe Balbi
2008-04-27  9:43     ` Kalle Valo
2008-04-27 22:32       ` Felipe Balbi
2008-04-27 23:04         ` Igor Stoppa
2008-04-28  6:24           ` Jarkko Nikula
2008-04-28 23:38         ` Tony Lindgren
2008-04-29  9:00           ` Brian Swetland
2008-04-30  9:49             ` Kalle Valo
2008-04-30 10:20               ` Brian Swetland
2008-04-30 10:46                 ` Felipe Balbi
2008-05-02  6:17                 ` Kalle Valo
2008-05-12 12:32             ` Dirk Behme
2008-04-29  9:49           ` Jarkko Nikula
2008-04-29 22:31             ` Jonathan Herriott
2008-04-30  1:04             ` Tony Lindgren
2008-04-30  9:45           ` Kalle Valo [this message]
2008-04-25 19:31   ` Jonathan Herriott
2008-04-25 23:35     ` Jonathan Herriott
2008-04-26  7:13     ` Dirk Behme
2008-04-27  2:21       ` Jonathan Herriott
2008-04-27  6:44         ` Dirk Behme
2008-04-27  8:13           ` Jonathan Herriott
2008-04-29  9:06         ` Brian Swetland
     [not found]           ` <200804290948.m3T9mLHt021830@smtp.google.com>
2008-04-29 10:13             ` Questions on Android Brian Swetland
2008-05-05 12:38               ` shivananda.hebbarp

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=87fxt3y8uk.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=dirk.behme@googlemail.com \
    --cc=herriojr@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --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