public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: Brian Swetland <swetland@google.com>
Cc: Tony Lindgren <tony@atomide.com>,
	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: Fri, 02 May 2008 09:17:12 +0300	[thread overview]
Message-ID: <87bq3p8c2f.fsf@nokia.com> (raw)
In-Reply-To: <20080430102036.GA23558@bulgaria.corp.google.com> (ext Brian Swetland's message of "Wed\, 30 Apr 2008 03\:20\:36 -0700")

Brian Swetland <swetland@google.com> writes:

> [Kalle Valo <kalle.valo@nokia.com>]
>> Brian Swetland <swetland@google.com> writes:
>> >
>> > This was the show-stopper for me.  When I last got things hobbling
>> > along on n8x0, the binary-only wlan module was incompatible with
>> > newer kernels than 2.6.21 (changes in some network data structures).
>> 
>> That's exactly the problem. I have written something about it here:
>> 
>> https://garage.maemo.org/pipermail/cx3110x-devel/2007-December/000007.html
>
> Just did a quick diff between v2.6.21 and v2.6.24 and the skbuff changes
> are pretty daunting.  Doesn't look like there's an easy hack here...
>
>> Currently there's nothing I can do to resolve the issue, unfortunately.
>
> Pity.  It'd be nice to get newer kernels running on the n8x0 -- it's
> nice hardware.

Trust me, I share the pain. If a solution comes up, I'll let you know.

It's also a good idea to follow cx3110x-devel:

https://garage.maemo.org/mailman/listinfo/cx3110x-devel

-- 
Kalle Valo

  parent reply	other threads:[~2008-05-02  6:17 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 [this message]
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
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=87bq3p8c2f.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=swetland@google.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