From: Deepak Saxena <dsaxena@plexity.net>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: dsaxena@laptop.org, libertas-dev@lists.infradead.org,
linux-wireless@vger.kernel.org, Nicolas Pitre <nico@marvell.com>
Subject: Re: [PATCH] libertas: add auto auth mode feature
Date: Wed, 3 Mar 2010 10:52:31 -0800 [thread overview]
Message-ID: <20100303185231.GA14009@plexity.net> (raw)
In-Reply-To: <201003021302.10039.holgerschurig@gmail.com>
On Mar 02 2010, at 13:02, Holger Schurig was caught saying:
> > support is an option our community would be happy with. However, I also
> > don't want to end up with a libertas fork (all our mesh patches are
> > currently upstream and not forkd off)
>
> Oh, sorry for being misinformed and spreading this misinformation. I had some
> read-only variables in the mainline libertas driver (for example
> mesh_autostart_enabled get's never written to) and heard that this is a
> remnant, and that the real implementation in in the OLPC tree.
That is definitely a remnant of old work and our tree seems to have the
same read-only issues.
> Therefore I thought that you're sticking to some older kernel, and not
> following mainline linux at all.
We're currently on 2.6.31, which I guess is somewhat pre-historic by
kernel development standards. We do have some patches to Libertas which
were co-developed along with Marvell to fix some bugs we've discovered
during the XO-1.5 ramp up process and unfortunately we were on a really
tight release schedule and not all of those have been pushed upstream,
including some changes to the SDIO stack that were needed for proper
suspend/resume support on the gen 2 laptops. I'll be working on moving
our kernel up to a newer version and will send up any patches that
we need merged and will also work with our users to figure out what
to do about mesh testing.
~Deepak
--
"People think all we need to fix our predicament is a free source of
energy, but I think we need to change out behaviour. More energy would
just deplete the Earth's lifeblood faster." - Janine Benyius
next prev parent reply other threads:[~2010-03-03 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 1:16 [PATCH] libertas: add auto auth mode feature Bing Zhao
2010-02-26 12:55 ` Holger Schurig
[not found] ` <c1545bb51002261210h27ba9868tca0261742b848e51@mail.gmail.com>
[not found] ` <1267225266.14995.7.camel@localhost.localdomain>
2010-03-01 19:59 ` Deepak Saxena
2010-03-02 12:02 ` Holger Schurig
2010-03-03 18:52 ` Deepak Saxena [this message]
2010-03-03 19:06 ` Nicolas Pitre
2010-02-26 13:08 ` Marcel Holtmann
2010-02-26 13:21 ` Johannes Berg
2010-02-26 23:02 ` Dan Williams
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=20100303185231.GA14009@plexity.net \
--to=dsaxena@plexity.net \
--cc=dsaxena@laptop.org \
--cc=holgerschurig@gmail.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nico@marvell.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;
as well as URLs for NNTP newsgroup(s).