All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Varnin <fenixk19-JGs/UdohzUI@public.gmane.org>
To: Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
	Bing Zhao <bzhao-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
	"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: mwifiex_sdio on chromebook
Date: Tue, 05 Nov 2013 13:12:46 +0400	[thread overview]
Message-ID: <5278B68E.5070807@mail.ru> (raw)
In-Reply-To: <5278B1EC.8020000-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>

05.11.2013 12:53, Arend van Spriel пишет:
>>>
>>
>> It is ported at most already and mainline kernel works good on
>> Chromebook. It is just peripheral problem.
>
> Not sure how chromium os architecture looks like, but you mean to say
> *you* ported code in chromium user-space to work with
> upstream/mainline kernel API's? 

No. There is work doing by somebody from google or somewhere else, by
making mainline kernel work on Chromebook. Kernel 3.11 is the first
mainline kernel, that is able to boot and work on Chromebook. Working
parts is MMC controller, display controller, keyboard, etc. Not working
is usb, wifi, rtc, temperature sensors, etc.

By a tradition of open source, as I am interested, and I have experience
in kernel development, I have decided to debug wifi issue by myself. I
don't know, why I should port anything. Everything that was needed is
already ported - there is Chromebook device tree in kernel, there is all
required drivers. There is just a problem with powering up Marvell wifi
chip. I don't see, why fixing it requires any complex porting.

One thing worth doing is to compare 3.4 from chromeos and 3.4 mainline,
and find, if there any specific wifi changes. But there is possibly not.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Varnin <fenixk19@mail.ru>
To: Arend van Spriel <arend@broadcom.com>,
	Bing Zhao <bzhao@marvell.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: mwifiex_sdio on chromebook
Date: Tue, 05 Nov 2013 13:12:46 +0400	[thread overview]
Message-ID: <5278B68E.5070807@mail.ru> (raw)
In-Reply-To: <5278B1EC.8020000@broadcom.com>

05.11.2013 12:53, Arend van Spriel пишет:
>>>
>>
>> It is ported at most already and mainline kernel works good on
>> Chromebook. It is just peripheral problem.
>
> Not sure how chromium os architecture looks like, but you mean to say
> *you* ported code in chromium user-space to work with
> upstream/mainline kernel API's? 

No. There is work doing by somebody from google or somewhere else, by
making mainline kernel work on Chromebook. Kernel 3.11 is the first
mainline kernel, that is able to boot and work on Chromebook. Working
parts is MMC controller, display controller, keyboard, etc. Not working
is usb, wifi, rtc, temperature sensors, etc.

By a tradition of open source, as I am interested, and I have experience
in kernel development, I have decided to debug wifi issue by myself. I
don't know, why I should port anything. Everything that was needed is
already ported - there is Chromebook device tree in kernel, there is all
required drivers. There is just a problem with powering up Marvell wifi
chip. I don't see, why fixing it requires any complex porting.

One thing worth doing is to compare 3.4 from chromeos and 3.4 mainline,
and find, if there any specific wifi changes. But there is possibly not.

  parent reply	other threads:[~2013-11-05  9:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 13:01 mwifiex_sdio on chromebook Alexander Varnin
2013-11-03 22:10 ` Bing Zhao
2013-11-03 22:10   ` Bing Zhao
     [not found]   ` <477F20668A386D41ADCC57781B1F70430F45757E63-r8ILAu4/owuHXkj8w7BxOhL4W9x8LtSr@public.gmane.org>
2013-11-04  2:18     ` Alexander Varnin
2013-11-04  2:18       ` Alexander Varnin
2013-11-04 13:32       ` Luis R. Rodriguez
     [not found]       ` <527703E6.8040504-JGs/UdohzUI@public.gmane.org>
2013-11-04 19:46         ` Bing Zhao
2013-11-04 19:46           ` Bing Zhao
     [not found]           ` <477F20668A386D41ADCC57781B1F70430F45758053-r8ILAu4/owuHXkj8w7BxOhL4W9x8LtSr@public.gmane.org>
2013-11-05  8:38             ` Alexander Varnin
2013-11-05  8:38               ` Alexander Varnin
     [not found]               ` <5278AE8E.9060203-JGs/UdohzUI@public.gmane.org>
2013-11-05  8:53                 ` Arend van Spriel
2013-11-05  8:53                   ` Arend van Spriel
     [not found]                   ` <5278B1EC.8020000-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-11-05  9:12                     ` Alexander Varnin [this message]
2013-11-05  9:12                       ` Alexander Varnin
     [not found]                       ` <5278B68E.5070807-JGs/UdohzUI@public.gmane.org>
2013-11-05 16:26                         ` Paul Stewart
2013-11-05 16:26                           ` Paul Stewart

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=5278B68E.5070807@mail.ru \
    --to=fenixk19-jgs/udohzui@public.gmane.org \
    --cc=arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
    --cc=bzhao-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.