From: Kalle Valo <kalle.valo@iki.fi>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Christian Lamparter <chunkeey@web.de>,
Alexander Wenzel <wenzel@fgan.de>,
linux-wireless@vger.kernel.org
Subject: Re: Problem with p54 driver and ibss mode
Date: Fri, 10 Jul 2009 11:10:15 +0300 [thread overview]
Message-ID: <87iqi10xi0.fsf@litku.valot.fi> (raw)
In-Reply-To: <73aaf0dd0907100043p7916c4fbid9aa2faa3580477d@mail.gmail.com> (Max Filippov's message of "Fri\, 10 Jul 2009 11\:43\:48 +0400")
Max Filippov <jcmvbkbc@gmail.com> writes:
>>> Should be easy to copy the code into p54spi, we just never did, hoping
>>> Kalle would come up with a better way, maybe request_firmware() :)
>>
>> I agree with you, better not to copy the sysfs interface to p54spi. I'm
>> planning to experiment with the firmware interface at some point, but it
>> would be great if someone else could take a look at it first.
>
> I can take a look at it. (:
Excellent!
> But the question is... to take a look at it to see what?
:)
Basically we have been talking about fetching calibration data via the
request_firmware() interface. In user space there would be a udev script
which would dynamically retrieve the calibration data specific to the
platform it is running on. In N800/N810 case that would mean to run
stlc45xx-cal and provide the calibration data to the driver.
This way we can have platform specific implementations and use already
existing user space interface. The idea was discussed in this mailing
list few months ago. The implementation details are currently unknown to
me. I was planning to talk about this at the Wireless Summit, but of
course I forgot :/
stlc45xx-cal will most probably need some changes, maybe dumping the
calibration data to stdout so that udev script can forward it to the
driver? I can do the necessary changes to stlc45xx-cal, but it's better
to have a some sort of working prototype before I'll start changing
stlc45xx-cal.
--
Kalle Valo
next prev parent reply other threads:[~2009-07-10 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 11:59 Problem with p54 driver and ibss mode Alexander Wenzel
2009-07-09 13:20 ` Max Filippov
2009-07-09 15:35 ` Alexander Wenzel
2009-07-09 17:57 ` Max Filippov
2009-07-09 18:56 ` Christian Lamparter
2009-07-09 19:55 ` Kalle Valo
2009-07-09 21:43 ` Max Filippov
2009-07-09 21:48 ` Johannes Berg
2009-07-10 7:01 ` Kalle Valo
2009-07-10 7:43 ` Max Filippov
2009-07-10 8:10 ` Kalle Valo [this message]
2009-07-10 8:36 ` Max Filippov
2009-07-10 10:29 ` Alexander Wenzel
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=87iqi10xi0.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=chunkeey@web.de \
--cc=jcmvbkbc@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wenzel@fgan.de \
/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).